2011/6/1 Marcela Mašláňová <mmaslano(a)redhat.com>:
On 06/01/2011 03:28 PM, Emmanuel Seyman wrote:
>
> Now that Fedora 15 is out, I was hoping we would work perl 5.14 in
> rawhide quickly enough as to be able to fix all the resulting bugs in
> time for Fedora 16 release.
>
> Is anything planned?
>
> Emmanuel
On perl porters were reported serious bugs with 5.14.0, so we are
waiting for 5.14.1 anyway.
At the moment I and Petr are working on new filters, better generating
of provides and requires and automatic script for rebuild of related
packages. We'd like to push all changes in test build target in koji.
Hopefully, this time it will be easier than rebuild for perl5.12.
For kicks, I rebuilt all perl-* packages in mock recently against
5.14. After getting all the arch-specific packages rebuilt in the
correct order (actually, just repeatedly rebuild all failing
arch-dependent packages until no more builds succeed), everything else
pretty much just works. Most failures are fixed simply by updating to
latest upstream version or applying a patch from rt - and I pushed a
bunch of these into rawhide a few weeks ago. I never got around to
finalising the rest, but ended up with around 35 failures, many of
which have an upstream update available or a patch in rt. From the
list I have here at the minute (which may be incomplete), these
packages had non-trivial problems:
perl-Class-DBI-AsForm
perl-DBM-Deep
perl-Mail-MboxParser
perl-mogilefs-server
perl-Net-FTPServer
perl-Net-SSH-Perl
perl-OpenFrame
perl-Pugs-Compiler-Rule
perl-rpm-build-perl
perl-Wx-Perl-DataWalker
I've got limited time for the next week or so, but will try to get a
proper list of failures, reasons, and (potential) fixes shortly after
that.
Bottom line, though, I'd rather see 5.14.0 in rawhide soon so that we
can iron out the difficulties together. A later update to 5.14.1
/should/ be trivial with no need for an additional mass rebuild.
Of course, the newly dual-lifed packages that were added to core in
5.14 need to be sub-packaged in perl.spec too as we have all of them
as separate packages already. I have a patch, but can't get my hands
on it until June 13th.
--
Iain.