I just attempted to make my own openoffice-bin-1.1.0 and place it in PORTAGE_OVERLAY, as no ebuild for that version is yet in portage. The emerge command didn't find the new version of the package even though I specified it explicitly with "emerge -pv openoffice-bin-1.1.0". However, when using the full path to the ebuild file, things worked without problems. Also, when renaming my package to openoffice-mybin everything worked as expected. I've tried the same thing both with new Manifest and digest files (generated with ebuild ... digest), and without them. The results are the same. NOTE: When overlaying an EXISTING version of a package in portage, things seem to work correctly though. I'm doing that with several packages, and portage is using my versions instead of the versions in the default portage tree. Reproducible: Always Steps to Reproduce: 1. mkdir -p /usr/local/portage/app-office/openoffice-bin 2. cd /usr/local/portage/app-office/openoffice-bin 3. cp /usr/portage/app-office/openoffice-bin/openoffice-bin-1.1_rc4.ebuild . 4. mv openoffice-bin-1.1_rc4.ebuild openoffice-bin-1.1.0.ebuild 5. emerge -pv openoffice-bin-1.1.0 Maybe it is better to use openoffice-bin-1.2.0 or something, as the 1.1.0 will probably reach portage one of these days. Also, I know I've omitted some minor stuff in the files directory, but it doesn't matter for this issue. Actual Results: These are the packages that I would merge, in order: Calculating dependencies emerge: there are no masked or unmasked ebuilds to satisfy "openoffice-bin-1.1.0". !!! Error calculating dependencies. Please correct. Expected Results: These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] app-office/openoffice-bin-1.1.0 -kde +gnome Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r7)================================================================= System uname: 2.4.20-gentoo-r7 i686 Intel(R) Celeron(R) CPU 2.00GHz ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium2 -frerun-cse-after-loop -frerun-loop-opt -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /opt/tomcat/conf /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=pentium2 -frerun-cse-after-loop -frerun-loop-opt -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache fixpackages sandbox userpriv" GENTOO_MIRRORS="http://gentoo.linux.no/ http://trumpetti.atm.tut.fi/gentoo/ http://gentoo.oregonstate.edu" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 apm encode foomaticdb jpeg libg++ mad mikmod mmx ncurses nls quicktime xml2 xmms zlib gtkhtml gdbm berkdb slang readline tetex bonobo tcltk guile mysql sdl gpm tcpd pam libwww ssl perl python esd imlib motif opengl cdr apache2 avi cups dga doc emacs evo gnome gif gtk innodb java mozilla mozsvg mpeg oggvorbis oss pdflib pic png samba sis spell sse truetype usb X xv -alsa -arts -crypt -kde -svga -qt"
Invalid. The ebuild is masked. Have a look at /usr/portage/profiles/package.mask
Ok, I see. Shouldn't portage report "no *unmasked* ebuild ..." as usual then? This was very confusing...
Aha! My bad, forgot the little annoying "=" in front of the package version. With "emerge =openoffice-bin-1.1.0" I do get the right error message. Hmm... I remember having done this little trivial mistake before. Maybe it would be an easy thing to patch the emerge command to check for version numbers in erroneous package names and print a nice little help message? Like "try again with '=package' or '>=package'". Anyway, that would be another bug. Close, abort, ignore.
*** This bug has been marked as a duplicate of 29856 ***
