During a deep/newuse upgrade of the world package tree libcdio repeatedly wishes to be upgraded, then downgraded, requiring I compile it every time I wish to upgrade the world tree. Reproducible: Always Steps to Reproduce: mbevan@pan mbevan $ sudo emerge -uDN -ptv world These are the packages that I would merge, in reverse order: Calculating world dependencies ...done! [nomerge ] app-cdr/k3b-0.11.23-r2 +arts -debug +dvdr +encode +flac +kde -kdeenablefinal +mad +oggvorbis +xinerama [nomerge ] media-video/vcdimager-0.7.20-r2 +xml2 [ebuild U ] dev-libs/libcdio-0.73 [0.70] -cddb -minimal 0 kB Total size of downloads: 0 kB mbevan@pan mbevan $ sudo emerge -uDN world ... mbevan@pan mbevan $ sudo emerge -uDN -ptv world s These are the packages that I would merge, in reverse order: Calculating world dependencies ...done! [nomerge ] app-cdr/k3b-0.11.23-r2 +arts -debug +dvdr +encode +flac +kde -kdeenablefinal +mad +oggvorbis +xinerama [nomerge ] media-video/vcdimager-0.7.20-r2 +xml2 [ebuild UD] dev-libs/libcdio-0.70 [0.73] -cddb 0 kB Total size of downloads: 0 kB Actual Results: Upgrade is compiled and installed, then downgrade is compiled and installed. Rinse, repeat. Expected Results: Upgrade once, then no more. I have unmasked k3b and libcdio in my /etc/portage/package.keywords file as so: app-cdr/k3b ~amd64 dev-libs/libcdio ~amd64 I was not required to unmask vcdimager.
My emerge info output is: Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r7-pan-r2 x86_64) ================================================================= System uname: 2.6.11-gentoo-r7-pan-r2 x86_64 AMD Athlon(tm) 64 Processor 3400+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 13 2005, 13:46:37)] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r8 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O3 -pipe -fomit-frame-pointer" CHOST="x86_64-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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox strict" GENTOO_MIRRORS="ftp://gentoo.ccccom.com/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 3dnowext X aalib acpi alsa apic arts avi berkdb bitmap-fonts bzip2 cdparanoia cdr cdrw crypt cups curl dv dvb dvd dvdr dvdread encode exif fam flac font-server fortran gif gimpprint gpm gtk gtk2 gtkhtml hal imagemagick imlib ipv6 java jp2 jpeg kde lcms ldap lzw lzw-tiff mad matroska mng motif mozsvg mp3 mpeg mysql ncurses network nls nvidia offensive ogg oggvorbis opengl oss pam pda perl pic png postgres ppds prelink python qt readline rtc samba sdl sqlite ssl svg tcpd theora tiff truetype truetype-fonts type1-fonts usb userlocales utf8 vorbis wmf xanim xinerama xml2 xpm xrandr xscreensaver xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
(In reply to comment #0) >I have unmasked k3b and libcdio in my /etc/portage/package.keywords file as so: >app-cdr/k3b ~amd64 >dev-libs/libcdio ~amd64 >I was not required to unmask vcdimager. Why did you unmask dev-libs/libcdio? Current stable vcdimager requires <dev-libs/libcdio-0.70
Err, <=dev-libs/libcdio-0.70
Strangely enough, even if I remove the unmask line in package.keywords my system attempts to upgrade to 0.73, then downgrade to 0.70. The circular reference continues. If vcdimager requires <=dev-libs/libcdio-0.70, why can 0.73 be installed at all?
Don
Don´t mix ~arch and stable. Which packages do depend on 0.73 that you had to unmask it? Do you have the same problem if you don´t unmask k3b?
Downgrading libcdio or updating to vcdimager-0.7.21 will fix this. But this is not a bug. When you use ebuilds marked testing, you should be able to figure out such cycles yourself. This can happen all time.
