The 0.4.2 ebuild is for a newer version than 0.4b, but emerge does not agree and now that I have emerged 0.4.2 (by deleting the 0.4b ebuild file), a subsequent 'emerge -p ksambaplugin' shows that emerge would upgrade to 0.4b. There is either a naming convention failure in the created ebuilds for ksambaplugin, or emerge really doesn't understand that 0.4.2 > 0.4b. Reproducible: Always Steps to Reproduce: 1. emerge -p ksambaplugin 2. 3. Actual Results: fizban$ emerge -p ksambaplugin These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] net-misc/ksambaplugin-0.4b [0.4.2] Expected Results: Showed an R (regen) for ksambaplugin-0.4.2. fizban$ emerge info Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-gentoo-r2 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GENTOO_MIRRORS="ftp://ftp.ibiblio.org/pub/linux/distributions/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://gentoo.oregonstate.edu ftp://ftp.oregonstate.edu/pub/gentoo http://distro.ibiblio.org/gentoo " 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" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg gnome libg++ libwww mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts svga java guile X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk qt kde motif opengl ldap cdr" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe" CXXFLAGS="-march=pentium3 -O3 -pipe" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://localhost:8730/gentoo-portage" FEATURES="sandbox ccache"
This seems to be a problem in portage.best(). This is a easy way to reproduce it : >>> portage.best(['net-www/lynx-2.8.4.1c', 'net-www/lynx-2.8.4a-r4', 'net-www/lynx-2.8.4.1d']); 'net-www/lynx-2.8.4a-r4' The expected result is of course 'net-www/lynx-2.8.4.1d'
Lexigraphically, this is correct. 4b is more than 4 so... 0.4b > 0.4.2b > 0.4.2
Excuse me, but this *is* a bug. Despite what portage.best() says, ksambaplugin-0.4b is not newer than ksambaplugin-0.4.2. Perhaps the bug was misassigned and the bug is in the naming convention being applied in the ksambaplugin ebuilds? A nice solution for this would be to delete ksambaplugin-0.4b from the portage tree.
I'd like to open this back up. Is there a standard way to force this? It would be nice not to have to watch out for these things.