Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[kde-testing] and [kde-crazy] KDE4 overlays thread (part 2)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6 ... 28, 29, 30  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
xeonman9000
n00b
n00b


Joined: 06 Aug 2008
Posts: 51
Location: UK

PostPosted: Tue Oct 21, 2008 9:48 pm    Post subject: Reply with quote

How can I install Amarok 1.92.2? I am on an x86_64 system and I get the following messages:

Code:
!!! All ebuilds that could satisfy "=media-sound/amarok-1.92.2" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-sound/amarok-1.92.2 (masked by: missing keyword)


normally I would just use
ACCEPT_KEYWORDS="~amd64" emerge -vp =media-sound/amarok-1.92.2
But this is a "missing keyword" problem, anyone know how to get around this?
Back to top
View user's profile Send private message
loftwyr
l33t
l33t


Joined: 29 Dec 2004
Posts: 970
Location: 43°38'23.62"N 79°27'8.60"W

PostPosted: Tue Oct 21, 2008 11:47 pm    Post subject: Reply with quote

Just run the command:
Code:

echo "=media-sound/amarok-1.92.2 **" >> /etc/portage/package.keywords

_________________
My emerge --info
Have you run revdep-rebuild lately? It's in gentoolkit and it's worth a shot if things don't work well.
Celebrating 5 years of Gentoo-ing.
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Wed Oct 22, 2008 7:42 am    Post subject: Reply with quote

Quote:
normally I would just use
ACCEPT_KEYWORDS="~amd64" emerge -vp =media-sound/amarok-1.92.2


Never do that. Use /etc/portage/package.keywords instead.

echo "=media-sound/amarok-1.92.2 ~amd64" >> /etc/portage/package.keywords

or

echo "=media-sound/amarok-1.92.2 ~amd64" >> /etc/portage/package.keywords/somefilename

if package.keywords is a folder. I use the latter.

The reason is the next upgrade

emerge -uDNv world

will want to downgrade your ~amd64 packages.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
rocktale
n00b
n00b


Joined: 13 May 2006
Posts: 6
Location: Munich, Germany

PostPosted: Wed Oct 22, 2008 11:09 am    Post subject: Reply with quote

I'm running the KDE 4.1.2 from portage but I wanted to use the new amarok (1.92.2) and maybe some of the plasmoids from the kde-testing overlay. However, when I add the overlay using layman, portage complains that the overlay overrides some eclasses from portage and I read in another forum post that it's not a good idea to ignore that.

So my question is: What would be the best (gentoo) way to solve this?
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Wed Oct 22, 2008 1:23 pm    Post subject: Reply with quote

Quote:
So my question is: What would be the best (gentoo) way to solve this?


I would either ignore the warining or install kde-meta:4.2 instead of 4.1.2.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3250
Location: Gainesville, Florida

PostPosted: Wed Oct 22, 2008 5:40 pm    Post subject: Reply with quote

