From: Alan Grimes <alonzotg@verizon.net>
To: gentoo-user@lists.gentoo.org, Andreas Fink <finkandreas@web.de>
Subject: Re: [gentoo-user] Libsld, what gives?
Date: Wed, 16 Nov 2022 11:17:49 -0500 [thread overview]
Message-ID: <85f1b6a2-699c-7aed-30db-0ef4df1e87e8@verizon.net> (raw)
In-Reply-To: <20221116155914.7d2f3304@web.de>
Andreas Fink wrote:
> On Wed, 16 Nov 2022 02:11:18 -0500
> Alan Grimes <alonzotg@verizon.net> wrote:
>
>> I'm jackhammering the system now and I'm getting about 50% error spew
> I would suggest a different tool than a jackhammer to fix the problems.
Basic assumption: Problems are caused by outdated packages.
Underlying problem: In order to break a log-jam it is necessary to purge
outdated packages.
Facts on the ground: The only way to make ANY progress in updating
outdated packages is to jackhammer the hell out of all packages in hopes
that some of them might sucessfully update which will, hopefully either:
A. allow other packages to sucessfully update
B. Expose something that can be fixed.
Once the logjam is broken, the system is then --emptytree world'ed and
declared healthy... Expected failure rate is on the order of 0.3% of
hopefully unimportant packages.
It is known that the KDE group of packages has incomplete dependency
graph because it is hopelessly convoluted, and it always causes problems
and the only way to break through it is the jackhammer approach.
LLVM and friends also fails to update when updating within a single slot
and this is VERY annoying...
What causes me to post to the list is when I get failures that prevent
me from even beginning to jackhammer the system.
--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
next prev parent reply other threads:[~2022-11-16 16:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84f5abeb-2557-10b7-9cca-5845215db109.ref@verizon.net>
2022-11-16 7:11 ` [gentoo-user] Libsld, what gives? Alan Grimes
2022-11-16 14:00 ` [gentoo-user] " Grant Edwards
2022-11-16 15:55 ` Laurence Perkins
2022-11-16 23:02 ` Peter Humphrey
2022-11-16 14:59 ` [gentoo-user] " Andreas Fink
2022-11-16 16:01 ` Laurence Perkins
2022-11-16 16:17 ` Alan Grimes [this message]
2022-11-16 16:40 ` Laurence Perkins
2022-11-16 22:52 ` Alan Grimes
2022-11-17 0:18 ` Laurence Perkins
2022-11-17 0:26 ` Michael Cook
2022-11-16 15:14 ` Julien Roy
2022-11-17 6:52 ` Paul Colquhoun
2022-11-17 12:52 ` Dr Rainer Woitok
2022-11-17 13:25 ` Peter Humphrey
2022-11-17 13:14 ` [gentoo-user] " Grant Edwards
2022-11-17 13:48 ` Neil Bothwick
2022-11-17 14:12 ` Mark Knecht
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=85f1b6a2-699c-7aed-30db-0ef4df1e87e8@verizon.net \
--to=alonzotg@verizon.net \
--cc=finkandreas@web.de \
--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