I emerged the net-analyzer/nessus ebuild on my system, it defaulted to 2.3.0. Then I found out that I needed an older version, so I tried to simply emerge =net-analyzer/nessus-2.2.2a and count on it unmerging 2.3.0 in the process. This basically worked, except that when it says it got rid of it, it did not, and I did not end up with 2.2.2a as Portage says I did; old files were not removed, and new files were not merged in. I can verify the actual version installed by 'nessus -v'. Also 'emerge sync'd' and now I can work with v2.2.3 - same issue. Reproducible: Always Steps to Reproduce: 1. Add the following overrides to /etc/portage/package.keywords: net-analyzer/nessus ~amd64 net-analyzer/nessus-plugins ~amd64 net-analyzer/nessus-core ~amd64 net-analyzer/nessus-libraries ~amd64 net-analyzer/libnasl ~amd64 2. Run 'emerge nessus' -> gives you 2.3.0 3. Run 'emerge =net-analyzer/nessus-2.2.3. You see the update work as expected, except that the emerge output shows no file listed as being added (merged) and not files listed when be removed (unmerged) from the 2.3.0 package. Actual Results: The files from 2.3.0 remain on the system, even when Portage reports that no versions of nessus are installed. When trying to emerge an older version to have it replace the installed version, it doesn't happen; 2.3.0 persists no matter what. Expected Results: Portage should be able to merge files from older ebuilds in and remove the 2.3.0 version from the system. Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r12 x86_64) ================================================================= System uname: 2.6.9-gentoo-r12 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 14 2005, 20:32:49)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 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=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://gentoo.mirrors.pair.com http://cudlug.cudenver.edu/gentoo http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac aalib acpi alsa apache2 avi berkdb bitmap-fonts cdr crypt cups curl divx4linux dvd dvdr encode esd exif f77 fam flac font-server foomaticdb fortran gd gif gnome gphoto2 gpm gstreamer gtk gtk2 imagemagick imlib java jp2 jpeg junit kde ldap libwww lzw lzw-tiff mad mozilla mpeg multilib mysql ncurses nls nptl nvidia oggvorbis opengl oss pam pcre perl png python qt quicktime readline samba sdl spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xine xml2 xmms xpm xrandr xv xvid zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY Contents of /etc/portage/package.keywords: net-analyzer/nessus ~amd64 net-analyzer/nessus-plugins ~amd64 net-analyzer/nessus-core ~amd64 net-analyzer/nessus-libraries ~amd64 net-analyzer/libnasl ~amd64
You will need to remove: net-analyzer/nessus-libraries net-analyzer/libnasl net-analyzer/nessus-core net-analyzer/nessus-plugins This is because the nessus ebuild only exists to install all dependancies. I've added a notice to the end of nessus ebuilds explaining this when you attempt to remove next time. The other problems is that all the ebuilds specify >=net-analyzer/libnasl-${PV} so downgrading will still have the dependanies satisified.
the good news is its fixed now :-)- thanks for the bug report.
I should have figured that, I knew there were dependencies in the back of my mind but it didn't dawn on me when they weren't listed in the emerge output. Thanks for the fix, that was hella fast.