On today's rebuild of kdebase-svn, kde-base/plasma-workspace-9999 failed.
Entire failure output here: http://pastebin.com/m4cf6eec8
Code:
clock.moc: In member function 'virtual void* Clock::qt_metacast(const char*)':
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace_build/plasma/applets/analog-clock/clock.moc:59: error: 'ClockApplet' has not been declared
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace_build/plasma/applets/analog-clock/clock.moc: In member function 'virtual int Clock::qt_metacall(QMetaObject::Call, int, void**)':
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace_build/plasma/applets/analog-clock/clock.moc:64: error: 'ClockApplet' has not been declared
/usr/kde/svn/include/kpluginfactory.h: In static member function 'static QObject* KPluginFactory::createInstance(QWidget*, QObject*, const QVariantList&) [with impl = Clock, ParentType = QObject]':
/usr/kde/svn/include/kpluginfactory.h:479:   instantiated from 'QObject* (* KPluginFactory::InheritanceChecker<impl>::createInstanceFunction(...))(QWidget*, QObject*, const QVariantList&) [with impl = Clock]'
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace/plasma/applets/analog-clock/clock.h:89:   instantiated from here
/usr/kde/svn/include/kpluginfactory.h:461: error: cannot convert 'Clock*' to 'QObject*' in return
make[2]: *** [plasma/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/clock.o] Error 1
make[1]: *** [plasma/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Scanning dependencies of target plasma_applet_activitybar
[  1%] Building CXX object plasma/applets/activitybar/CMakeFiles/plasma_applet_activitybar.dir/activitybar.o
[  1%] Building CXX object plasma/applets/activitybar/CMakeFiles/plasma_applet_activitybar.dir/plasma_applet_activitybar_automoc.o
Linking CXX shared module ../../../lib/plasma_applet_activitybar.so
[  1%] Built target plasma_applet_activitybar
make: *** [all] Error 2
 *
 * ERROR: kde-base/plasma-workspace-9999 failed.


Any seeing this one? I'm thinking line 272 at the pastebin link above.
Code:
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace/plasma/applets/analog-clock/clock.h:38:40: error: libplasmaclock/clockapplet.h: No such file or directory


Hmmmm. krunner problems again also http://pastebin.com/m6c1e736e

UPDATE on plasma-workspace. I tried commented out the analog-clock applet in CMaKeLists.txt, but then another applet failed, and after also commenting it out, another applet failed. So it seems it's not just an individual applet gone bad. Am now trying deleting the kdebase src, and getting a fresh download of it. Also need a layman -s kdesvn-portage- forgot about that. :oops:
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r5, gcc-9.2.0 kernel-5.2.10-gentoo USE=experimental
Back to top
View user's profile Send private message
aliquid
n00b
n00b


Joined: 14 Mar 2008
Posts: 37

PostPosted: Wed Oct 22, 2008 7:48 pm    Post subject: Reply with quote

wrc1944 wrote:
On today's rebuild of kdebase-svn, kde-base/plasma-workspace-9999 failed.
Entire failure output here: http://pastebin.com/m4cf6eec8
Code:
clock.moc: In member function 'virtual void* Clock::qt_metacast(const char*)':
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace_build/plasma/applets/analog-clock/clock.moc:59: error: 'ClockApplet' has not been declared
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace_build/plasma/applets/analog-clock/clock.moc: In member function 'virtual int Clock::qt_metacall(QMetaObject::Call, int, void**)':
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace_build/plasma/applets/analog-clock/clock.moc:64: error: 'ClockApplet' has not been declared
/usr/kde/svn/include/kpluginfactory.h: In static member function 'static QObject* KPluginFactory::createInstance(QWidget*, QObject*, const QVariantList&) [with impl = Clock, ParentType = QObject]':
/usr/kde/svn/include/kpluginfactory.h:479:   instantiated from 'QObject* (* KPluginFactory::InheritanceChecker<impl>::createInstanceFunction(...))(QWidget*, QObject*, const QVariantList&) [with impl = Clock]'
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace/plasma/applets/analog-clock/clock.h:89:   instantiated from here
/usr/kde/svn/include/kpluginfactory.h:461: error: cannot convert 'Clock*' to 'QObject*' in return
make[2]: *** [plasma/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/clock.o] Error 1
make[1]: *** [plasma/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Scanning dependencies of target plasma_applet_activitybar
[  1%] Building CXX object plasma/applets/activitybar/CMakeFiles/plasma_applet_activitybar.dir/activitybar.o
[  1%] Building CXX object plasma/applets/activitybar/CMakeFiles/plasma_applet_activitybar.dir/plasma_applet_activitybar_automoc.o
Linking CXX shared module ../../../lib/plasma_applet_activitybar.so
[  1%] Built target plasma_applet_activitybar
make: *** [all] Error 2
 *
 * ERROR: kde-base/plasma-workspace-9999 failed.


Any seeing this one? I'm thinking line 272 at the pastebin link above.
Code:
/var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace/plasma/applets/analog-clock/clock.h:38:40: error: libplasmaclock/clockapplet.h: No such file or directory


Hmmmm. krunner problems again also http://pastebin.com/m6c1e736e

UPDATE on plasma-workspace. I tried commented out the analog-clock applet in CMaKeLists.txt, but then another applet failed, and after also commenting it out, another applet failed. So it seems it's not just an individual applet gone bad. Am now trying deleting the kdebase src, and getting a fresh download of it. Also need a layman -s kdesvn-portage- forgot about that. :oops:


Your build fails because you don't have latest libplasmaclock. You may create a custom ebuild for it (library was moved to kdebase/plasma/libplasmaclock), but I doubt it's good idea because current trunk is quite broken
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3250
Location: Gainesville, Florida

PostPosted: Wed Oct 22, 2008 7:55 pm    Post subject: Reply with quote

UPDATE on above post. OK. synced kdesvn-portage, and thought i had it solved. Got some new stuff- sip, PyQt4-4.4.3, and pykde4.

Then on libplasmaclock it compiles, but won't install due to file collisions. the usual tricks don't work.

FEATURES="collision-protect"

or
COLLISION_IGNORE="libplasmaclock.so.4.2.0 libplasmaclock.so.4 libplasmaclock.so" emerge libplasmaclock

None of those files are owned by any installed packages.

Code:
>>> Installing kde-base/libplasmaclock-9999
* checking 13 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 *
 * Detected file collision(s):
 *
 *    /usr/kde/svn/lib/libplasmaclock.so.4.2.0
 *    /usr/kde/svn/lib/libplasmaclock.so.4
 *    /usr/kde/svn/lib/libplasmaclock.so
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * kde-base/plasma-workspace-9999
 *    /usr/kde/svn/lib/libplasmaclock.so
 *    /usr/kde/svn/lib/libplasmaclock.so.4
 *    /usr/kde/svn/lib/libplasmaclock.so.4.2.0
 *
 * Package 'kde-base/libplasmaclock-9999' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.

Why can't I ignore these file collisions with the above methods? :? 8O
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r5, gcc-9.2.0 kernel-5.2.10-gentoo USE=experimental
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3250
Location: Gainesville, Florida

PostPosted: Wed Oct 22, 2008 7:59 pm    Post subject: Reply with quote

Thanks aliquid,
layman -s kdesvn-portage got me an ebuild and libplasmaclock compiles, but the collisions are the big install stopper. Any ideas?

Looked at the ebuild- very short and simple one- maybe it's missing something???
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r5, gcc-9.2.0 kernel-5.2.10-gentoo USE=experimental
Back to top
View user's profile Send private message
aliquid
n00b
n00b


Joined: 14 Mar 2008
Posts: 37

PostPosted: Wed Oct 22, 2008 8:04 pm    Post subject: Reply with quote

wrc1944 wrote:
Thanks aliquid,
layman -s kdesvn-portage got me an ebuild and libplasmaclock compiles, but the collisions are the big install stopper. Any ideas?

Try to delete all libplasmaclock* in /usr/kde/svn/lib/. That worked for me
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3250
Location: Gainesville, Florida

PostPosted: Wed Oct 22, 2008 8:23 pm    Post subject: Reply with quote

Code:
COLLISION_IGNORE="/usr/kde/svn/lib/libplasmaclock.so.4.2.0 /usr/kde/svn/lib/libplasmaclock.so.4 /usr/kde/svn/lib/libplasmaclock.so" emerge libplasmaclock
worked for me.

I had to use the whole path for the files. Thanks for your tip. :D

plasma-workspace worked too. :D On to the krunner problem. :roll:

UPDATE: krunner installed OK now, after the above stuff was fixed. :D
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r5, gcc-9.2.0 kernel-5.2.10-gentoo USE=experimental
Back to top
View user's profile Send private message
xeonman9000
n00b
n00b


Joined: 06 Aug 2008
Posts: 51
Location: UK

PostPosted: Wed Oct 22, 2008 10:07 pm    Post subject: Reply with quote

loftwyr wrote:
Just run the command:
Code:

echo "=media-sound/amarok-1.92.2 **" >> /etc/portage/package.keywords


OK, I did this and it seemed to be going fine until it failed at 98%

Code:
[ 98%] Building CXX object src/context/applets/albums/CMakeFiles/amarok_context_applet_albums.dir/amarok_context_applet_albums_automoc.o                       
Linking CXX shared module ../../../../lib/amarok_context_applet_albums.so       
[ 98%] Built target amarok_context_applet_albums                               
make: *** [all] Error 2                                                         
 *                                                                             
 * ERROR: media-sound/amarok-1.92.2 failed.                                     
 * Call stack:                                                                 
 * ebuild.sh, line   49:  Called src_compile                                   
 * environment, line 2722:  Called kde4-base_src_compile                       
 * environment, line 2040:  Called kde4-base_src_make                           
 * environment, line 2093:  Called cmake-utils_src_make                         
 * environment, line  658:  Called die                                         
 * The specific snippet of code:                                               
 * emake "$@" || die "Make failed!";                                           
 * The die message:                                                             
 * Make failed!                                                                 
 *                                                                             
 * If you need support, post the topmost build error, and the call stack if relevant.                                                                           
 * A complete build log is located at '/var/tmp/portage/media-sound/amarok-1.92.2/temp/build.log'.                                                             
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/amarok-1.92.2/temp/environment'.                                                     
 * This ebuild used the following eclasses from overlays:                       
 * /usr/portage/local/layman/kde-testing/eclass/kde4-base.eclass               
 * /usr/portage/local/layman/kde-testing/eclass/kde4-functions.eclass           
 *                                                                             

>>> Failed to emerge media-sound/amarok-1.92.2, Log file:

>>>  '/var/tmp/portage/media-sound/amarok-1.92.2/temp/build.log'

 * Messages for package media-sound/amarok-1.92.2:

 *
 * ERROR: media-sound/amarok-1.92.2 failed.
 * Call stack:
 * ebuild.sh, line   49:  Called src_compile
 * environment, line 2722:  Called kde4-base_src_compile
 * environment, line 2040:  Called kde4-base_src_make
 * environment, line 2093:  Called cmake-utils_src_make
 * environment, line  658:  Called die
 * The specific snippet of code:
 * emake "$@" || die "Make failed!";
 * The die message:
 * Make failed!
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/media-sound/amarok-1.92.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/amarok-1.92.2/temp/environment'.
 * This ebuild used the following eclasses from overlays:
 * /usr/portage/local/layman/kde-testing/eclass/kde4-base.eclass
 * /usr/portage/local/layman/kde-testing/eclass/kde4-functions.eclass


Nothing immediately jumps out at me, what has gone wrong?
Back to top
View user's profile Send private message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Thu Oct 23, 2008 7:26 am    Post subject: Reply with quote

kdesvn-portage and kde-testing are merging together. nice.
Back to top
View user's profile Send private message
Krog
Guru
Guru


Joined: 26 Jun 2007
Posts: 330
Location: Roma, Italy

PostPosted: Fri Oct 24, 2008 11:35 am    Post subject: Reply with quote

is there an ebuild for the latest kdenlive for kde4?
Back to top
View user's profile Send private message
lazx888
Tux's lil' helper
Tux's lil' helper


Joined: 13 Sep 2005
Posts: 118

PostPosted: Fri Oct 24, 2008 5:32 pm    Post subject: Reply with quote

Trying to install kde 4.2 weekly snapshots... Getting this error when installing strigi:

Quote:

.... (CUT)
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4/bits/ostream.tcc:430: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_streambuf<_CharT, _Traits>*) [with _CharT = wchar_t, _Traits = std::char_traits<wchar_t>]
make[2]: *** [src/daemon/eventlistener/CMakeFiles/eventlistener.dir/eventlistenerqueue.o] Error 1
make[1]: *** [src/daemon/eventlistener/CMakeFiles/eventlistener.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 26%] Building CXX object src/archiveengine/CMakeFiles/archiveengine.dir/archiveenginehandler.o
[ 26%] Building CXX object src/archiveengine/CMakeFiles/archiveengine.dir/fsfileinputstream.o
[ 26%] [ 26%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/testrunner.o
Building CXX object src/archiveengine/CMakeFiles/archiveengine.dir/streamengine.o
[ 26%] [ 27%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/Base64InputStreamTest.o
Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/BZ2InputStreamTest.o
[ 27%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/EventInputStreamTest.o
Linking CXX static library libarchiveengine.a
[ 27%] [ 27%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/FileInputStreamTest.o
Built target archiveengine
[ 28%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/GZipInputStreamTest.o
[ 28%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/InputStreamReaderTest.o
[ 28%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/InputStreamTest.o
[ 29%] [ 29%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/KmpSearcherTest.o
Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/MailInputStreamTest.o
[ 30%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/RpmInputStreamTest.o
[ 30%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/StringTerminatedSubStreamTest.o
[ 30%] [ 31%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/SubInputStreamTest.o
Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/SdfInputStreamTest.o
[ 31%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/TarInputStreamTest.o
[ 31%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/ZipInputStreamTest.o
[ 32%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/stat64bitTest.o
[ 32%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/ArchiveReaderTest.o
[ 32%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/ProcessInputStreamTest.o
[ 33%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/StringStreamTest.o
[ 33%] Building CXX object src/streams/tests/CMakeFiles/testrunner-streams.dir/inputstreamtests.o
Linking CXX executable testrunner-streams
[ 33%] Built target testrunner-streams
make: *** [all] Error 2
/usr/libexec/paludis/utils/emake: emake returned error 2

!!! ERROR in app-misc/strigi-0.5.11:
!!! In cmake-utils_src_make at line 915
!!! Make failed!

!!! Call stack:
!!! * cmake-utils_src_make (/var/tmp/paludis/app-misc-strigi-0.5.11/temp/loadsaveenv:915)
!!! * cmake-utils_src_compile (/var/tmp/paludis/app-misc-strigi-0.5.11/temp/loadsaveenv:866)
!!! * src_compile (/var/tmp/paludis/app-misc-strigi-0.5.11/temp/loadsaveenv:3432)
!!! * ebuild_f_compile (/usr/libexec/paludis/2/src_compile.bash:54)
!!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:477)
!!! * main (/usr/libexec/paludis/ebuild.bash:492)

diefunc: making ebuild PID 22755 exit with error
die trap: exiting with error.

Install error:
* In program paludis -i strigi:
* When performing install action from command line:
* When executing install task:
* When installing 'app-misc/strigi-0.5.11:0::gentoo':
* Install error: Install failed for 'app-misc/strigi-0.5.11:0::gentoo'



Summary of failures:

* app-misc/strigi-0.5.11:0::gentoo: failure


Ideas?

Thanks guys!


//EDIT

strigi-9999 installs fine. Should I be using svn packages for all of kde 4.2 svn weekly snapshots? Thanks.
Back to top
View user's profile Send private message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Sat Oct 25, 2008 2:53 pm    Post subject: Reply with quote

there is no kde-base/kdeplasma-addons-4.1.71 in kde-testing. is it temporary?
Back to top
View user's profile Send private message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Sat Oct 25, 2008 3:42 pm    Post subject: Reply with quote

kded4 global shortcuts daemon doesn't work in 4.1.71. Global shortcuts don't work. When I go to the Keybaord&Mouse in System settings it says

Failed to contact the KDE global shortcuts daemon
Message: No such object path '/modules/kdedglobalaccel'
Error: org.freedesktop.DBus.Error.UnknownObject

UPDATE:


Generally 4.1.71 isn't very stable. Plasma dies from time to time without any crash report. Fixed

UPDATE2: Fixed in kde-testing

x11-themes/gtk-engines-qt-1.1-r1 dies with this error:

* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/local/portage/layman/kde-testing/x11-themes/gtk-engines-qt/files/1.1-stdlib.patch
* ( 1.1-stdlib.patch )
*
* ERROR: x11-themes/gtk-engines-qt-1.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_prepare
* environment, line 2821: Called epatch '/usr/local/portage/layman/kde-testing/x11-themes/gtk-engines-qt/files/1.1-stdlib.patch'
* environment, line 1319: Called die
* The specific snippet of code:
* die "Cannot find $EPATCH_SOURCE!";
* The die message:
* Cannot find $EPATCH_SOURCE!

UPDATE3:


So plasma dies because of playground-plasma:

plasma: symbol lookup error: /usr/lib64/kde4/plasma_applet_tasks.so: undefined symbol: _ZN6Plasma14ToolTipManager14ToolTipContentC1Ev

CONCLUSION:

Migrating from kdesvn-portage was almost painless.
KDED4 doesn't work in 4.1.71 (or am I doing something wrong?). Fixed by installing kde-base/kdedglobalaccel
Removing playground-plasma fixes plasma crashes.
It looks like there is no need in kdeplasma-addons because of kde-plasmoids category in kde-testing (kdesvn-portage didn't have it) BUT there are missing some plasmoid ebuilds (e.g. komix, lancelot etc.) from kdeplasma-addons and playground-plasma.
Missing patch in gtk-engines-qt.

That's all folks.


Last edited by aTan on Sun Oct 26, 2008 12:15 pm; edited 5 times in total
Back to top
View user's profile Send private message
uraes
Tux's lil' helper
Tux's lil' helper


Joined: 28 Nov 2002
Posts: 120
Location: Estonia

PostPosted: Sat Oct 25, 2008 5:12 pm    Post subject: Reply with quote

aTan wrote:

Generally 4.1.71 isn't very stable. Plasma dies from time to time without any crash report.


Leaving unstabilty aside - how did you get .71 at all? Siting already for two weeks or so on .69 and no updates (70 was there but due kbruch error it was unable to compile without hacking). I know that kdesvn-portage overlay is currently merged to kde-testing, but as I understand it might get usable at the beginning next week.
Back to top
View user's profile Send private message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Sat Oct 25, 2008 5:30 pm    Post subject: Reply with quote

uraes wrote:
aTan wrote:

Generally 4.1.71 isn't very stable. Plasma dies from time to time without any crash report.


Leaving unstabilty aside - how did you get .71 at all? Siting already for two weeks or so on .69 and no updates (70 was there but due kbruch error it was unable to compile without hacking). I know that kdesvn-portage overlay is currently merged to kde-testing, but as I understand it might get usable at the beginning next week.


It was merged 6 hours ago (according to git log).
Back to top
View user's profile Send private message
lazx888
Tux's lil' helper
Tux's lil' helper


Joined: 13 Sep 2005
Posts: 118

PostPosted: Sun Oct 26, 2008 5:30 am    Post subject: Weekly snapshots... Reply with quote

New to this overlay... have been using the kde4-experimental overlay (paludis based, has had sets for a long time now :) - but that is beside the point).

Anyway, I have switched to the overlay because I like the sound of weekly snapshots (and hopefully tested snapshots...). So how does this work? When I do a update world, every 7 days, I will see that there are new kde4 packages available (ie, version change from 4.1.69 to 4.1.70)???

Thanks devs!
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Sun Oct 26, 2008 1:51 pm    Post subject: Reply with quote

It's more like 2 weeks or so. To update I now use portage2.2 and

Code:
layman -S
emerge -av kde-meta:4.2 --keep-going

_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Sun Oct 26, 2008 2:48 pm    Post subject: Reply with quote

From git:
Quote:

Revert overlay to state before destroying stuff pass 1. Note all users whom wants kde-live and kde-snapshots please checkout kde-crazy overlay.


Where can I find kde-crazy overlay? It's not in layman.
Back to top
View user's profile Send private message
lazx888
Tux's lil' helper
Tux's lil' helper


Joined: 13 Sep 2005
Posts: 118

PostPosted: Sun Oct 26, 2008 3:51 pm    Post subject: Reply with quote

But will the kde version numbers change? (ie, how do you know there are new snapshots?)

drescherjm wrote:
It's more like 2 weeks or so. To update I now use portage2.2 and

Code:
layman -S
emerge -av kde-meta:4.2 --keep-going
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Sun Oct 26, 2008 5:32 pm    Post subject: Reply with quote

Quote:
how do you know there are new snapshots


Watching the layman output you can see when there are new ebuilds. If you miss that

Code:
# equery list kde -o


will do.

BTW, The latest I am seeing in kdesvn-portage is 4.1.69.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Sun Oct 26, 2008 6:05 pm    Post subject: Reply with quote

kdesvn-portage is obsolete and as far as I know will be removed next week. Now you can try this overlay git://git.overlays.gentoo.org/proj/kde-crazy.git it has 4.1.71, see http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=03981f82e3be667fb192dd091763b7ad64bae0cc
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6 ... 28, 29, 30  Next
Page 5 of 30

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum