(I know these are not yet unmask so I am not sure if you want bug reports on these or not ??) I emerged gnome-light-2.10.0, which upgraded libwnck to 2.10.0 In that case, gnome-system-monitor failed to start with error complaining about missing libwnck-1.so.4. (i already "solved" it so i lost original error message). Message is typical "Cannot open shared library libwnck-1.so.4." Indeed libwnck-2.10.0 upgraded library to .16 (making a link to .16 called .4, allows gnome-system-monitor to start but list of process is full of processes without names) Gnome-system-monitor which is not part of gnome-light-2.10 remains at version 2.8 here as I was using full gnome-2.8 before. Upgrading gnome-system-monitor and gliptop to 2.10 fixed it, but they are not supposed to be in gnome-light... Reproducible: Always Steps to Reproduce: 1. 2. 3.
I forgot that : # emerge info Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r14 x86_64) ================================================================= System uname: 2.6.9-gentoo-r14 x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 10 2005, 00:53:56)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /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 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" 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="amd64 X alsa apache2 avi bonobo cups dv dvd dvdread eds encode font-server gnome gphoto2 gstreamer gtk gtk2 hal howl java jpeg mad mbox mozsvg mpeg mplayer multilib network nptl nvidia ogg oggvorbis opengl quicktime readline real svg theora tiff truetype truetype-fonts type1-fonts v4l v4l2 xosd xv xvid zlib"Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
yea mixing p.mask with other pkgs will do that :)
Sorry to ask here, but does that means that we should not report bugs occuring when testing masked packages ?
sure, but you should also unmask other apps that may depend on each other and so on...
But if gnome-light-2.10.0 cannot work without gnome-system-monitor>=2.10.0, doesn't that mean there is a dependency problem in gnome-light-2.10.0 ebuild ? When I did it, I unmasked the whole of dependencies for gnome-light ... the fix that I used was to emerge packages from gnome's dependencies list NOT from gnome-light.
FYI, same on x86. Unless gnome-light is not supported anymore, I don't see why this bug is marked invalid.