On 05/30/2012 09:42 AM, Petr Pisar wrote:
On Tue, May 29, 2012 at 03:36:15PM +0100, Paul Howarth wrote:
On 05/25/2012 03:52 PM, Marcela Mašláňová wrote:
Hi Perl SIG,
as you probably already found out the new Perl 5.16.0 was released.
http://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186903.html
The perl-5.16.0 is now building fine in scratch. You can find it in rc
branch of our Fedora perl git. More details about annual rebuild will be
next week.
I forgot fix versions of sub-packages in the specfile, I'll do it next
week. We might also put more modules into their own sub-packages.
Is the plan to do a "clean" rebuild of all perl modules, not pulling
in any built for perl 5.14.x? If so, I think the
perl(:MODULE_COMPAT_5.14.*) provides should be dropped in the 5.16.0
package, just to make sure that old modules don't get in.
That's the plan. I started some dry-runs using mock (new Fedora::Rebuild 0.9.0
feature) and discovered this will not work because of:
(1) YUM cannot install dual-lived module from perl-5.16.spec just because it's
lower version than the standalone dual-lived package (yes, perl-5.16 did not
merged all updates from CPAN). It crashes on installing minimal buildroot.
(2) There are dependenices by git and rpmbuild which will require modules in
minimal build-root.
So we need to rebuild those packages before removing old COMPAT Provide.
We have already set up f18-perl build-root in Koji for the mass rebuild. I'd
like start the rebuild in a few day once I resolve these issues.
Is it not possible to untag the problematic packages from f18-perl in koji?
Paul.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
