From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] world upgrade a mess, need some advise
Date: Tue, 2 Jul 2024 03:57:36 -0500 [thread overview]
Message-ID: <f0d09e8f-f4d0-4399-a6b4-92d3897d210e@gmail.com> (raw)
In-Reply-To: <m3msn0sb2c.wl-covici@ccs.covici.com>
John Covici wrote:
> On Mon, 01 Jul 2024 19:16:11 -0400,
> Wol wrote:
>> On 01/07/2024 20:27, John Covici wrote:
>>>> I seem to recall having to run that during that upgrade as well. It
>>>> reinstalled a lot of packages but it worked. It's worth trying for sure.
>>>>
>>> But don't you do that after the upgrade -- I can't even start the
>>> upgrade, so how would perl-cleaner help?
>> Trust me it does!
>>
>> You have a bunch of old perl scripts, one (or more) of which are
>> blocking the upgrade. perl-cleaner will upgrade them to the
>> latest version compatible with your current perl, which then
>> frees up the perl upgrade. Make sure you run perl-cleaner again
>> afterwards, to ensure you have the absolute latest version of all
>> these extra bits. In fact, you should really run perl-cleaner
>> after every "emerge --update". Most people most of the time
>> either forget or don't realise ...
>>
>> Don't forget, if I've got it right, perl and CPAN predate linux,
>> so if there's an argument about who needs to change, perl simply
>> says "I was here first, you have to do it *my* way".
>>
>> Cheers,
>> Wol
>>
> I ran perl-cleaner and it is going right now -- installing perl itself
> and lots of others -- thanks a lot people.
>
Just some additional info. I did a update on my main rig the other
day. According to emerge, everything is just fine. I ran perl-cleaner
with pretend, it is wanting to emerge some 200 packages. Looks like Wol
is right. We need to run this after each OS update. Maybe this should
be documented in a wiki somewhere???
Dale
:-) :-)
P. S. Monitor left Memphis hub. Should arrive today. I hope.
next prev parent reply other threads:[~2024-07-02 8:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 10:04 [gentoo-user] world upgrade a mess, need some advise John Covici
2024-07-01 10:34 ` Michael
2024-07-01 11:23 ` Wols Lists
2024-07-01 13:53 ` Dale
2024-07-01 19:27 ` John Covici
2024-07-01 19:54 ` Dale
2024-07-01 23:16 ` Wol
2024-07-02 3:54 ` John Covici
2024-07-02 8:57 ` Dale [this message]
2024-07-02 9:17 ` Arve Barsnes
2024-07-02 12:54 ` Dale
2024-07-02 16:49 ` Wols Lists
2024-07-02 22:04 ` Arve Barsnes
2024-07-02 23:33 ` Dale
2024-07-03 0:20 ` Eli Schwartz
2024-07-03 0:34 ` Dale
2024-07-03 10:52 ` Michael
2024-07-03 13:24 ` Dale
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=f0d09e8f-f4d0-4399-a6b4-92d3897d210e@gmail.com \
--to=rdalek1967@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