public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rikard Johnels <rikjoh@norweb.se>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] Problems running bootstrap.sh
Date: Tue, 3 Aug 2004 05:18:20 +0200	[thread overview]
Message-ID: <200408030518.20611.rikjoh@norweb.se> (raw)
In-Reply-To: <20040802040125.GN12327@time.flatmonk.org>

On Monday 02 August 2004 06.01, Aron Griffis wrote:
> Rikard Johnels wrote:	[Sat Jul 31 2004, 01:21:39PM EDT]
>
> > I did "tar xjpUvf portage-rescue-2.0.49-r3-alpha.tbz2  -C /" as described
> > in the README-RESCUE file
>
> Ouch, we should really make a newer portage-rescue for alpha, based on
> 2.0.50.
>
> > The foillowing trash occurs after the patched portage
> >
> > Gentoo files # emerge sync
> >
> > <snip (lots of lines)>
> >
> > x11-wm/fluxbox/files/
> > xfce-extra/
> > rsync: connection unexpectedly closed (1977189 bytes read so far)
> > rsync error: error in rsync protocol data stream (code 12) at io.c(150)
>
> As Kloeri said, bad rsync version
>
> > Gentoo files # emerge portage
> > portage: Update type "slotmove" not recognized.
> > portage: Update type "slotmove" not recognized.
> > portage: Update type "slotmove" not recognized.
> > portage: Update type "slotmove" not recognized.
> > portage: Update type "slotmove" not recognized.
> > portage: Update type "slotmove" not recognized.
> > portage: Update type "slotmove" not recognized.
>
> This is because the version of portage in the rescue tarball is too
> old.
>
> > Calculating dependencies -Traceback (most recent call last):
> > ...
>
> The crash probably occurred because the tree was only partly rsync'd,
> but I'm not sure.
>
> > So what now?
>
> I don't know the easiest way out.  I would probably build a better
> rsync on either another machine or this one if you can make it work
> (perhaps using emerge with --nodeps).  Then try to get the tree to
> sync.
>
> Alternatively you could unpack stage1 into a chroot and build a newer
> portage there, use --buildpkg to make a package out of it, then untar
> that into your root partition.  Self-baked portage rescue...
>
> Regards,
> Aron
>
> --
> Aron Griffis
> Gentoo Linux Developer

Maybe time for a new complete release? :)
I did see something about a new one around the corner..

*waiting*

-- 
         /Rikard

------------------------------------------------------------------------------------
Rikard Johnels          email   : rikjoh@norweb.se
                        Web     : http://www.rikjoh.com
                        Mob     : +46 735 05 51 01

------------------------ Public PGP fingerprint ----------------------------
< 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78  46 1C EE 56 >

--
gentoo-alpha@gentoo.org mailing list


  parent reply	other threads:[~2004-08-03  3:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 14:04 [gentoo-alpha] Problems running bootstrap.sh Sigurd Stordal
2004-07-31 17:21 ` Rikard Johnels
2004-08-01  1:15   ` Bryan Østergaard
2004-08-02  4:01   ` Aron Griffis
2004-08-03  3:16     ` Rikard Johnels
2004-08-03  3:18     ` Rikard Johnels [this message]
2004-09-26 12:40     ` Rikard Johnels
  -- strict thread matches above, loose matches on Subject: below --
2004-07-26  4:36 Rikard Johnels
2004-07-26 11:20 ` Rikard Johnels
2004-07-27 22:08   ` Fluff
2004-08-02  4:05 ` Aron Griffis

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=200408030518.20611.rikjoh@norweb.se \
    --to=rikjoh@norweb.se \
    --cc=gentoo-alpha@lists.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