From: Thorsten Fischer <frosch@cs.tu-berlin.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] yeeehaaa!
Date: Mon Jun 4 08:00:02 2001 [thread overview]
Message-ID: <Pine.SOL.4.10.10106041536050.27284-100000@bolero> (raw)
It's up and running, folks!
* thorsten is jumping around happily and waving at everyone *
Unfortunately I got no time to address the remaining minor annoyances
today, which include: supervise coughing because of missing directories,
cluttering terminals with that message and thus locking them down with
'respawning too fast' messages (which went away after I created the dir
by hand); network/pcmcia stuff running only after I start them a
second time 'by hand'; and some other things.
portage stuff:
I cd'ed into /usr/portage, running 'emerge rsync'. Then I decided to
check out the latest version of portage, so I typed
emerge sys-apps/portage/portage-1.5.1.ebuild
which produced
Calculating dependencies.!!! Name error in 1.7e2
!!! Error: /usr/portage/app-games/bzflag is not a valid portage
directory, skipping...
...... done!
!!! Error: circular dependencies
1.7e2 does not seem to match portage's naming scheme. The header of
portage.py reads 'Version 1.0 7/31/2000'. Deleting the bzflag subdir
removes the name error, but the circular dependencies remain. It's unclear
to me why bzflag is addressed here anyway.
After all:
It's there! It's running! And most important: internet access is working.
I am writing this using an ssh login from gentoo.
With more time at hand, I will happily address errors myself, and not just
bother you with them - which, after all, is the way I prefer to do
things.
thorsten
--
thorsten fischer
<frosch@derfrosch.de>
<tfischer@linux-magazin.de>
groessere mengen hostien sind schwer zu beschaffen
reply other threads:[~2001-06-04 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.SOL.4.10.10106041536050.27284-100000@bolero \
--to=frosch@cs.tu-berlin.de \
--cc=gentoo-dev@cvs.gentoo.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