From: Kain <kain@kain.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] [gentoo-ppc] bootstrap/portage problem
Date: Fri, 5 Apr 2002 18:00:51 -0600 [thread overview]
Message-ID: <20020406000051.GA22590@noir.is.pn> (raw)
In-Reply-To: <20020406005602.0a73c8a4.linux-dev@dialectique.org>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Sat, Apr 06, 2002 at 12:56:02AM +0200, linux-dev wrote:
>
> trying to run the bootstrap.sh script
> portage merges, then it proceeds to emerge sys-kernel/linux-headers-2.4.17-r5,
> downloads http://mirrors.sunsite.dk/gentoo/distfiles/linux-2.4.17.tar.bz2 and
This isn't right... you should be emerging
linux-headers-2.4.19.ebuild... I'll check cvs and see if I have it in
there right when I get back from work.
--
What's the difference between predicting and controlling a situation?
If you say it and it happens, can you prove that you didn't alter the
universe to make your prediction occur?
**
Concerned Citizen
Bryon Roche, Kain <kain@imperativesolutions.com>
<kain@kain.org>
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2002-04-06 0:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 8:59 [gentoo-dev] Gentoo PPC announcement Pieter Van den Abeele
2002-04-04 20:13 ` gentoo ppc cvs problem (was Re: [gentoo-dev] Gentoo PPC announcement) linux-dev
2002-04-04 21:39 ` Pieter Van Den Abeele
2002-04-04 22:15 ` linux-dev
2002-04-04 22:49 ` [gentoo-dev] [gentoo-ppc] make.conf settings for the PowerPC linux-dev
2002-04-05 1:15 ` Pieter Van Den Abeele
2002-04-05 22:56 ` [gentoo-dev] [gentoo-ppc] bootstrap/portage problem linux-dev
2002-04-05 22:43 ` Jared H. Hudson
2002-04-05 23:29 ` linux-dev
2002-04-06 0:00 ` Kain [this message]
2002-04-06 10:57 ` Pieter Van den Abeele
2002-04-06 16:38 ` linux-dev
2002-04-06 16:34 ` Pieter Van den Abeele
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=20020406000051.GA22590@noir.is.pn \
--to=kain@kain.org \
--cc=gentoo-dev@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