How did the Perl 5.20 upgrade go for you?

dilfridge · Last edited by dilfridge on Thu Feb 12, 2015 5:24 pm; edited 1 time in total

It would be great to have some numbers how well (or not) the new Perl upgrade mechanisms are working.

If you encounter problems, please make sure

no perl-core/* packages in your world file /var/lib/portage/world
This command
Code:

for name in $(qlist -IC 'perl-core/*') ; do equery depends $name ; done
shows only virtuals depending on perl-core
Try upgrading with
Code:

emerge -uDNav --backtrack=100 world
If this does not work, try upgrading with
Code:

emerge -uNav --backtrack=100 world
(i.e. without -D).

If you're stuck because of "many packages depending on Perl 5.18", attach emerge --info and your full portage output to bug 539414.

davidm · Guru Joined: 26 Apr 2009 Posts: 557 Location: US

No real problems. Just this after running perl cleaner

Anon-E-moose · Posted: Tue Feb 10, 2015 2:48 am Post subject:

I had the same file left with the same message, and just deleted it after checking that it existed under 5.20*
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

khayyam · Posted: Tue Feb 10, 2015 3:00 am Post subject:

dilfridge ...

It's not hit x86 as yet, but I'm not the least bit worried, I'd not had any of the issues reported with 5.18.2-2 (though I did have to do some clean up for PERL5LIB), and looking at the output from the above commands I'm not expecting any with this particular upgrade (fingers crossed). Some of the posts on planet gentoo no doubt helped at the time, and so thanks for that ... and of course the above heads-up.

best ... khay

P1neapple · n00b Joined: 18 Jul 2014 Posts: 35

perl-core/Module-Build was blocking the update to perl-core/Module-Build but it seems that after I updated it, it resolved itself :roll:

_________________
Gentoo currently running in Virtualbox, hoping to switch to real hardware soon...

xaviermiller · Posted: Tue Feb 10, 2015 8:08 am Post subject:

No big issues : perl-cleaner, and if I had blockers, I removed them manually then called "emerge --update" to rebuild the good ones.
_________________
Kind regards,
Xavier Miller

Roman_Gruber · Posted: Tue Feb 10, 2015 11:48 am Post subject:

229566 · Tux's lil' helper Joined: 16 Aug 2010 Posts: 127

No issues at all here. There were a few blockers that resolved automagickally. Also perl-cleaner did its job with no error.

depontius · Advocate Joined: 05 May 2004 Posts: 3509

Actually the perl update went through with no problems. When I started the update, some of the other packages getting updated at the same time had (capital 'B') Blockers. When emerge listed those blockers, it also listed even more issues for Perl. I left the Perl upgrade alone for the moment, and fixed the other issues. After that the Perl update only had (lower case 'B') blockers, and proceeded uneventfully.
_________________
.sigs waste space and bandwidth

dilfridge · Posted: Tue Feb 10, 2015 6:29 pm Post subject:

Raffi · l33t Joined: 17 Mar 2003 Posts: 731 Location: Moscow, Id.

The upgrade had mostly minor issues that were pretty easy to deal with. The --backtrack=100 world tip solved the only major head scratcher I ran into. However, two packages are not able to deal with the upgrade (nvi and graphviz). Bug reports have been opened on both.

NeddySeagoon · Posted: Tue Feb 10, 2015 7:09 pm Post subject:

dilfridge,

The first time, I ripped all the blockers out by hand until the perl upgrade ran.
The second time I was aware of the one liners to look at the world file and manage the virtuals.
Aftel the update to perl-cleaner, it just worked.

I have about 8 installs, not counting Raspberry Pis, so I got plently of practice.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Raffi · l33t Joined: 17 Mar 2003 Posts: 731 Location: Moscow, Id.

Looks like subversion also has a problem with the latest perl.

paulj · Guru Joined: 30 Sep 2004 Posts: 523 Location: Wales, UK

Didn't work out of the box, but following the instructions to update the perl modules and run perl-cleaner etc resolved the blockers.

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

I'm going with no problems because I didn't even notice there was a perl update.

My complements to the devs

_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

v_andal · Guru Joined: 26 Aug 2008 Posts: 543 Location: Germany

In my case, the upgrade went fine, without any issues, but then I've tried "emerge -p --depclean" and this reported some blockers (I believe XML-Simple, XML-LibXML and perl-core/podlators). After running perl-cleaner things were working smoothly again.

So, this upgrade of perl was unbelievably easy

init3 · n00b Joined: 26 Dec 2013 Posts: 21

No real issues, as at almost all (excepting the first one) perl updates before.
After world's update perl-cleaner check find an atom (dev-perl/Locale-gettext) to be rebuilt (strange thing, that should NOT be).

And another known, but not fixed yet issue:
Orphant file (/usr/lib64/perl5/vendor_perl/5.18.2/XML/SAX/ParserDetails.ini) without any warning (this file is used and namaged by several dev-perl/* packages, so it can't belong to any _one_ of them).
Exact one was regenerated for Perl-5.20 (/usr/lib64/perl5/vendor_perl/5.20.1/XML/SAX/ParserDetails.ini).
So, I can just recursively remove /usr/lib64/perl5/vendor_perl/5.18.2.
_________________
Excuse me my English.

ff11 · l33t Joined: 10 Mar 2014 Posts: 664

"emerge -auDN @world" fail for me, then:
"emerge -auDN --backtrack=30 @world" fail too, then
"emerge --deselect $(qlist -IC 'perl-core/*')" and again "emerge -auDN --backtrack=30 @world" work
is building now, for me to make the final "perl-cleaner -all"
Deselect some package is doing it work for me

schorsch_76 · Guru Joined: 19 Jun 2012 Posts: 450

The world update did run smoothly, After the update i do regulary a "emerge --ask --depclean" It complained that dependencies were not fullfilled in perl packages. So i ran "perl-cleaner --all". Afterwards the depclean did run as expected.

bubbl07 · Posted: Fri Feb 13, 2015 6:08 pm Post subject:

user · Apprentice Joined: 08 Feb 2004 Posts: 209

+1
for poll and forum feedback.

John R. Graham · Posted: Fri Feb 13, 2015 10:51 pm Post subject:

Had to manually remove perl-core/Compress-Raw-Zlib, which has apparently become part of dev-lang/perl-5.20*. Portage couldn't figure that out on its own. Otherwise, smooth sailing.

- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters.

OldTango · l33t Joined: 21 Feb 2004 Posts: 718

Seemed to go alright on my three Gentoo systems. However perl-cleaner --all didn't seem to clean anything or at least everything. All three of my systems reported

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1629 Location: U.S.A.

I couldn't get anything here to work. Except for manually removing stuff.
Followed part of this and the bug report: https://forums.gentoo.org/viewtopic-t-1010432-start-25-postdays-0-postorder-asc-highlight-.html

Not done yet, but
1) emerge -C ~ the first 10 blockers of >61 blockers
2) Stopped that and emerge -C virtual/perl-*
3) Then emerge =dev-lang/perl-5.20.1-r4:0/5.20
is now emerging 1 of 86. And just finished.
4) perl-cleaner --all
which is doing 1 of 16 now.
5) Looks like good idea to run: perl-cleaner --reallyall also cause wants to upgrade 72 files.
Probably not good idea to reboot anytime during this process.

So far so good. Going to emerge world before reboot.

***UPDATE:
I'm doing this now on my laptop which haven't done in long long time. This method is working fine for updating from perl-5.18.2-r1 to 5.20.2 on it. Right now perl is updated and is emerging perl files 5 of 64. So looks like this method has worked on 2 or my boxes.
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright

khayyam