From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: William Kenworthy <billk@iinet.net.au>
Subject: Re: [gentoo-user] Re: can fix preserved-rebuild ...
Date: Sun, 7 Jun 2009 17:02:47 +0200 [thread overview]
Message-ID: <200906071702.47892.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <1244338101.15834.31.camel@rattus>
On Sunday 07 June 2009 03:28:21 William Kenworthy wrote:
> > As for the OP, I can only guess what might be causing this. Let's start
> > with obvious stuff:
> >
> > 1. Is portage the latest version for your arch?
> > 2. What does revdep-rebuild return?
> > 3. What is your arch, and is it a mixture of stable and ~?
>
> The system is quite a few years old - the original install was ~2000,
> and has quite a few hardware upgrades/rebuilds in between. Current (for
> at least a couple of years) cpu is amd athlon barton 2500+.
>
> Software is a mix of stable, ~x86 and pinned (mostly particular ~x86 at
> the time) working versions to avoid some of the upgrade treadmill.
Your libusb is currently latest, your portage-utils and portage are not.
I honestly think that debugging this will be an exercise in futility unless
you can find a reference somewhere that says which versions of which portage
tools are incompatible with which other ones, and why...
I'm also not sure anymore about which portage version was first to support
sets. What I did was blow my top at the forced downgrade of portage at Zac's
whim, and unmasked portage. Lots of troubles immediately and at once went away
when I did this.
I'd suggest you switch to ~arch and tolerate the upgrade treadmill. A lot of
that is packages that are rapidly and often changing. If you sync and upgrade
once a week or fortnight, you'll find you upgrade package X just once, not
several times during that period.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-06-07 15:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 12:03 [gentoo-user] can fix preserved-rebuild William Kenworthy
2009-06-06 16:23 ` [gentoo-user] " walt
2009-06-06 17:23 ` Alan McKinnon
2009-06-06 21:10 ` walt
2009-06-06 21:37 ` Alan McKinnon
2009-06-06 21:50 ` Dale
2009-06-07 1:28 ` William Kenworthy
2009-06-07 15:02 ` Alan McKinnon [this message]
2009-06-07 15:21 ` walt
2009-06-07 15:38 ` Alan McKinnon
2009-06-07 16:15 ` Graham Murray
2009-06-07 16:11 ` Neil Bothwick
2009-06-08 12:25 ` William Kenworthy
2009-06-08 12:32 ` William Kenworthy
2009-06-08 12:53 ` Neil Bothwick
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=200906071702.47892.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=billk@iinet.net.au \
--cc=gentoo-user@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