when doing "emerge -auDv world" portage writes a number of messages and use flags, which looks "unprofessional". I suspect this is not as much a bug in portage as buglets in various ebuilds, so I will attach my world file. Reproducible: Always Steps to Reproduce: 1. emerge -auDv world 2. 3. Actual Results: b307-213 root # emerge -auD world These are the packages that I would merge, in order: Calculating world dependencies /ssl alsa cups x86 |QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.9 python QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.4 python QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.6 python QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.9-r1 python QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.8 python QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.3 python QA Notice: USE Flag 'python' not in IUSE for dev-libs/libxslt-1.1.8-r1 python /tetex -motif encode cups oggvorbis opengl ssl pam |opengl -sdl xmms sdl xmms sdl xmms sdl xmms sdl xmms \motif slang tcltk oggvorbis cdr -pam ...done! [ebuild U ] sys-apps/baselayout-1.9.4-r5 [1.9.4-r3] [ebuild FU ] dev-java/sun-jdk-1.4.2.06 [1.4.2.05] Do you want me to merge these packages? [Yes/No] Expected Results: b307-213 root # emerge -auD world These are the packages that I would merge, in order: Calculating world dependencies / ...done! [ebuild U ] sys-apps/baselayout-1.9.4-r5 [1.9.4-r3] [ebuild FU ] dev-java/sun-jdk-1.4.2.06 [1.4.2.05] Do you want me to merge these packages? [Yes/No] b307-213 root # emerge info Portage 2.0.51 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8.1 i686) ================================================================= System uname: 2.6.8.1 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/var/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/ ftp://trumpetti.atm.tut.fi/gentoo/ ftp://ftp.rhnet.is/pub/gentoo/ ftp://gd.tuwien.ac.at/opsys/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/var/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X Xaw3d acpi alsa arts atlas avi berkdb bitmap-fonts cdr crypt cups dga dvd emacs encode f77 fam foomaticdb gdbm gif gpm gtk gtk2 imap imlib java jpeg kde libg++ libwww mad maildir mbox mikmod motif mozilla mpeg mule ncurses netcdf nls nptl oggvobis oggvorbis opengl oss pam pcmcia pdflib perl png pnp ppds python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype trusted usb wxwindows x86 xml2xmms xprint xv xvid zlib" b307-213 root #
Created attachment 42296 [details] /var/lib/portage/world My world file, in case it is relevant.
Oops, my "reproducible" is wrong! After doing it once, the "garbage" does not appear next time. So it is probably _not_ related to this portage version. I will ressolve my own bug as invalid. Sorry about this! /Jakob
The reason it's not reproducable, is that the ebuilds are sourced -once- for the cache when a change has been detected. Regarding unprofessional, well, the ebuilds have issues- they aren't abiding by the strict (getting stricter) qa rules. The ebuilds have issues, not portage.
Yes, thanks for the explanation - I guessed it was something like that. And sorry about the "unprofessional" part, I did not want to sound negative, I just wanted to state that it is not a problem with the functionality, only with the impression one gets. Thanks for your reply. /Jakob
As noted in the post-installation notice, emerge sync or emerge metadata will get rid of them entirely.
