From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8957D158008 for ; Tue, 13 Jun 2023 16:36:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C1F8E09AB; Tue, 13 Jun 2023 16:36:06 +0000 (UTC) Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4B38CE08FA for ; Tue, 13 Jun 2023 16:36:06 +0000 (UTC) Received: by mail-vs1-xe33.google.com with SMTP id ada2fe7eead31-43b3b30bd55so364926137.3 for ; Tue, 13 Jun 2023 09:36:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686674165; x=1689266165; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=mQOc9J6JZpWqUMYh/bxI7DuoQJYDNduhA1Xz4I9THqo=; b=SCH+QzSb180U1cFteHVs0ZoJuL3wK1ZfJUEkhTaAAiIJ7gzeaL6jetHsKfKwAelbfR EuF1Anq/S62sz9ATdHe5QXwm3VSAKeCNuAnOLnyUGFaBi9gnO1kfPrWqmuzo8K7edHls SoBbA/SyuxlhT7IhdeucVFzVLTl2nu2y1+VVktnGcM6jkXpK6FLvKcGuqMofE7MyG+8r 7RSc/OOgcOEwcJ2J4b2ZNPAR/gfs1PYzvQ/u2ZE1EKLY9N5M/UXdaGcWWUjwFnAStTmz GdOSY/ZkVIFsejyqjY1V4+Qszqpw/jInIchldJCnbWCbOLTbrw5R68O2T7Pt9IoJPVWo BIUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686674165; x=1689266165; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mQOc9J6JZpWqUMYh/bxI7DuoQJYDNduhA1Xz4I9THqo=; b=OcTwWl/BEI2HuLlTDVGzDE90cB6VwmnslnAYOfB+lVLarlZXhnF0Ydbgehikbg7N5I Qkbp2berWhYT996qldO04GD5e0FoLYLPnpUGhIQBTMmAHqQVPEL4nBgRXh0EzP/i1Ag8 gd7nk5Ei0kEk9wmSgFmXZ313C765JSfbN1uBu8JuZVknRqPcObzNDx71pUM+NjRtWQ1w 5I9BtZB8d5wx5YEyBpJlHOoaUlylMZJqnQoBGIKcpvI94tD2eRJqlJ+3BJ4xvitzB9Aw MGHRjp6vtK1BDlDRCGzbJu0sAHidXykLcOb8yiXsK3eyCHxb/CIPnwAkZhCQRPDoYYnh lgaw== X-Gm-Message-State: AC+VfDysKCNKFthEsAlsdgiY72I4EKg3xD2XDan5c0lKcuXrUs9ybA8y LlGqZh8wiROBNFbEnZXiQ4r1zloU7yRyv6ik9DDb8png X-Google-Smtp-Source: ACHHUZ6DG0y/Py8o4Ac2zN4id5I1WZNdo0J7OdTf4mt2l/HMfqH+ns87YKShDNW6Fn7p5Ei9+V2teoEZC10rm1Uk9bA= X-Received: by 2002:a05:6102:302f:b0:43b:40e2:4031 with SMTP id v15-20020a056102302f00b0043b40e24031mr4061348vsa.7.1686674165201; Tue, 13 Jun 2023 09:36:05 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <62781de6-1696-1e3d-c316-c1cedc254383@gentoo.org> <241a4960-de51-4b18-7396-af4beb22434c@youngman.org.uk> In-Reply-To: From: "Mitch D." Date: Tue, 13 Jun 2023 12:35:55 -0400 Message-ID: Subject: Re: [gentoo-user] Re: Can't upgrade portage or update/install ebuilds To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="0000000000007801ab05fe056ede" X-Archives-Salt: 9d847d6c-ea7b-45e8-8aff-eca23060407a X-Archives-Hash: d014a43370c8fdaa9f8118bb6897ece7 --0000000000007801ab05fe056ede Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jun 13, 2023 at 10:38=E2=80=AFAM Grant Edwards wrote: > On 2023-06-12, Wol wrote: > > On 09/06/2023 21:16, Grant Edwards wrote: > >> On 2023-06-09, Daniel Pielmeier wrote: > >> > >>> If it is only about gemato then temporary disable the rsync-verify fl= ag > >>> which pulls it in. > >>> > >>> # USE=3D"-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". --0000000000007801ab05fe056ede Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Jun 13, 2023 at 10:38=E2=80=AFAM = Grant Edwards <grant.b.edwa= rds@gmail.com> wrote:
On 2023-06-12, Wol <antlists@youngman.org.uk<= /a>> 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-ve= rify flag
>>> which pulls it in.
>>>
>>> # USE=3D"-rsync-verify" emerge sys-apps/portage
>>
>> The problem I ran into is that you never know how many issues ther= e
>> are standing in the way of upgrading. The one time I decided to mu= scle
>> 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. Whe= n rescuing a Gentoo system, my first step would be to deselect any and ever= y non-critical package from @world, then try to get=C2=A0@system updated th= rough any means necessary. In the past, I've removed packages instead o= f deselecting them, but I've had cases where depclean refused to do any= thing because there were already dependency problems, and sometimes it'= s hard to know what's safe to unmerge with "-C".
<= /div> --0000000000007801ab05fe056ede--