If I emerge anything portage continues to autoclean itself along with other needed gentoo components Reproducible: Always Steps to Reproduce: 1. emerge foo 2. 3. Actual Results: portage stopped autocleaning because it was no longer there: >>> Regenerating /etc/ld.so.cache... >>> Auto-cleaning packages... app-misc/pax-utils selected: 0.1.15 protected: 0.1.16 omitted: none sys-apps/portage selected: 2.1.2.2 protected: 2.1.3.12 omitted: none net-misc/rsync selected: 2.6.9-r1 protected: 2.6.9-r4 omitted: none sys-apps/coreutils selected: 6.4 protected: 6.9-r1 omitted: none <snip...> [portage-2.1.2.2] bash: /usr/lib/portage/bin/ebuild.sh: No such file or directory !!! FAILED postrm: 127 A removal phase of the 'sys-apps/portage-2.1.2.2' package has failed with exit value 127. The problem occurred while executing the ebuild located at '/var/db/pkg/sys-apps/portage-2.1.2.2/portage-2.1.2.2.ebuild'. If necessary, manually remove the ebuild in order to skip the execution of removal phases. Expected Results: Finish the emerge This emerge --info is pretty useless as I have had to unpack a stage 3 tarball to get portage working again george-laptop / # emerge --info Portage 2.1.2.2 (default-linux/x86/2007.0, gcc-4.1.1, glibc-2.5-r0, 2.6.22-13-generic i686) ================================================================= System uname: 2.6.22-13-generic i686 Intel(R) Pentium(R) 4 CPU 3.06GHz Gentoo Base System release 1.12.9 Timestamp of tree: Mon, 08 Oct 2007 18:00:08 +0000 app-shells/bash: 3.1_p17 dev-lang/python: 2.4.3-r4, 2.5.1-r2 dev-python/pycrypto: 2.0.1-r5 sys-apps/baselayout: 1.12.9 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.61 sys-devel/automake: 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" CBUILD="i486-pc-linux-gnu" CFLAGS="-O2 -mtune=i686 -pipe" CHOST="i486-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-O2 -mtune=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_GB.UTF-8" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="acl berkdb bitmap-fonts cli cracklib crypt cups dri fortran gdbm gpm iconv ipv6 isdnlog midi mudflap ncurses nls nptl nptlonly openmp pam pcre perl pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts unicode x86 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
I have heard of this happening in the 'rescue' case. If you untar a stage3 tarball over your /, you can end up with /var/db/pkg showing more than one version of a package installed, even though it's not really installed. To "fix" this, portage (read: autoclean) will remove the package... Does that sound like what might've happened?
It's possible, this is not the first time i've unpacked the tarball to fix it, the problem was there originally somehow and as I am installing the stage3 was already there to hand
in /var/db/pkg there is indeed two version, maybe deleting the one that isn't Portage 2.1.2.2 would help
http://dev.gentoo.org/~marienz/stage-tarball-is-not-a-rescue-tarball.txt
(In reply to comment #4) > http://dev.gentoo.org/~marienz/stage-tarball-is-not-a-rescue-tarball.txt > That does describe the problem. I would also like to point out that this is a new install and not an existing one
