ebuild doesn't use the portage tree: pulsar # ebuild cisco-vpnclient-3des-4.0.1a.ebuild unpack /usr/sbin/ebuild.sh: line 1057: //var/db/pkg/net-misc/cisco-vpnclient-3des-4.0.1a/cisco-vpnclient-3des-4.0.1a.ebuild: No such file or directory !!! ERROR: net-misc/cisco-vpnclient-3des-4.0.1a failed. !!! Function , Line 1057, Exitcode 1 !!! error sourcing ebuild pulsar # very broken!!!!!! Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: ebuild should always! use the copy in the portage tree
Great repoman has the same "bug", after stracing why it would complain the var doesn't exist: pulsar # repoman full RepoMan scours the neighborhood... digest.stray 0 digest.missing 0 ebuild.invalidname 0 ebuild.namenomatch 0 changelog.missing 0 changelog.notadded 0 ebuild.notadded 0 digest.notadded 0 ebuild.disjointed 0 digest.disjointed 0 DEPEND.bad 0 RDEPEND.bad 0 DEPEND.badmasked 0 RDEPEND.badmasked 0 ebuild.syntax 0 ebuild.output 0 ebuild.nesteddie 0 LICENSE.invalid 0 IUSE.invalid 0 KEYWORDS.invalid 0 ebuild.nostable 0 ebuild.allmasked 0 KEYWORDS.missing 0 LICENSE.missing 0 DESCRIPTION.missing 0 SLOT.missing 1 net-misc/cisco-vpnclient-3des/cisco-vpnclient-3des-4.0.1a.ebuild RepoMan sez: "You're only giving me a partial QA payment? I'll take it this time, but I'm not happy." pulsar # grep SLOT cisco-vpnclient-3des-4.0.1a.ebuild SLOT="0" pulsar #
Are you sure you are in the directory containing the ebuild in the first place? It is more useful if you set your shell prompt to PS1='\w \$ ' for bugreporting... I've seen this behaviour before, but I wonder, whether it is really looking at that particular ebuild (in /var) or just saying it is. In any case, the fault lies in /usr/lib/python/site-packages/portage.py
The paths get too long if I post them on each command line so I have them in my xterm title. I'd be darned if I remember 100% where I was but I think I was in that directory because that is what I always do to run repoman. I think this point to some sort of logic error at some level which could cause critical failures in any ebuild which would be hard to identify to any dev not stumbling onto this bug.
What version of Portage?
please post `emerge info`
i'm seeing this as well. Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ============================================================ ===== System uname: 2.4.22_pre2-gss i686 AMD Athlon(TM) XP 2500+ GENTOO_MIRRORS="http://www.gtlib.cc.gatech.edu/pub/gentoo http://gentoo.ussg.indiana.edu http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://www.ibiblio.org/pub/Linux/distributions/ gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/ 3/share/config /var/bind /usr/X11R6/lib/X11/xkb" 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 foomaticdb gif imlib java jpeg libg++ libwww mad mmx mpeg ncurses oggvorbis pdflib png qt quicktime sdl slang spell svga truetype xml2 xmms xv zlib gdbm berkdb readline X tcpd pam ssl perl python gtk motif opengl ldap alsa apache2 cdr curl doc dvd emacs ethereal gtk2 imap innodb jikes maildir mbox mozilla mysql offensive sasl slp sse tcltk tiff usb xvid -arts -gpm -kde -gnome -mikmod -nls" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe" CXXFLAGS="-march=athlon-xp -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
FEATURES=noauto fix this? I believe I've fixed this since -r5. Please try 49 or 48-r7
no more comments, so I assume it is fixed.
This is NOT fixed. Steps to reproduce: 1. Emerge <package> 2. Unmerge <package> 3. ebuild <package>.ebuild <command> 4. ebuild tried to source the ebuild in /var/db instead of the one in portage (and yes I'm in the correct dir)
Ok, I think I found the problem: There were some files left in /var/tmp/portage/<package>/temp (eclass-debug.log and environment), deleting these fixed the problem.
