From: "Mitch D." <futurehypoon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Can't upgrade portage or update/install ebuilds
Date: Tue, 13 Jun 2023 12:35:55 -0400 [thread overview]
Message-ID: <CAFp6V1gNyDmK0vm-psaBB3K6PhLDNpSJ3N5zzrm5s6M8Ku-49w@mail.gmail.com> (raw)
In-Reply-To: <u69v0d$8qs$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
On Tue, Jun 13, 2023 at 10:38 AM Grant Edwards <grant.b.edwards@gmail.com>
wrote:
> On 2023-06-12, Wol <antlists@youngman.org.uk> wrote:
> > On 09/06/2023 21:16, Grant Edwards wrote:
> >> On 2023-06-09, Daniel Pielmeier <billie@gentoo.org> wrote:
> >>
> >>> If it is only about gemato then temporary disable the rsync-verify flag
> >>> which pulls it in.
> >>>
> >>> # USE="-rsync-verify" emerge sys-apps/portage
> >>
> >> The problem I ran into is that you never know how many issues there
> >> are standing in the way of upgrading. The one time I decided to muscle
> >> my way through updating an "obsolete" Gentoo install, [...]
> >>
> >> You do learn alot about how portage/emerge works...
> >>
> > Learning that is a good idea maybe :-)
> >
> > But last time I had a well-out-of-date system, it was a long and
> > messy process ...
> >
> > What I did was, every time portage said "giving up" or "conflict found"
> > or whatever, I just took a note of as many of the packages I could
> > remember that portage said it could emerge, and then manually updated
> > them "emerge --update --one-shot".
> >
> > And any conflicts, if I dared, I simply deleted then "emerge -C
> --one-shot".
>
> IIRC, at one point Python was one of those problems, and I stupidly
> removed Python before realizing what that meant...
>
> Hilarity ensued.
>
> Removing/skipping as many of the non-essential "big" packages and
> their dependancies and getting the base system updated is indeed the
> best way to go.
I second this approach. When rescuing a Gentoo system, my first step would
be to deselect any and every non-critical package from @world, then try to
get @system updated through any means necessary. In the past, I've removed
packages instead of deselecting them, but I've had cases where depclean
refused to do anything because there were already dependency problems, and
sometimes it's hard to know what's safe to unmerge with "-C".
[-- Attachment #2: Type: text/html, Size: 2678 bytes --]
next prev parent reply other threads:[~2023-06-13 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 19:40 [gentoo-user] Can't upgrade portage or update/install ebuilds Nikolay Pulev
2023-06-09 19:55 ` [gentoo-user] " Grant Edwards
2023-06-09 20:04 ` [gentoo-user] " John Covici
2023-06-09 20:07 ` Daniel Pielmeier
2023-06-09 20:16 ` [gentoo-user] " Grant Edwards
2023-06-12 23:50 ` Wol
2023-06-13 14:38 ` Grant Edwards
2023-06-13 16:35 ` Mitch D. [this message]
2023-06-13 18:06 ` Laurence Perkins
2023-06-14 13:17 ` Michael
2023-06-10 9:47 ` [gentoo-user] " Nikolay Pulev
2023-06-10 17:32 ` Daniel Pielmeier
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=CAFp6V1gNyDmK0vm-psaBB3K6PhLDNpSJ3N5zzrm5s6M8Ku-49w@mail.gmail.com \
--to=futurehypoon@gmail.com \
--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