Killed my coreutils -- HELP

[panik08]

Which stage3? The 2008.0 one?
and then emerge -DuNtav world?
Sorry for having to ask these basic stuff, but I really want stuff to work again and not mess it up any more.

[panik08]

Oh, re-emerge whole system... how do I do that?

[Sodki]

[panik08]

Well, stuff are getting better, but still this:

/usr/lib/portage/bin/filter-bash-environment.py: line 8: egrep_compat_map: command not found
/usr/lib/portage/bin/filter-bash-environment.py: line 9: [:alnum:]: command not found
/usr/lib/portage/bin/filter-bash-environment.py: line 10: [:space:]: command not found
/usr/lib/portage/bin/filter-bash-environment.py: line 11: syntax error near unexpected token `}'
/usr/lib/portage/bin/filter-bash-environment.py: line 11: `}'

Don't know how to fix it. I get it when running emerge so stuff doesn't get emerged.
Anyone knows what is broken here? Can I get portage to ignore all kind of errors? It complains about

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

open_wr: /root/sys
open_wr: /root/sys
open_wr: /root/sys
open_wr: /root/sys


since it tries to do
import os, re, sys

and that is interpreted as the imagemagic command.

[gentleman]

Ah ok thanks. Though I think the sense seems a little bit confusing.

After unmerging debianutils

[panik08]

It seems it was the file /usr/bin/env that was messed up.
https://forums.gentoo.org/viewtopic-t-688104.html

[panik08]

Still problem with emerging coreutils
any ideas?


* Running autoheader ... [ ok ]
* Running automake --add-missing --copy ... [ !! ]

* Failed Running automake !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/sys-apps/coreutils-6.10-r1/temp/automake-31105.out

*
* ERROR: sys-apps/coreutils-6.10-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2851: Called eautoreconf
* environment, line 941: Called eautomake
* environment, line 915: Called autotools_run_tool 'src_unpack' 'src_unpack' 'automake'
* environment, line 416: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
* The die message:
* Failed Running automake !
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/log/portage/sys-apps:coreutils-6.10-r1:20080420-091648.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/coreutils-6.10-r1/temp/environment'.
*

[59729]

Had the same problem, waited for this thread before removing mktemp (solved)

[Cyker]

I just had this too!

Thanks for the fix confirmation!

[coolsnowmen]

[desultory]

[ashsama]

[kepik_k]

I'm not sure if this is relevant to this post, but I did find out that during the emerge -uavD world to satisfy a Block on coreutils I had to unmerge both mktemp and util-linux. The consequences to unmerging util-linux was a deletion of /bin/mount.
All of this worked great until emerge got the step of upgrading grub, it reported a failure to mount /boot, and asked user to mount /boot manually. Well that was how I found my mistake:

[Tuxenstein]

I tried to remove some of the blocked packages listed, with the following messages attached:

[markp2000]

Yes, if you do remove mktemp DO NOT REBOOT. I lost the ability for nameserver resolution which prevented any further emerging.

Here is how I fixed it. Although it was mentioned before by downloading from tinderbox.

1. Boot using minimal install cd

2. Mount hard disk partition that root is on under /mnt/gentoo

[desultory]

Merged a post.

[Tuxenstein]

So far, it seems I can't remove mktemp (although, I don't want to risk rebooting just in case...), but as I presently don't have access to a Live or rescue CD of any type, it may have to wait until I can find someone who can make me one.

[desultory]

If both sys-apps/mktemp and sys-apps/coreutils, prior to version 6.10-r1, are installed, run the following commands in the order given.

[Tuxenstein]

Coreutils appears to have definitely been removed from my system, but in checking /bin, mktemp still appears to be there (nor could I try and remove it if I wanted to for the same reason I also can't emerge anything--although, given the current situation, I'm not so sure I'd want to try and remove it even if I could...).

On a related note, if/when I might finally get access to a Live CD and can copy over stty into /bin, would I get stuck in this same mess all over again? Or is there some way for me to avoid it and still be able to update everything I need to (including mktemp and coreutils)?

[desultory]

[Tuxenstein]

I know this is going to sound like an incredibly stupid question, but a previous post made by someone earlier as well as your last post has me curious about this. What exactly does mktemp actually do and why, based upon a previous comment (which also gives me another reason as to why I don't think I want to try and find out "the hard way"), would it basically "hose" my install? Going by the initials, I'm assuming the mk stands for "make" as in "make temp"?

Also, regarding root access, the "best" I can currently do is being able to log in as su through the shell--which I know isn't quite the same thing as being logged in as root, itself, and from what I remember (and I could be wrong about this?), it's not really possible to somehow switch over to root, itself, through the command line?

In terms of packages, as far as I'm consciously aware, I'm not using either the --buildpkg or --buildpkgonly options when I emerge (in fact, I don't think I've ever used them nor was even aware of them). I'm also not entirely certain, however, as to where my system would store pre-build packages.

[desultory]

[Tuxenstein]

Using Nautilus (as I can't view any directories using the command line), I just checked under usr/portage and while I can see the directories listed by category, I didn't see a directory labeled "packages" and therefore none called "All". However, in looking at my sys-apps directory, I am seeing some coreutils files (specifically, I see an XML file labeled "manifest", a directory labeled "files", another file labeled "manifest" and ebuilds for coreutils, including both the version I had as well as 6.10-r (and maybe strangely, I'm seeing 6.11 listed?).

When I get a chance to later on today, I'll see about trying out the steps you provided and am assuming that in place of $PKGDIR, I would type the path in (given what I've just seen of the above) as /usr/portage/sys-apps/coreutils?

Edited to add, I just tried running wget and then to untar coreutils and placing them into /usr/portage/sys-apps/coreutils, however, for whatever reason, I can't seem to run the command: env FEATURES="-collision-protect" emerge -1KO '=sys-apps/coreutils-6.10-r2' as it creates the following error message: emerge: there are no ebuilds to satisfy "=sys-apps/coreutils-6.10-r2".

[desultory]

[Tuxenstein]

I ran emerge --info | grep PKGDIR and it came up as telling me /usr/portage/packages--however, I don't have a packages directory (Nautilus isn't showing it and when I attempted to get into it through the command line--after attempting to view it in the command line--it wasn't there), so I went ahead and created the directory as well as a directory within it called All.

Also, someone suggested to me to look in the distfiles directory and I did notice a number of archives listed there, but I'm assuming it's also different?

Regardless, after downloading and untarring the file in the newly-created packages/All directory (in /usr/portage), I ran env FEATURES="-collision-protect" emerge -1KO '=sys-apps/coreutils-6.10-r2' and it appeared to "take", but when I tried to run emerge -avo1 sys-apps/coreutils, it came up with this: