Re: [gentoo-user] Trying KDE-4
On Thursday 23 October 2008 11:03:12 Daniel Pielmeier wrote: I thought he already installed some of the qt split ebuilds so they should be unmasked, but let us see :-) $ sudo autounmask x11-libs/qt-4.3.3 autounmask version 0.21 (using PortageXS-0.02.07 and portage-2.2_rc12) * Using repository: /usr/portage * Using package.keywords file: /etc/portage/package.keywords * Using package.unmask file: /etc/portage/package.unmask * Unmasking x11-libs/qt-4.3.3 and its dependencies.. this might take a while.. * done! $ tail -n 7 /etc/portage/package.unmask # --- # BEGIN: x11-libs/qt-4.3.3 # --- # --- # END: x11-libs/qt-4.3.3 # --- $ tail -n 7 /etc/portage/package.keywords # --- # BEGIN: x11-libs/qt-4.3.3 # --- # --- # END: x11-libs/qt-4.3.3 # --- -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
On Thursday 23 October 2008 11:03:12 Daniel Pielmeier wrote: I thought he already installed some of the qt split ebuilds so they should be unmasked, but let us see :-) I've found it myself. For some reason I had these two entries in my world file: x11-libs/qt x11-libs/qt:3 Once I'd removed those the blocks disappeared. Thanks to those who tried to help. -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
On Wednesday 22 October 2008 19:32:08 Daniel Pielmeier wrote: Please post again the output from emerge -pvutND world but attach it in a file so it doesn't get crippled by the mail program. Attached. Also what I have seen from your previous tree output is that you are trying to do many things at one time. Upgrading to kde4 changing and changing many use flags. This makes debugging very hard. Try to do only one thing at a time That's only because one thing leads to another. All I wanted to do was to install KDE-4; everything else I've tried has been to enable that. Of course I do try to do only one thing at a time - I had half a lifetime of debugging of one kind or another. I started by running autounmask, as suggested by Neil B; that unmasked 81 packages. Then I tried to update world - 82 times: one for each other package that needed unmasking. At the end of that I had all the packages unmasked that were required for an upgrade to KDE-4, but I also had the blocker that started this conversation. I've been trying to find the conflict in dependencies ever since, with your help - thanks again. Here's another titbit: $ equery d '=x11-libs/qt-4.4.0_alpha:4' [ Searching for packages depending on =x11-libs/qt-4.4.0_alpha:4... ] app-text/poppler-bindings-0.8.7 (qt4? =x11-libs/qt-4.3:4) x11-libs/qscintilla-2.1-r1 (qt4? =x11-libs/qt-4.3*:4) -- Rgds Peter These are the packages that would be merged, in reverse order: Calculating dependencies ... ... done! [ebuild R ] app-office/openoffice-3.0.0 USE=cups dbus* gtk java kde mono nsplugin opengl pam -debug -eds -gnome -gstreamer -ldap -odk -templates LINGUAS=en_GB -af -ar -as_IN -be_BY -bg -bn -br -bs -ca -cs -cy -da -de -dz -el -en -en_US -en_ZA -eo -es -et -fa -fi -fr -ga -gl -gu_IN -he -hi_IN -hr -hu -it -ja -km -ko -ku -lt -lv -mk -ml_IN -mr_IN -nb -ne -nl -nn -nr -ns -or_IN -pa_IN -pl -pt -pt_BR -ru -rw -sh -sk -sl -sr -ss -st -sv -sw_TZ -ta_IN -te_IN -tg -th -ti_ER -tn -tr -ts -uk -ur_IN -ve -vi -xh -zh_CN -zh_TW -zu 338,400 kB [ebuild NS ] kde-base/kdebase-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] x11-libs/qt-4.3.3 [3.3.8-r4] USE=accessibility cups dbus gif jpeg mng mysql odbc opengl png qt3support ssl tiff zlib -debug -doc -examples (-firebird) -glib -nas -nis -pch -postgres -sqlite -sqlite3 -xinerama INPUT_DEVICES=-wacom 41,350 kB [ebuild NS ] kde-base/kdegraphics-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] kde-base/kdemultimedia-meta-4.1.2 [3.5.9] 0 kB [ebuild U ] media-video/mplayer-1.0_rc2_p27725-r1 [1.0_rc2_p26753] USE=3dnowext X a52 alsa arts cddb cdparanoia cpudetection doc dv dvd enca gif gtk iconv ipv6 jpeg live mad mmx mmxext mp3 openal opengl png real rtc sdl sse sse2 theora truetype unicode vorbis x264 xanim xscreensaver xv xvid xvmc -3dnow -aac -aalib (-altivec) -amrnb -amrwb -bidi -bindist -bl -cdio -custom-cflags -custom-cpuopts% -debug -dga -dirac% -directfb -dts -dvb -dxr3% -encode -esd -fbcon -ftp -ggi -jack -joystick -ladspa -libcaca -lirc -lzo -md5sum -mp2 -musepack -nas -nemesi -oss -pnm -pulseaudio -pvr% -quicktime -radio -rar -samba -schroedinger% -speex -srt -ssse3 (-svga) -teletext -tga -v4l -v4l2 (-vidix) (-win32codecs) -xinerama -zoran VIDEO_CARDS=-mga -s3virge -tdfx -vesa 8,170 kB [ebuild NS ] kde-base/kdeutils-meta-4.1.2 [3.5.9] USE=-floppy 0 kB [ebuild R ] media-video/vlc-0.8.6i-r2 USE=X a52 alsa arts cdda cddb dc1394 dvd httpd libnotify live mp3 mpeg ncurses nsplugin ogg opengl png rtsp sdl sdl-image stream svg truetype vcd vorbis x264 xml xv (-3dfx) -aalib (-altivec) -avahi -bidi -corba -daap -debug -directfb -dts -dvb -esd -fbcon -flac -ggi -gnome -gnutls -hal* -jack -libcaca -lirc -matroska -modplug -musepack -optimisememory -oss -samba -seamonkey -shout -skins -speex (-svga) -theora -upnp -v4l -vlm (-win32codecs) -wxwindows -xinerama -xosd -xulrunner 11,522 kB [ebuild R ] media-gfx/gimp-2.4.6 USE=alsa curl dbus* doc exif gtkhtml lcms mmx mng pdf png python smp sse svg tiff wmf -aalib (-altivec) -debug -gnome -hal* 17,935 kB [ebuild NS ] kde-base/kate-4.1.2 [3.5.9] USE=plasma -debug -htmlhandbook -kdeprefix 4,793 kB [ebuild NS ] kde-base/kdeartwork-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] kde-base/kdeartwork-emoticons-4.1.2 [3.5.9] USE=-kdeprefix 41,367 kB [ebuild N] kde-base/kdeartwork-colorschemes-4.1.2 USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-kscreensaver-4.1.2 [3.5.9] USE=opengl -debug -kdeprefix -xscreensaver 0 kB [ebuild NS ] kde-base/kdeartwork-styles-4.1.2 [3.5.9] USE=-debug -kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-wallpapers-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-icewm-themes-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-sounds-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-kworldclock-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [nomerge ] kde-base/kdeutils-meta-4.1.2 [3.5.9] USE=-floppy [ebuild NS ]
Re: [gentoo-user] Trying KDE-4
On Thursday 23 October 2008 11:28:49 Peter Humphrey wrote: On Wednesday 22 October 2008 19:32:08 Daniel Pielmeier wrote: Please post again the output from emerge -pvutND world but attach it in a file so it doesn't get crippled by the mail program. Attached. Finally, we can see what you are running into. This is a stable box and you are trying to install latest kde:4 onto it right? emerge is trying to install qt-4.3.3 which is marked stable and conflicts with what kde-4.1.2 wants generate an autounmask for qt Also what I have seen from your previous tree output is that you are trying to do many things at one time. Upgrading to kde4 changing and changing many use flags. This makes debugging very hard. Try to do only one thing at a time That's only because one thing leads to another. All I wanted to do was to install KDE-4; everything else I've tried has been to enable that. Of course I do try to do only one thing at a time - I had half a lifetime of debugging of one kind or another. I started by running autounmask, as suggested by Neil B; that unmasked 81 packages. Then I tried to update world - 82 times: one for each other package that needed unmasking. At the end of that I had all the packages unmasked that were required for an upgrade to KDE-4, but I also had the blocker that started this conversation. I've been trying to find the conflict in dependencies ever since, with your help - thanks again. Here's another titbit: $ equery d '=x11-libs/qt-4.4.0_alpha:4' [ Searching for packages depending on =x11-libs/qt-4.4.0_alpha:4... ] app-text/poppler-bindings-0.8.7 (qt4? =x11-libs/qt-4.3:4) x11-libs/qscintilla-2.1-r1 (qt4? =x11-libs/qt-4.3*:4) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying KDE-4
2008/10/23 Alan McKinnon [EMAIL PROTECTED]: On Thursday 23 October 2008 11:28:49 Peter Humphrey wrote: On Wednesday 22 October 2008 19:32:08 Daniel Pielmeier wrote: Please post again the output from emerge -pvutND world but attach it in a file so it doesn't get crippled by the mail program. Attached. Finally, we can see what you are running into. This is a stable box and you are trying to install latest kde:4 onto it right? emerge is trying to install qt-4.3.3 which is marked stable and conflicts with what kde-4.1.2 wants generate an autounmask for qt I thought he already installed some of the qt split ebuilds so they should be unmasked, but let us see :-) -- Regards, Daniel
Re: [gentoo-user] Trying KDE-4
On Tuesday 21 October 2008 19:46:33 Daniel Pielmeier wrote: One thing I would give a try is to give portage a hand and emerge some of the qt split ebuilds with the oneshot option. In your case the qt split ebuilds which are blocked: x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2 and then see if portage will be able to continue with the world update. That was a good idea, one that I ought to have thought of but didn't. Unfortunately, it's made no difference at all. Emerge -upDvN world still gives the same block: [blocks B ] x11-libs/qt-core (x11-libs/qt-core is blocking x11-libs/qt-4.3.3) [blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4 is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) Total: 160 packages (3 upgrades, 78 new, 65 in new slots, 14 reinstalls), Size of downloads: 209,150 kB Conflict: 2 blocks (2 unsatisfied) To recap, the only version of qt installed is qt-3.3.8-r4, and equery d =x11-libs/qt-3.3.8-r4 returns 160 packages, all wanting =x11-libs/qt-3*. Emerge seems to think I have a version4.* of qt installed, but I haven't apart from the split e-builds I've just installed as above. $ equery l qt [ Searching for package 'qt' in all categories among: ] * installed packages [I--] [ ] app-emulation/emul-linux-x86-qtlibs-20071210 (0) [I--] [ ] dev-db/qt-unixODBC-3.3.8 (3) [I--] [ ] dev-libs/dbus-qt3-old-0.70 (0) [I--] [ ] sys-apps/qtparted-0.4.5 (0) [I--] [ ] x11-libs/qt-3.3.8-r4 (3) [I--] [ ~] x11-libs/qt-core-4.4.2 (4) [I--] [ ~] x11-libs/qt-dbus-4.4.2 (4) [I--] [ ~] x11-libs/qt-gui-4.4.2 (4) [I--] [ ~] x11-libs/qt-opengl-4.4.2 (4) [I--] [ ~] x11-libs/qt-qt3support-4.4.2 (4) [I--] [ ~] x11-libs/qt-script-4.4.2 (4) [I--] [ ~] x11-libs/qt-sql-4.4.2 (4) [I--] [ ~] x11-libs/qt-svg-4.4.2 (4) [I--] [ ~] x11-libs/qt-test-4.4.2 (4) [I--] [ ~] x11-libs/qt-webkit-4.4.2 (4) I could try removing qt-3.3.8-r4, but first I'd have to back up the whole system against the probability of being unable to recover from the resultant smashing of KDE 3.5. I've started building a new system from scratch on another disk, and I'm now about ready to start installing KDE on it. Maybe a clean start is what I need. I think this could be solved without a reinstall but it is up to you. Thanks for your help so far; I think though that I'll continue building the clean system as well in case your optimism proves unfounded. At least with two systems I can pursue both lines independently. -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
On Wed, 22 Oct 2008 10:15:34 +0100, Peter Humphrey wrote: That was a good idea, one that I ought to have thought of but didn't. Unfortunately, it's made no difference at all. Emerge -upDvN world still gives the same block: [blocks B ] x11-libs/qt-core (x11-libs/qt-core is blocking x11-libs/qt-4.3.3) [blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4 is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) Total: 160 packages (3 upgrades, 78 new, 65 in new slots, 14 reinstalls), Size of downloads: 209,150 kB Conflict: 2 blocks (2 unsatisfied) To recap, the only version of qt installed is qt-3.3.8-r4, Something you are trying to emerge as part of the world update depends on qt-4.3*, so it is trying to install 4.3 and 4.4, that's the cause of the block. Blocks aren't always the result of installed packages, only those that would be installed at the end of the emerge. I could try removing qt-3.3.8-r4, but first I'd have to back up the whole system against the probability of being unable to recover from the resultant smashing of KDE 3.5. qt3 seems to be unrelated to this, but a full backup is unnecessary. quickpkg qt3 before unmerging it. If the system goes TU you can emerge -k it. -- Neil Bothwick Nostalgia isn't what it used to be. signature.asc Description: PGP signature
Re: [gentoo-user] Trying KDE-4
On Wednesday 22 October 2008 11:15:34 Peter Humphrey wrote: On Tuesday 21 October 2008 19:46:33 Daniel Pielmeier wrote: One thing I would give a try is to give portage a hand and emerge some of the qt split ebuilds with the oneshot option. In your case the qt split ebuilds which are blocked: x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2 and then see if portage will be able to continue with the world update. That was a good idea, one that I ought to have thought of but didn't. Unfortunately, it's made no difference at all. Emerge -upDvN world still gives the same block: [blocks B ] x11-libs/qt-core (x11-libs/qt-core is blocking x11-libs/qt-4.3.3) [blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4 is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) Total: 160 packages (3 upgrades, 78 new, 65 in new slots, 14 reinstalls), Size of downloads: 209,150 kB Conflict: 2 blocks (2 unsatisfied) To recap, the only version of qt installed is qt-3.3.8-r4, and equery d =x11-libs/qt-3.3.8-r4 returns 160 packages, all wanting =x11-libs/qt-3*. Emerge seems to think I have a version4.* of qt installed, but I haven't apart from the split e-builds I've just installed as above. No, that is incorrect and your reading of the output is wrong. Emerge detects blockers by looking at what is currently on the machine or what it wants to install and seeing if that will block with what is on the machine or what will be installed. You do not have to have a package installed to create a block - it can be caused by something that is due to be emerged (and hence will only be installed in the future). Look at the second blocker line. It says: =x11-libs/qt-4.4.0_alpha:4 That means: - a version in SLOT 4 - the version number is less than 4.4.0_alpha is blocking/blocked by qt-4.4.2 You do not have such a package installed. That's cool. You need to find out why portage thinks it must install such a thing. That's why I asked you for emerge -t earlier. Find an entry for =x11-libs/qt-4.4.0_alpha:4 in that list and look above it to see what pulled it in. Fix that thing and portage will stop trying to pull in an old version of qt and your problem will go away. I earnestly recommend you do not go through a full reinstall. That will teach you nothing. You need to go through this at least once to learn how to deal with it, it's a necessary gentoo skill -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying KDE-4
Neil Bothwick writes: On Wed, 22 Oct 2008 10:15:34 +0100, Peter Humphrey wrote: That was a good idea, one that I ought to have thought of but didn't. Unfortunately, it's made no difference at all. Emerge -upDvN world still gives the same block: [...] To recap, the only version of qt installed is qt-3.3.8-r4, Something you are trying to emerge as part of the world update depends on qt-4.3*, so it is trying to install 4.3 and 4.4, that's the cause of the block. Blocks aren't always the result of installed packages, only those that would be installed at the end of the emerge. I could try removing qt-3.3.8-r4, but first I'd have to back up the whole system against the probability of being unable to recover from the resultant smashing of KDE 3.5. qt3 seems to be unrelated to this, but a full backup is unnecessary. quickpkg qt3 before unmerging it. If the system goes TU you can emerge -k it. I think I have the same conflict. I just solved it by putting this into package.keywords: ~dev-python/PyQt4-4.4.3 ~dev-python/sip-4.7.7 So I upgraded to PyQt4-4.4.3, and this depends on the splitted Qt ebuilds, while PyQt4 up to version 4.4-r1 wants the old monolithic Qt. weird ~ # grep x11-libs/qt /usr/portage/dev-python/PyQt4/*.ebuild /usr/portage/dev-python/PyQt4/PyQt4-4.3.3.ebuild:RDEPEND==x11-libs/qt-4.3* /usr/portage/dev-python/PyQt4/PyQt4-4.4-r1.ebuild:RDEPEND==x11-libs/qt-4* /usr/portage/dev-python/PyQt4/PyQt4-4.4.2.ebuild: =x11-libs/qt-core-4.4.0:4 /usr/portage/dev-python/PyQt4/PyQt4-4.4.3.ebuild: =x11-libs/qt-core-4.4.0:4 [...] Wonko
Re: [gentoo-user] Trying KDE-4
2008/10/22 Alex Schuster [EMAIL PROTECTED]: I think I have the same conflict. I just solved it by putting this into package.keywords: ~dev-python/PyQt4-4.4.3 ~dev-python/sip-4.7.7 So I upgraded to PyQt4-4.4.3, and this depends on the splitted Qt ebuilds, while PyQt4 up to version 4.4-r1 wants the old monolithic Qt. weird ~ # grep x11-libs/qt /usr/portage/dev-python/PyQt4/*.ebuild /usr/portage/dev-python/PyQt4/PyQt4-4.3.3.ebuild:RDEPEND==x11-libs/qt-4.3* /usr/portage/dev-python/PyQt4/PyQt4-4.4-r1.ebuild:RDEPEND==x11-libs/qt-4* /usr/portage/dev-python/PyQt4/PyQt4-4.4.2.ebuild: =x11-libs/qt-core-4.4.0:4 /usr/portage/dev-python/PyQt4/PyQt4-4.4.3.ebuild: =x11-libs/qt-core-4.4.0:4 [...] This is maybe the PyQt issue I did not remember. So I think it is worth a try. If this is the case portage tries to pull qt-4.4.3 because it is needed by PyQt-4.4 plus the qt split ebuilds which are needed by some other packages. So putting versions of PyQt and sip in package.keywords which depemd on qt split ebuilds should solve it. If I remember right I have this entries in my package.keywords too. Probably you need oneshot for PyQt and sip too. -- Regards, Daniel
Re: [gentoo-user] Trying KDE-4
On Wednesday 22 October 2008 12:10:15 Daniel Pielmeier wrote: 2008/10/22 Alex Schuster [EMAIL PROTECTED]: I think I have the same conflict. I just solved it by putting this into package.keywords: ~dev-python/PyQt4-4.4.3 ~dev-python/sip-4.7.7 [...] This is maybe the PyQt issue I did not remember. So I think it is worth a try. If this is the case portage tries to pull qt-4.4.3 because it is needed by PyQt-4.4 plus the qt split ebuilds which are needed by some other packages. So putting versions of PyQt and sip in package.keywords which depemd on qt split ebuilds should solve it. If I remember right I have this entries in my package.keywords too. Probably you need oneshot for PyQt and sip too. I've found another way around it on my fresh test system. I had a working KDE-3.5 system installed on it and upgraded it to version 4, no problem. Then I tried to install hplip on it and got the same blockers again. By a process of elimination I found I had to put two entries in package.use: =dev-python/qscintilla-python-2.1 -qt4 =x11-libs/qscintilla-2.1-r1 -qt4 Then I could install hplip as well. Now I'm back on the original system, and putting Alex's package.keywords entries in I find I still have the blockers; his solution isn't working for me, even after reinstalling PyQt4 and sip. Neither is my own on this system. But then I'm getting what looks like nonsense from equery, thus: # equery h qt4 [ Searching for USE flag qt4 in all categories among: ] * installed packages [I--] [ ] dev-python/qscintilla-python-2.1 (0) [I--] [ ] net-print/hplip-2.8.6b (0) [I--] [ ] x11-libs/qscintilla-2.1-r1 (0) [I--] [ ] app-text/poppler-bindings-0.8.7 (0) ...but equery u qscintilla and equery u qscintilla-python both return this line: - - qt4 : Adds support for the Qt GUI/Application Toolkit version 4.x So unless I'm misunderstanding the output of equery as well, the qt4 USE flag both is and is not in use in the two scintilla packages. After writing the above, I uninstalled hplip and poppler-bindings, then reinstalled poppler-bindings and ran revdep-rebuild. That hasn't helped either. -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
Peter Humphrey schrieb am 22.10.2008 18:42: Now I'm back on the original system, and putting Alex's package.keywords entries in I find I still have the blockers; his solution isn't working for me, even after reinstalling PyQt4 and sip. Neither is my own on this system. But then I'm getting what looks like nonsense from equery, thus: # equery h qt4 [ Searching for USE flag qt4 in all categories among: ] * installed packages [I--] [ ] dev-python/qscintilla-python-2.1 (0) [I--] [ ] net-print/hplip-2.8.6b (0) [I--] [ ] x11-libs/qscintilla-2.1-r1 (0) [I--] [ ] app-text/poppler-bindings-0.8.7 (0) ...but equery u qscintilla and equery u qscintilla-python both return this line: - - qt4 : Adds support for the Qt GUI/Application Toolkit version 4.x So unless I'm misunderstanding the output of equery as well, the qt4 USE flag both is and is not in use in the two scintilla packages. Why is this nonsense? equery h shows which installed packages have the given use flag regardless if it is set or not. equery u shows you which use flags are set or unset for the given package. After writing the above, I uninstalled hplip and poppler-bindings, then reinstalled poppler-bindings and ran revdep-rebuild. That hasn't helped either. Please post again the output from emerge -pvutND world but attach it in a file so it doesn't get crippled by the mail program. Also what I have seen from your previous tree output is that you are trying to do many things at one time. Upgrading to kde4 changing and changing many use flags. This makes debugging very hard. Try to do only one thing at a time Regards, Daniel
Re: [gentoo-user] Trying KDE-4
On Monday 20 October 2008 13:08:30 Daniel Pielmeier wrote: Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split ebuilds can not live alongside the non split ebuild. I ran quickpkg and emerge -C on qt-4.3.3, then emerge -upDvN world again. The block is still there, exactly the same as before. I've started building a new system from scratch on another disk, and I'm now about ready to start installing KDE on it. Maybe a clean start is what I need. -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
Peter Humphrey schrieb am 21.10.2008 11:07: On Monday 20 October 2008 13:08:30 Daniel Pielmeier wrote: Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split ebuilds can not live alongside the non split ebuild. I ran quickpkg and emerge -C on qt-4.3.3, then emerge -upDvN world again. The block is still there, exactly the same as before. Let me quote Alan here: I main underlying reason seems to be that Qt now comes as split-ebuilds and Peter has some monolithic ones installed. It's similar to migrating KDE to split-ebuilds, but on a much smaller scale. Unfortunately there's no easy way to automate this in an ebuild, that would require several new unrelated packages replacing one big one, portage doesn't support that kind of thing. So one has to do it manually, and deal with the resulting recdep-rebuild issues as well The problem is that portage is probably not smart enough to do the upgrade from the non-split to the split ebuilds, so the world update will always run into this blocker even when qt-4.3.3 is not installed. Maybe some ebuild depends on =qt-4.3.3 so it is pulled in and another one depends on =qt-4.4.x which also gets pulled in and thus the blockers. This should be no problem in the normal case as the highest needed version would be installed. But the new split ebuilds have no relation to the old monolithic which is probably causing the problems in this case. The highest available version for monolithic is qt-4.3.3 and so it is pulled in alongside the new split ebuilds which are also needed because of a =4.4.x dependency of other programs. I remember such problems to when migrating to qt split ebuilds and simply running emerge world was not enough but I do not remember the exact procedure which solved this. There were some issues with PyQt4 but I am not sure if this was related. One thing I would give a try is to give portage a hand and emerge some of the qt split ebuilds with the oneshot option. In your case the qt split ebuilds which are blocked: x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2 and then see if portage will be able to continue with the world update. I've started building a new system from scratch on another disk, and I'm now about ready to start installing KDE on it. Maybe a clean start is what I need. I think this could be solved without a reinstall but it is up to you. Regards, Daniel
Re: [gentoo-user] Trying KDE-4
On Sunday 19 October 2008 18:52:49 Alan McKinnon wrote: I main underlying reason seems to be that Qt now comes as split-ebuilds and Peter has some monolithic ones installed. It's similar to migrating KDE to split-ebuilds, but on a much smaller scale. Unfortunately there's no easy way to automate this in an ebuild, that would require several new unrelated packages replacing one big one, portage doesn't support that kind of thing. So one has to do it manually, and deal with the resulting recdep-rebuild issues as well Does that mean I have to uninstall PyQt and let KDE-4 pull it back in? -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
On Sunday 19 October 2008 16:28:35 Alan McKinnon wrote: Repost the output of your emerge command using the -t option. Tip: tricky blockers often require that you post the output of 'emerge -t'. Otherwise all we know is THAT you have a block and no way to determine WHY it's happening. If you are going to post emerge output, it's a excellent habit to do it with -t You're right. Here it is* (you did ask :): # USE=dbus qt4 emerge -upDvNt world These are the packages that would be merged, in reverse order: Calculating dependencies . . done! [ebuild NS ] kde-base/kdebase-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] kde-base/kdegraphics-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] kde-base/kdemultimedia-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] kde-base/kdeutils-meta-4.1.2 [3.5.9] USE=-floppy 0 kB [ebuild NS ] kde-base/kate-4.1.2 [3.5.9] USE=plasma -debug -htmlhandbook -kdeprefix 4,793 kB [ebuild NS ] kde-base/kdeartwork-meta-4.1.2 [3.5.9] 0 kB [ebuild NS ] kde-base/kdeartwork-emoticons-4.1.2 [3.5.9] USE=-kdeprefix 41,367 kB [ebuild N] kde-base/kdeartwork-colorschemes-4.1.2 USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-kscreensaver-4.1.2 [3.5.9] USE=opengl -debug -kdeprefix -xscreensaver 0 kB [ebuild NS ] kde-base/kdeartwork-styles-4.1.2 [3.5.9] USE=-debug -kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-wallpapers-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-icewm-themes-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-sounds-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdeartwork-kworldclock-4.1.2 [3.5.9] USE=-kdeprefix 0 kB [nomerge ] kde-base/kdeutils-meta-4.1.2 [3.5.9] USE=-floppy [ebuild NS ] kde-base/kjots-4.1.2 [3.5.9] USE=kontact -debug -htmlhandbook -kdeprefix 12,860 kB [ebuild N] kde-base/kontactinterfaces-4.1.2 USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild NS ] kde-base/libkdepim-4.1.2 [3.5.9] USE=-debug -kdeprefix 0 kB [ebuild NS ] kde-base/ktimer-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix 2,230 kB [ebuild NS ] kde-base/kcharselect-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/kdessh-4.1.2 USE=-debug -kdeprefix 0 kB [ebuild NS ] kde-base/superkaramba-4.1.2 [3.5.9] USE=python -debug -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/kwallet-4.1.2 USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild NS ] kde-base/ark-4.1.2 [3.5.9] USE=archive zip -debug -htmlhandbook -kdeprefix 0 kB [ebuild NS ] kde-base/kdf-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/sweeper-4.1.2 USE=-debug -kdeprefix 0 kB [ebuild NS ] kde-base/kgpg-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/okteta-4.1.2 USE=-debug -kdeprefix 0 kB [nomerge ] kde-base/kdemultimedia-meta-4.1.2 [3.5.9] [ebuild NS ] kde-base/kmix-4.1.2 [3.5.9] USE=alsa -debug -htmlhandbook -kdeprefix 1,410 kB [ebuild NS ] kde-base/juk-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix -tunepimp 0 kB [ebuild N] kde-base/dragonplayer-4.1.2 USE=-kdeprefix 0 kB [ebuild NS ] kde-base/kdemultimedia-kioslaves-4.1.2 [3.5.9] USE=vorbis -debug -encode -flac -kdeprefix 0 kB [ebuild NS ] kde-base/kdebase-startkde-4.1.2-r1 [3.5.9] USE=-kdeprefix 46,387 kB [ebuild N] kde-base/plasma-apps-4.1.2 USE=-debug -htmlhandbook -kdeprefix 4,297 kB [ebuild NS ] kde-base/kwin-4.1.2 [3.5.9-r1] USE=opengl -captury -debug -kdeprefix -xcomposite -xinerama 0 kB [ebuild N] kde-base/systemsettings-4.1.2 USE=opengl usb -debug -htmlhandbook -kdeprefix -xinerama 0 kB [ebuild N] kde-base/knotify-4.1.2 USE=-debug -kdeprefix 50,977 kB [ebuild NS ] kde-base/kreadconfig-4.1.2 [3.5.9] USE=-debug -kdeprefix 0 kB [ebuild N] kde-base/kstyles-4.1.2 USE=-kdeprefix 0 kB [ebuild N] kde-base/kstartupconfig-4.1.2 USE=-debug -kdeprefix 0 kB [ebuild N] kde-base/krunner-4.1.2 USE=opengl -debug -kdeprefix -xcomposite -xscreensaver 0 kB [ebuild N] kde-base/kde-wallpapers-4.1.2 USE=-kdeprefix 0 kB [nomerge ] kde-base/kdegraphics-meta-4.1.2 [3.5.9] [ebuild N] kde-base/kdegraphics-strigi-analyzer-4.1.2 USE=-debug -kdeprefix 3,355 kB [ebuild NS ] kde-base/kgamma-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/libkexiv2-4.1.2 USE=-kdeprefix 0 kB [ebuild N] kde-base/svgpart-4.1.2 USE=-debug -kdeprefix 0 kB [ebuild N] kde-base/libkdcraw-4.1.2 USE=-kdeprefix 0 kB [ebuild N] kde-base/gwenview-4.1.2 USE=semantic-desktop -debug -htmlhandbook -kdeprefix -kipi 0 kB [ebuild NS ] kde-base/kamera-4.1.2 [3.5.9] USE=-debug -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/okular-4.1.2 USE=jpeg pdf tiff -chm -debug -djvu -htmlhandbook -kdeprefix 0 kB [ebuild N] kde-base/libkipi-4.1.2 USE=-kdeprefix 0 kB [ebuild N] kde-base/kcolorchooser-4.1.2 USE=-debug
Re: [gentoo-user] Trying KDE-4
Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split ebuilds can not live alongside the non split ebuild. -- Regards, Daniel
Re: [gentoo-user] Trying KDE-4
On Monday 20 October 2008 09:46:56 Peter Humphrey wrote: On Sunday 19 October 2008 18:52:49 Alan McKinnon wrote: I main underlying reason seems to be that Qt now comes as split-ebuilds and Peter has some monolithic ones installed. It's similar to migrating KDE to split-ebuilds, but on a much smaller scale. Unfortunately there's no easy way to automate this in an ebuild, that would require several new unrelated packages replacing one big one, portage doesn't support that kind of thing. So one has to do it manually, and deal with the resulting recdep-rebuild issues as well Does that mean I have to uninstall PyQt and let KDE-4 pull it back in? Sorry - I hadn't checked. The only version I have is 3.17.4, so removing it seems unlikely to help. -- Rgds Peter
[gentoo-user] Trying KDE-4
Having been inspired by messages here extolling the virtues of KDE-4, I tried installing it. I did as Neil B said and autounmasked kde-meta-4.1.2, but I still have a couple of show-stoppers. After running autounmask, I had 81 new entries in package.keywords, but I had to add another 82 myself after that many attempts to emerge -uaDvN world. Even so, I now have five blockers. Three of them I can clear by unmerging old package versions, but that leaves me with these two: [blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4 is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) [blocks B ] x11-libs/qt-core (x11-libs/qt-core is blocking x11-libs/qt-4.3.3) The first of these implies that I have to unmerge qt-3.*, which I assume would smash the system into tiny pieces, while the second just looks nonsensical to me. Can anyone see anything obvious here that I can fix? -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
I think I had the similar blocks while upgrading my kde from 3.5.x to 4.1.2, I just unmerged x11-libs/qt-core then everything seemed to be fine. -Weifeng On Sun, Oct 19, 2008 at 9:54 PM, Peter Humphrey [EMAIL PROTECTED]wrote: Having been inspired by messages here extolling the virtues of KDE-4, I tried installing it. I did as Neil B said and autounmasked kde-meta-4.1.2, but I still have a couple of show-stoppers. After running autounmask, I had 81 new entries in package.keywords, but I had to add another 82 myself after that many attempts to emerge -uaDvN world. Even so, I now have five blockers. Three of them I can clear by unmerging old package versions, but that leaves me with these two: [blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4 is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) [blocks B ] x11-libs/qt-core (x11-libs/qt-core is blocking x11-libs/qt-4.3.3) The first of these implies that I have to unmerge qt-3.*, which I assume would smash the system into tiny pieces, while the second just looks nonsensical to me. Can anyone see anything obvious here that I can fix? -- Rgds Peter
Re: [gentoo-user] Trying KDE-4
On Sunday 19 October 2008 15:54:24 Peter Humphrey wrote:
Having been inspired by messages here extolling the virtues of KDE-4, I
tried installing it. I did as Neil B said and autounmasked kde-meta-4.1.2,
but I still have a couple of show-stoppers.
After running autounmask, I had 81 new entries in package.keywords, but I
had to add another 82 myself after that many attempts to emerge -uaDvN
world.
Even so, I now have five blockers. Three of them I can clear by unmerging
old package versions, but that leaves me with these two:
[blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4
is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2,
x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2,
x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2,
x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2)
[blocks B ] x11-libs/qt-core (x11-libs/qt-core is blocking
x11-libs/qt-4.3.3)
The first of these implies that I have to unmerge qt-3.*, which I assume
would smash the system into tiny pieces, while the second just looks
nonsensical to me.
Can anyone see anything obvious here that I can fix?
e
From the qt-core-4.4.2 ebuild:
RDEPEND=
!=x11-libs/qt-4.4.0_alpha:${SLOT}
Te first blocker you have does NOT refer to any version less than 4.4.0_alpha,
it means any version less than that which is SLOT=4.
Fixing this is simple:
unmerge the existing qt:4
merge qt:4
They all co-exist nicely with qt-3:
nazgul x11-libs # eix -e qt
[I] x11-libs/qt
Available versions:
(3) 3.3.8-r4 (~)3.3.8b
(4) 4.3.3 (~)4.3.4-r1 (~)4.3.5 [M](~)4.4.0 (~)4.4.1 (~)4.4.1-r1
(~)4.4.2
{accessibility cups dbus debug doc examples firebird gif glib immqt
immqt-bc input_devices_wacom ipv6 jpeg mng mysql nas nis odbc opengl pch png
postgres qt3support sqlite sqlite3 ssl tiff xinerama zlib}
Installed versions: 3.3.8b(3)(18:45:41 10/12/08)(cups opengl
xinerama -debug -doc -examples -firebird -immqt -immqt-bc -ipv6 -mysql -nas
-nis -odbc -postgres -sqlite)
4.4.2(4)(22:55:09 09/23/08)(dbus opengl qt3support)
Homepage:http://www.trolltech.com/
Description: The Qt toolkit is a comprehensive C++ application
development framework.
nazgul x11-libs # eix -e qt-core
[I] x11-libs/qt-core
Available versions: (4) [M](~)4.4.0 (~)4.4.1 (~)4.4.1-r1 (~)4.4.2
{debug doc glib pch qt3support ssl}
Installed versions: 4.4.2(4)(23:35:51 09/22/08)(pch qt3support
ssl -debug -doc -glib)
Homepage:http://www.trolltech.com/
Description: The Qt toolkit is a comprehensive C++ application
development framework.
--
alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying KDE-4
On Sunday 19 October 2008 15:24:45 Alan McKinnon wrote:
From the qt-core-4.4.2 ebuild:
RDEPEND=
!=x11-libs/qt-4.4.0_alpha:${SLOT}
[The] first blocker you have does NOT refer to any version less than
4.4.0_alpha, it means any version less than that which is SLOT=4.
I thought that too, but I have only version 3.3.8-r4 of qt on the system. A
version 4.x may have existed some months ago, but not since then.
Fixing this is simple:
unmerge the existing qt:4
Which I can't do, as I said above.
merge qt:4
I'm doing this now; I'll see if it clears the blocks - thanks.
--
Rgds
Peter
Re: [gentoo-user] Trying KDE-4
Peter Humphrey schrieb am 19.10.2008 16:50:
On Sunday 19 October 2008 15:24:45 Alan McKinnon wrote:
From the qt-core-4.4.2 ebuild:
RDEPEND=
!=x11-libs/qt-4.4.0_alpha:${SLOT}
[The] first blocker you have does NOT refer to any version less than
4.4.0_alpha, it means any version less than that which is SLOT=4.
I thought that too, but I have only version 3.3.8-r4 of qt on the system. A
version 4.x may have existed some months ago, but not since then.
Fixing this is simple:
unmerge the existing qt:4
Which I can't do, as I said above.
merge qt:4
I'm doing this now; I'll see if it clears the blocks - thanks.
I hope you compile the qt split ebuilds 4.4.2, if not I you probably
will run into blockers again.
Re: [gentoo-user] Trying KDE-4
Alan McKinnon writes: Repost the output of your emerge command using the -t option. Tip: tricky blockers often require that you post the output of 'emerge -t'. Otherwise all we know is THAT you have a block and no way to determine WHY it's happening. If you are going to post emerge output, it's a excellent habit to do it with -t I had the same experience as Peter. Looks like it's PyQt. I have it in world, no idea why, maybe I forgot the -1 switch once. Anyway, equery also lists it as a dependency of amarok-1.4.10 (when the python use flag is set). And it's another dependency of qscintilla-python, when the qt4 use flag is not set (for me, it is). I do not know how to solve this, but did not yet try hard to do so. I'm installing KDE 4.1 on a remote machine I do not have physical access to yet, so it's no showstopper for me. Yet :) Wonko
Re: [gentoo-user] Trying KDE-4
On Sunday 19 October 2008 19:32:42 Alex Schuster wrote: Alan McKinnon writes: Repost the output of your emerge command using the -t option. Tip: tricky blockers often require that you post the output of 'emerge -t'. Otherwise all we know is THAT you have a block and no way to determine WHY it's happening. If you are going to post emerge output, it's a excellent habit to do it with -t I had the same experience as Peter. Looks like it's PyQt. I have it in world, no idea why, maybe I forgot the -1 switch once. Anyway, equery also lists it as a dependency of amarok-1.4.10 (when the python use flag is set). And it's another dependency of qscintilla-python, when the qt4 use flag is not set (for me, it is). That sounds familiar. I had some issue with PyQt recently. I've also had many issues with many packages recently, so I forget the details very quickly. I do not know how to solve this, but did not yet try hard to do so. I'm installing KDE 4.1 on a remote machine I do not have physical access to yet, so it's no showstopper for me. Yet :) I main underlying reason seems to be that Qt now comes as split-ebuilds and Peter has some monolithic ones installed. It's similar to migrating KDE to split-ebuilds, but on a much smaller scale. Unfortunately there's no easy way to automate this in an ebuild, that would require several new unrelated packages replacing one big one, portage doesn't support that kind of thing. So one has to do it manually, and deal with the resulting recdep-rebuild issues as well -- alan dot mckinnon at gmail dot com
