public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Parkhurst" <brianp@spamcop.net>
To: <gentoo-alpha@lists.gentoo.org>
Subject: [gentoo-alpha] Portage problem
Date: Mon, 11 Oct 2004 10:40:32 -0700	[thread overview]
Message-ID: <016f01c4afb9$6a7aa690$3301a8c0@ICHIRO> (raw)
In-Reply-To: Pine.GSO.4.58.0410091753200.2554@sun-71.cae.wisc.edu

Hi all,

I had a system crash this weekend, about 12 hours after getting the 2.6.8
kernel working on my alpha.  (unrelated problem).

I've restored the system to a backup from about 10 days ago but it now seems
my portage database is problematic and the typical emerge commands are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



--
gentoo-alpha@gentoo.org mailing list


  reply	other threads:[~2004-10-11 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 15:03 [gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform Bill.Glessner
2004-10-08 15:28 ` Fluff
2004-10-08 16:33   ` Bill.Glessner
2004-10-09  2:31     ` [gentoo-alpha] 2.6.8 kernel and SWXCR (Mylex DAC960) controller Brian Parkhurst
2004-10-09 22:57 ` [gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform Tony Hammond
2004-10-11 17:40   ` Brian Parkhurst [this message]
2004-10-11 18:56     ` [gentoo-alpha] Portage problem Brian Parkhurst
2004-10-11 19:07       ` Brian Parkhurst
2004-10-13  5:22         ` Brian Parkhurst

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='016f01c4afb9$6a7aa690$3301a8c0@ICHIRO' \
    --to=brianp@spamcop.net \
    --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