1 |
On Friday 02 March 2007 01:40:10 Denis wrote: |
2 |
> > You really need to tell us more about your system. What did you do |
3 |
> > preceding this? |
4 |
> |
5 |
> emerge --info gives the following: |
6 |
> |
7 |
> Portage 2.0.51.22-r3 (default-linux/x86/no-nptl/2.4, gcc-3.3.5, |
8 |
> glibc-2.3.1-r2,glibc-2.3.4.20040808-r1, 2.4.19-gentoo-r10 i686) |
9 |
> ================================================================= |
10 |
> System uname: 2.4.19-gentoo-r10 i686 Intel(R) XEON(TM) CPU 2.20GHz |
11 |
[SNIP] |
12 |
|
13 |
Wow... ;) |
14 |
|
15 |
> I know, I haven't updated for a while. I was trying to update |
16 |
> Portage, and coreutils was listed as the necessary package to emerge |
17 |
> first. |
18 |
> |
19 |
> > What's the output of `emerge -pv coreutils`? |
20 |
> |
21 |
> Calculating dependencies ...done! |
22 |
> [ebuild N ] sys-apps/coreutils-6.4 -acl +nls (-selinux) -static 0 kB |
23 |
> |
24 |
> > please show the output of either `equery check coreutils` or `qcheck |
25 |
> > coreutils`. |
26 |
> |
27 |
> BLANK. I ran it, and it doesn't give any output at all. |
28 |
|
29 |
Ouch! Did you attempt to emerge busybox? If that doesn't work my best |
30 |
suggestion at this point and with the information available is to grab the |
31 |
coreutils-6.4 binpkg at [1], put it in /usr/portage/packages/All/ and emerge |
32 |
it with --usebinpkgonly... |
33 |
|
34 |
As a side note given the age of your portage you may need information |
35 |
available at [2] when you've gotten past this problem... |
36 |
|
37 |
[1] http://tinderbox.x86.dev.gentoo.org/default-linux/x86/All/ |
38 |
[2] http://www.gentoo.org/proj/en/portage/doc/common-problems.xml |
39 |
|
40 |
-- |
41 |
Bo Andresen |