Got myself in a bind unmerging portage

14 msg	Persistent revdep-rebuild issues: sun-jdk-1.4.2.16
1 msg	Which CFLAGS for Phenom?
6 msg	x looses ctrl, alt and shift keys
4 msg	Is there a way to get rid of the annoying speec...
33 msg	FS for laptop
3 msg	Qemu tun/tap privledge problem: HOWTO is wrong?
4 msg	portage update problem
10 msg	Booting up without X
7 msg	{OT} Safe to post my MAC address?
1 msg	Postgresql native replication problem
11 msg	How cam I get system to recognize MagicSysReq w...
7 msg	brlcad users here?
1 msg	emerge failed

Got myself in a bind unmerging portage
\ reader (17 Dec 2007)
. \ Randy Barlow (17 Dec 2007)
. . \ felix (17 Dec 2007)
. . . \ Dale (17 Dec 2007)
. . \ Albert Hopkins (17 Dec 2007)
. \ reader (17 Dec 2007)
. . \ Dale (17 Dec 2007)
. . \ Randy Barlow (17 Dec 2007)
. \ reader (17 Dec 2007)

10 msg	Dual USB HDD enclosure shows only a single disk...
5 msg	growisofs: 'media is not recognized as recordab...
7 msg	LVM, crypto, and backup
3 msg	scan for network devices by IP and time?
6 msg	trouble with vsftpd
3 msg	dd questions

Subject:	Got myself in a bind unmerging portage
Group:	Gentoo-user
From:	reader
Date:	17 Dec 2007

It all started like this: Using rsync I was getting an error when
ever I used the `--stats' flag. The output said it was an error in
the stack ... Rather than mess with it, I thought I might take the
opportunity to sync portage and see if a newer rsync was available.

Its been a mnth or so since I synced.

At the end of the sync I got the notice about emerging a new
portage... so did so.

But then when I attempted to emerg rsync I got some errors I'd never
seen before:

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-14253.log"

open_rd: /root/.bash_history
open_rd: /root/.bash_history
--------------------------------------------------------------------------------

What was shown there is absolutely all that is in the log and there
are no others at that location.

Looking at /root/.bash_history I saw nothing wrong. Its permissions
were 600... but just incase I set it to 644 but it didn't help.

Since these were (To me) unusual errors I thought maybe I should back
out the portage update.

Foolishly I ran emerge -vC portage before thinking about it much.

I was deeply embroiled in some perl programming is my only excuse
other than deep seated stupidity.

But cutting to the chase: Now of course many of the portage tools were
rm'ed before the emerge -vC failed here:

[...]
--- !empty dir /usr
--- !empty dir /etc/portage
--- !empty dir /etc/logrotate.d
--- !empty dir /etc/env.d
--- !empty dir /etc
[portage-2.1.4_rc10] bash: /usr/lib/portage/bin/ebuild.sh: No such file or directory
!!! FAILED postrm: 127

So very basic stuff is missing.

emerge is one of the tools now missing

I thought maybe I could download portage and compile it manually but
it appears not to really be made to be used like that.

At least looking in the unpacked top level directory I don't see the
familiar signs of a gnu sources package like ./configure and such. It
does have a ready made emerge at ./bin/emerge but running it seems to
indicate it is looking in the wrong places for stuff and isn't going
to be usefull without some more skilled technician than me.

What are my choices here... is the only one to use the livecd and
emerge portage from there? Or is there such a thing as a sources
package of portage arranged for a stand alone compile job.

All I could find was the distfile..

--
gentoo-user mailing list