1 |
Rikard Johnels wrote: [Sat Jul 31 2004, 01:21:39PM EDT] |
2 |
> I did "tar xjpUvf portage-rescue-2.0.49-r3-alpha.tbz2 -C /" as described in |
3 |
> the README-RESCUE file |
4 |
|
5 |
Ouch, we should really make a newer portage-rescue for alpha, based on |
6 |
2.0.50. |
7 |
|
8 |
> The foillowing trash occurs after the patched portage |
9 |
> |
10 |
> Gentoo files # emerge sync |
11 |
> |
12 |
> <snip (lots of lines)> |
13 |
> |
14 |
> x11-wm/fluxbox/files/ |
15 |
> xfce-extra/ |
16 |
> rsync: connection unexpectedly closed (1977189 bytes read so far) |
17 |
> rsync error: error in rsync protocol data stream (code 12) at io.c(150) |
18 |
|
19 |
As Kloeri said, bad rsync version |
20 |
|
21 |
> Gentoo files # emerge portage |
22 |
> portage: Update type "slotmove" not recognized. |
23 |
> portage: Update type "slotmove" not recognized. |
24 |
> portage: Update type "slotmove" not recognized. |
25 |
> portage: Update type "slotmove" not recognized. |
26 |
> portage: Update type "slotmove" not recognized. |
27 |
> portage: Update type "slotmove" not recognized. |
28 |
> portage: Update type "slotmove" not recognized. |
29 |
|
30 |
This is because the version of portage in the rescue tarball is too |
31 |
old. |
32 |
|
33 |
> Calculating dependencies -Traceback (most recent call last): |
34 |
> ... |
35 |
|
36 |
The crash probably occurred because the tree was only partly rsync'd, |
37 |
but I'm not sure. |
38 |
|
39 |
> So what now? |
40 |
|
41 |
I don't know the easiest way out. I would probably build a better |
42 |
rsync on either another machine or this one if you can make it work |
43 |
(perhaps using emerge with --nodeps). Then try to get the tree to |
44 |
sync. |
45 |
|
46 |
Alternatively you could unpack stage1 into a chroot and build a newer |
47 |
portage there, use --buildpkg to make a package out of it, then untar |
48 |
that into your root partition. Self-baked portage rescue... |
49 |
|
50 |
Regards, |
51 |
Aron |
52 |
|
53 |
-- |
54 |
Aron Griffis |
55 |
Gentoo Linux Developer |