emerge -uD world halts becauseCalculating dependencies ...done! [blocks B ] <=x11-themes/gnome-themes-2.8.2 (is blocking x11-themes/gtk-engines-2.6.3) even though: [ebuild U ] sys-devel/gcc-config-1.3.11 [1.3.10-r2] [ebuild U ] dev-libs/atk-1.9.1 [1.8.0-r1] [ebuild U ] x11-misc/shared-mime-info-0.16 [0.14-r2] [ebuild U ] x11-libs/gtk+-2.6.7 [2.6.4-r1] [ebuild U ] x11-themes/gtk-engines-2.6.3 [2.2.0] [ebuild U ] x11-themes/gnome-themes-2.10.0 [2.8.2] it seems to want to do it OK. Reproducible: Always Steps to Reproduce: 1. emerge -uD gnome-themes or gtk-engines 2. 3. Actual Results: !!! Error: the <=x11-themes/gnome-themes-2.8.2 package conflicts with another package. !!! both can't be installed on the same system together. !!! Please use 'emerge --pretend' to determine blockers. Expected Results: packages emerge root@mars /home/peter # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11.10 i686) ================================================================= System uname: 2.6.11.10 i686 AMD Athlon(tm) XP 2800+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Apr 28 2005, 06:48:52)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.7.9-r1, 1.5, 1.9.5, 1.6.3, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.11-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/mnt/src/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://gentoo.mirrors.tds.net/gentoo http://mirror.clarkson.edu/pub/distributions/gentoo/ ftp://206.75.217.180/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts artswrappersuid avi berkdb bitmap-fonts cdr crypt cups curl eds emboss encode esd fam flac foomaticdb fortran gd gdbm gif gnome gpm gtk gtk2 imagemagick imlib ipv6 java jpeg kde ldap libg++ libwww mad mikmod motif mozilla mp3 mpeg mysql ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl slang spell ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts vorbis xine xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
In gtk-engines-2.6.3.ebuild DEPEND="${DEPEND} .... !<=x11-themes/gnome-themes-2.8.2" This is the blocker here, Because g-t 2.8.2 IS installed, it IS <= 2.8.2 and therefore creates the block. Changing it to !<...2.8.2 creates warnings such as: root@mars /usr/portage/x11-themes/gtk-engines # emerge -puD gnome-themes These are the packages that I would merge, in order: Calculating dependencies \QA Notice: has_version() in global scope: eclass gtk-engines2 QA Notice: has_version() in global scope: eclass gtk-engines2 QA Notice: has_version() in global scope: eclass gtk-engines2 QA Notice: sed in global scope: x11-themes/gtk-engines-2.6.3 ...done! [ebuild U ] sys-devel/gcc-config-1.3.11 [1.3.10-r2] [ebuild U ] dev-libs/atk-1.9.1 [1.8.0-r1] [ebuild U ] x11-misc/shared-mime-info-0.16 [0.14-r2] [ebuild U ] x11-libs/gtk+-2.6.7 [2.6.4-r1] [ebuild U ] x11-themes/gtk-engines-2.6.3 [2.2.0] [ebuild U ] x11-themes/gnome-themes-2.10.0 [2.8.2] So, I'm going to wait and see!
this is not a bug, this is intended behaviour. Those 2 packs just don't go together, you need a newer gnome-themes.
Then why? root@mars /home/peter # emerge -pu gnome-themes These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] <=x11-themes/gnome-themes-2.8.2 (is blocking x11-themes/gtk-engines-2.6.3) [ebuild U ] dev-libs/atk-1.9.1 [1.8.0-r1] [ebuild U ] x11-misc/shared-mime-info-0.16 [0.14-r2] [ebuild U ] x11-libs/gtk+-2.6.7 [2.6.4-r1] [ebuild U ] x11-themes/gtk-engines-2.6.3 [2.2.0] [ebuild U ] x11-themes/gnome-themes-2.10.0 [2.8.2] respectfully reopening.
(In reply to comment #1) > Changing it to !<...2.8.2 creates warnings such as: > > QA Notice: has_version() in global scope: eclass gtk-engines2 Those warnings are IMHO related to the infamous Bug 24439.
Theres nothing wrong there either, I can't help portage isn't smarter than that (well, i'm not sure it can be in this particular case). Just do as it asks and you will be fine. It is still not a bug.
Cannot do what it asks because updating gnome-themes fails. Viz: root@mars /home/peter # emerge -u gnome-themes Calculating dependencies ...done! !!! Error: the <=x11-themes/gnome-themes-2.8.2 package conflicts with another package. !!! both can't be installed on the same system together. !!! Please use 'emerge --pretend' to determine blockers. root@mars /home/peter # emerge -u gtk-engines Calculating dependencies ...done! !!! Error: the <=x11-themes/gnome-themes-2.8.2 package conflicts with another package. !!! both can't be installed on the same system together. !!! Please use 'emerge --pretend' to determine blockers. So, either way, I can't update EITHER package. What's the way out of this? Thx
*** Bug 95245 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > So, either way, I can't update EITHER package. What's the way out of this? Thx You need to unmerge the offending package...
In reply to comment #8 I did remove gtk-engines, and then when I emerge -uDp world, it tries to install it as a new package and the dependency circle as discussed above continues.
both gnome-themes and gtk-engines need to be removed. Then they will both be emerged properly. Something is not right, but this works. HTH
Let me stress this once again (see comment #2 & #5) it's perfectly alright & expected behaviour and no, there is not another way to do this.
I respectfully disagree. Having circular blocks should never be acceptable.One way or the other should work.
It's not circular, maybe you should investigate the matter to a level of sufficient insight before you make unfounded claims. Thank you.
*** Bug 95829 has been marked as a duplicate of this bug. ***
*** Bug 96378 has been marked as a duplicate of this bug. ***