Each time I run 'emerge -uD world' the autoconf packages are re-emerged. If v2.57a is installed then v2.57-r1 wants to be installed and the other way round. Reproducible: Always Steps to Reproduce: 1. emerge -upD world 2. look at the list 3. emerge -uD world Actual Results: The installed version of autoconf is replaced. Expected Results: The right version (whichever that is) should remain installed. Portage 2.0.49-r7 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.20-gentoo-r5) ================================================================= System uname: 2.4.20-gentoo-r5 i686 AMD Athlon(tm) XP 2200+ distcc 2.11 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.2 [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/portage.ryttargarden/distfiles" FEATURES="sandbox autoaddcvs ccache distcc" GENTOO_MIRRORS="http://ds.thn.htu.se/linux/gentoo http://gentoo.linux.no/ http:/ /gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://portage.ryttargarden/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ libwww mad mik mod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib a lsa gdbm berkdb slang readline arts svga java X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis qt kde motif opengl mozilla gphoto2 cdr scanner dvd emacs j ikes joystick pda sse tiff usb -gnome -gtk"
I get the same response on my machine. I did not have this until I added ACCEPT_KEYWORDS="~x86" to my make.globals file. Might this have affected it?
I think portage should handle that. BTW! You should not tamper with the make.globals file, edit make.conf instead!
This is because KDE won't work with autoconf 2.57a, so it has a dependency to work with a lower version. but portage wants to upgrade to 2.57a. I don't know a way around this via portage, but this is just to let you know where the problem is coming from. the solution in the meantime is to mask autoconf 2.57a in package.mask so it won't continue doing this.
Azarah: according to the autoconf site, 2.57a is recommended for use with libtool 1.5 only, and 1.4 is not supported anymore. 1.4 is all that's in portage, however.
Oops, I rescend that. It's just encouraged for you to use 1.5, but not required (1.4 should work). My apologies.
same problem here too
I also can confirm this problem. I have KDE 3.1.4 installed and am using ~x86.
*** Bug 30529 has been marked as a duplicate of this bug. ***
As suggested above, create the file/directory: /etc/portage/package.mask. Insert the following line in package.mask: "=sys-devel/autoconf-2.57a".
seems to be a portage issue
caleb: can you verify that 2.57a-r1 of autoconf fixes this ? and if so update the DEPEND so we dont get this loop anymore ?
It works for me now with autoconf-2.57a-r1, so I removed this dependency. I'll close this bug as it shouldn't be valid anymore, and will repoen a new one if this breaks again.
