Tracker for eventual Perl 5.24 stabilization. No talking please.
Created attachment 468132 [details] stabilization list, v1
Created attachment 469206 [details] stabilization list, v2 Fix XSLoader version
Arches please proceed with testing and stabilizing the attached list at your own leisure. Target: all stable arches. One remark, it makes sense to do the actual stabilization of Perl & friends a bit later than the stabilization of perl-cleaner in bug 614696 - so users first get the new perl-cleaner and afterwards update Perl.
(In reply to Andreas K. Hüttel from comment #3) > One remark, it makes sense to do the actual stabilization of Perl & friends > a bit later than the stabilization of perl-cleaner in bug 614696 - so users > first get the new perl-cleaner and afterwards update Perl. Is there any hard reason for it? If so, why not bump the PDEPEND in perl to >=perl-cleaner-2.25. So far, test-results look good on arm, arm64, ppc & ppc64.
(In reply to Michael Weber from comment #4) > (In reply to Andreas K. Hüttel from comment #3) > > One remark, it makes sense to do the actual stabilization of Perl & friends > > a bit later than the stabilization of perl-cleaner in bug 614696 - so users > > first get the new perl-cleaner and afterwards update Perl. > > Is there any hard reason for it? If so, why not bump the PDEPEND in perl to > >=perl-cleaner-2.25. > > So far, test-results look good on arm, arm64, ppc & ppc64. If portage works fine then both should get installed in the same emerge run and afterwards the user can run the new perl-cleaner. So, OK. This is mostly about the cases when the update with emerge does not work properly... and these are hard to describe given the many configurations out there. Then again, the core functionality of perl-cleaner is identical in both versions. So should not be a big problem either.
Comment on attachment 469206 [details] stabilization list, v2 Moved to separate BZ field
arm arm64 ppc ppc64 stable.
A quick note about: after put the list to package.keywords, emerge -DNu world --backtrack=1000 didn't work. To emerge perl I had to emerge -C perl, then the list was emerged successfully. After that, emerge -DNu world with and without a backtrack didn't work (because of a conflict between the older and newer perl) Then, perl-cleaner --reallyall worked for me After that emerge -DNu world worked. If this is fine for you I will stabilize that.
(In reply to Agostino Sarubbo from comment #8) > A quick note about: > > after put the list to package.keywords, emerge -DNu world --backtrack=1000 > didn't work. > To emerge perl I had to emerge -C perl, then the list was emerged > successfully. > After that, emerge -DNu world with and without a backtrack didn't work > (because of a conflict between the older and newer perl) > Then, perl-cleaner --reallyall worked for me > After that emerge -DNu world worked. > > If this is fine for you I will stabilize that. OK so I prepared a mostly-stable test machine, added the stabilization file into package.keywords, and emerge was able to do the upgrade without any special preparations. I'm not sure what I am doing different... I.e., all works fine here. Ago- I suggest you go ahead with the stabilization.
amd64 stable
x86 stable
Stable for HPPA.
alpha, ia64, sparc: ping! It would be very useful to have this bug done and resolved. (It's effectively blocking other maintenance work on Perl...)
I just had this happen during an automated build starting with a clean gentoo container. I assume this is relevant to this bug, because it effectively means that the current packages in tree are not working together. !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-lang/perl:0 (dev-lang/perl-5.22.3_rc4:0/5.22::gentoo, installed) pulled in by =dev-lang/perl-5.22* required by (virtual/perl-Data-Dumper-2.158.0-r1:0/0::gentoo, installed) ^ ^^^^^ dev-lang/perl:0/5.22= required by (virtual/perl-File-Temp-0.230.400-r5:0/0::gentoo, installed) ^^^^^^^^ (and 14 more with the same problems) (dev-lang/perl-5.24.1-r1:0/5.24::gentoo, ebuild scheduled for merge) pulled in by =dev-lang/perl-5.24* required by (virtual/perl-Scalar-List-Utils-1.420.200_rc-r1:0/0::gentoo, ebuild scheduled for merge) ^ ^^^^^ (and 4 more with the same problem) See https://travis-ci.org/simonvanderveldt/simonvanderveldt-overlay/builds/224929151 for the full log
Since I can't delete a comment: please disregard the above comment. I've commented on https://bugs.gentoo.org/show_bug.cgi?id=615864
Stable on alpha.
sparc stable
@ IA64: PING! *NOW* would be an excellent time to finally handle this bug!
ia64 stable. Last arch. Closing.
