From: Radoslaw Stachowiak <radek@alter.pl>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] still no reply :/
Date: Wed, 18 Dec 2002 19:05:14 +0100 [thread overview]
Message-ID: <20021218180514.GT5197@blue.alter.pl> (raw)
Hello, I asked about strange portage bug few days ago, but got no reply :(
Today, after 'emerge perl ExtUtils-MakeMaker' which were completed ok, emerge
automaticly removed my portage and resulted in system with no emerge binary etc :)
I did 'emerge perl ExtUtils-MakeMaker' because I knew that I got some problems with
this system. emerge -p world showed that portage packege should be upgraded from
version 2.0.45-r1 to 2.0.45-r5, so I specific named only perl an MakeMaker for upgrade to address this situation..
unfortuntatly it didnt help and above command resulted in little
disaster. Longer description of this problem can be found in my previous
mail.
Looking forward _any_ ideas whats wrong :(
Here are fatal portage removal output. WHATS STRANGE: older package is
proteceted, while newer one is selected for removal. This is _after_
newer binaries are installed so, such action always results in removal
of files which of course is a serious failure :((((
>>> Regenerating /etc/ld.so.cache...
>>> Auto-cleaning packages ...
sys-apps/portage
selected: 2.0.45-r5
protected: 2.0.45-r1
omitted: none
>>> Packages in red are slated for removal.
>>> Packages in green will not be removed.
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging sys-apps/portage-2.0.45-r5...
No package files given... Grabbing a set.
<<< obj /var/tmp/.keep
<<< obj /usr/share/man/man5/make.conf.5.gz
<<< obj /usr/share/man/man5/ebuild.5.gz
<<< obj /usr/share/man/man1/repoman.1.gz
<<< obj /usr/share/man/man1/etc-update.1.gz
<<< obj /usr/share/man/man1/env-update.1.gz
<<< obj /usr/share/man/man1/emerge.1.gz
<<< obj /usr/share/man/man1/ebuild.1.gz
<<< obj /usr/share/doc/portage-2.0.45-r5/ChangeLog.gz
<<< obj /usr/lib/python2.2/site-packages/xpak.py
<<< obj /usr/lib/python2.2/site-packages/portage.py
<<< obj /usr/lib/python2.2/site-packages/output.py
<<< obj /usr/lib/python2.2/site-packages/missingos.so
<<< obj /usr/lib/portage/lib/sandbox.bashrc
<<< obj /usr/lib/portage/bin/xpak
<<< obj /usr/lib/portage/bin/tbz2tool
<<< obj /usr/lib/portage/bin/sandbox
<<< obj /usr/lib/portage/bin/repoman
<<< obj /usr/lib/portage/bin/quickpkg
<<< obj /usr/lib/portage/bin/queryhost.sh
<<< obj /usr/lib/portage/bin/prepstrip
<<< obj /usr/lib/portage/bin/prepman
<<< obj /usr/lib/portage/bin/preplib.so
<<< obj /usr/lib/portage/bin/preplib
<<< obj /usr/lib/portage/bin/prepinfo
<<< obj /usr/lib/portage/bin/prepallstrip
<<< obj /usr/lib/portage/bin/prepallman
<<< obj /usr/lib/portage/bin/prepallinfo
<<< obj /usr/lib/portage/bin/prepalldocs
<<< obj /usr/lib/portage/bin/prepall
<<< obj /usr/lib/portage/bin/pkgname
<<< obj /usr/lib/portage/bin/pkgmerge.new
<<< obj /usr/lib/portage/bin/pkgmerge
<<< obj /usr/lib/portage/bin/pkglist
<<< obj /usr/lib/portage/bin/pdb.cgi
<<< obj /usr/lib/portage/bin/pdb
<<< obj /usr/lib/portage/bin/newsbin
<<< obj /usr/lib/portage/bin/newman
<<< obj /usr/lib/portage/bin/newlib.so
<<< obj /usr/lib/portage/bin/newlib.a
<<< obj /usr/lib/portage/bin/newins
<<< obj /usr/lib/portage/bin/newexe
<<< obj /usr/lib/portage/bin/newdoc
<<< obj /usr/lib/portage/bin/newbin
<<< obj /usr/lib/portage/bin/fperms
<<< obj /usr/lib/portage/bin/fowners
<<< obj /usr/lib/portage/bin/find-requires
<<< obj /usr/lib/portage/bin/find-packages
<<< obj /usr/lib/portage/bin/etc-update
<<< obj /usr/lib/portage/bin/env-update
<<< obj /usr/lib/portage/bin/emerge
<<< obj /usr/lib/portage/bin/emake
<<< obj /usr/lib/portage/bin/ebuild.sh
<<< obj /usr/lib/portage/bin/ebuild
<<< obj /usr/lib/portage/bin/dosym
<<< obj /usr/lib/portage/bin/dosed
<<< obj /usr/lib/portage/bin/dosbin
<<< obj /usr/lib/portage/bin/dopython
<<< obj /usr/lib/portage/bin/domo
<<< obj /usr/lib/portage/bin/doman
<<< obj /usr/lib/portage/bin/dolib.so
<<< obj /usr/lib/portage/bin/dolib.a
<<< obj /usr/lib/portage/bin/dolib
<<< obj /usr/lib/portage/bin/dojar
<<< obj /usr/lib/portage/bin/doins
<<< obj /usr/lib/portage/bin/doinfo
<<< obj /usr/lib/portage/bin/dohtml
<<< obj /usr/lib/portage/bin/dohard
<<< obj /usr/lib/portage/bin/doexe
<<< obj /usr/lib/portage/bin/dodoc
<<< obj /usr/lib/portage/bin/dodir
<<< obj /usr/lib/portage/bin/dobin
<<< obj /usr/lib/portage/bin/db-update.py
<<< obj /usr/lib/portage/bin/chkcontents
<<< obj /lib/libsandbox.so
--- cfgpro obj /etc/make.globals
--- cfgpro obj /etc/make.conf
--- cfgpro obj /etc/etc-update.conf
<<< sym /usr/sbin/pkgmerge
<<< sym /usr/sbin/etc-update
<<< sym /usr/sbin/env-update
<<< sym /usr/sbin/ebuild.sh
<<< sym /usr/sbin/ebuild
<<< sym /usr/lib/portage/bin/pmake
<<< sym /usr/lib/portage/bin/donewins
<<< sym /usr/bin/xpak
<<< sym /usr/bin/tbz2tool
<<< sym /usr/bin/repoman
<<< sym /usr/bin/emerge
<<< dir /usr/share/doc/portage-2.0.45-r5
<<< dir /usr/lib/portage/lib
--- !empty dir /var/tmp
--- !empty dir /var
--- !empty dir /usr/share/man/man5
--- !empty dir /usr/share/man/man1
--- !empty dir /usr/share/man
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/sbin
--- !empty dir /usr/lib/python2.2/site-packages
--- !empty dir /usr/lib/python2.2
--- !empty dir /usr/lib/portage/bin
--- !empty dir /usr/lib/portage
--- !empty dir /usr/lib
--- !empty dir /usr/bin
--- !empty dir /usr
--- !empty dir /lib
--- !empty dir /etc
bash: /usr/sbin/ebuild.sh: No such file or directory
>>> Regenerating /etc/ld.so.cache...
* GNU info directory index is up-to-date.
* IMPORTANT: 1 config files in /etc need updating.
* Type emerge --help config to learn how to update config files.
plagae / # emerge
bash: /usr/bin/emerge: No such file or directory
.radek.
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-12-18 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 18:05 Radoslaw Stachowiak [this message]
2002-12-28 10:51 ` [gentoo-dev] still no reply :/ Martin Schlemmer
2002-12-28 11:01 ` Radoslaw Stachowiak
2002-12-28 11:20 ` Martin Schlemmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021218180514.GT5197@blue.alter.pl \
--to=radek@alter.pl \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox