version of ExtUtils::Manifest too strict?

[Alex Lancaster]

Does the version of ExtUtils::Manifest really need to be strictly
greater than or equal to 1.52?

Currently this blocks me updating the Fedora package of BioPerl to
1.6.1, because the version of perl that Fedora ships is on 1.51 and
hence the build fails with:

Checking prerequisites...
 - ERROR: ExtUtils::Manifest (1.51_01) is installed, but we need version >= 1.52

Full logs are here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1787483
http://koji.fedoraproject.org/koji/getfile?taskID=1787483&name=build.log

This is true even with the version of Perl in rawhide/F-12 etc.
(ExtUtils::Manifest is in the base perl package).

If it really is necessary, I would like to be armed with a good argument
why it needs to be updated, since the Perl package maintainer would have
to update the entire Perl package simply to get a more recent version of
one small subpackage.

Regards,
Alex
_______________________________________________
Bioperl-l mailing list
Bioperl-l@...
http://lists.open-bio.org/mailman/listinfo/bioperl-l

[Chris Fields-5]

Alex,

Not sure why ExtUtils::Manifest can't be bundled as a separate perl  
package alone.  It is part of perl core but it's also available on  
CPAN separately from perl itself:

http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.57/lib/ExtUtils/Manifest.pm

This is the commit message for that BTW.  This allows spaces in file  
names for the MANIFEST.  v1.52 is a bug fix and is required.

http://code.open-bio.org/svnweb/index.cgi/bioperl/revision/?rev=15673

chris

On Nov 4, 2009, at 1:30 AM, Alex Lancaster wrote:

> Does the version of ExtUtils::Manifest really need to be strictly
> greater than or equal to 1.52?
>
> Currently this blocks me updating the Fedora package of BioPerl to
> 1.6.1, because the version of perl that Fedora ships is on 1.51 and
> hence the build fails with:
>
> Checking prerequisites...
> - ERROR: ExtUtils::Manifest (1.51_01) is installed, but we need  
> version >= 1.52
>
> Full logs are here:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=1787483
> http://koji.fedoraproject.org/koji/getfile?taskID=1787483&name=build.log
>
> This is true even with the version of Perl in rawhide/F-12 etc.
> (ExtUtils::Manifest is in the base perl package).
>
> If it really is necessary, I would like to be armed with a good  
> argument why this ca
> why it needs to be updated, since the Perl package maintainer would  
> have
> to update the entire Perl package simply to get a more recent  
> version of
> one small subpackage.
>
> Regards,
> Alex
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l@...
> http://lists.open-bio.org/mailman/listinfo/bioperl-l

_______________________________________________
Bioperl-l mailing list
Bioperl-l@...
http://lists.open-bio.org/mailman/listinfo/bioperl-l

[Alex Lancaster]

>>>>> Chris Fields  writes:

> Alex, Not sure why ExtUtils::Manifest can't be bundled as a separate
> perl package alone.  It is part of perl core but it's also available
> on CPAN separately from perl itself:

> http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.57/lib/ExtUtils/Manifest.pm

Hi Chris,

Yes, in principle it would be possible to have this split out as a
separate package (currently it's a "subpackage" under the main perl
package), unfortunately that's just not the way it's currently done in
Fedora (probably because it's part of the core set and they like to
update all relevant packages in one step) and I have little control over
that.

As I suspected, the perl maintainer is not at all enthusiastic for
updating the whole of perl just for that package (except for rawhide
which would mean that bioperl 1.6.1 would not be available until F-13,
about 6 months from now).  See:

http://bugzilla.redhat.com/show_bug.cgi?id=533562#c1

Obviously I am not happy with this situation either, because it will
freeze bioperl on Fedora at 1.6.0 for about 6 months, so can you
recommend any temporary workarounds in the meantime?

> This is the commit message for that BTW.  This allows spaces in file
> names for the MANIFEST.  v1.52 is a bug fix and is required.

> http://code.open-bio.org/svnweb/index.cgi/bioperl/revision/?rev=15673

Perhaps I could create a patch that renamed files with spaces in them to
ones with no spaces and then rename them again upon installation.

Can you point me to which files are the problematic ones that triggered
the dependency for 1.52?  Perhaps I can figure a workaround.

Meanwhile I will press the maintainer of perl in Fedora to perhaps
reconsider his position (e.g. if another update for perl is going out
for another reason, like a security update, perhaps he could roll in the
1.52 update at the same time).

Cheers,
Alex
_______________________________________________
Bioperl-l mailing list
Bioperl-l@...
http://lists.open-bio.org/mailman/listinfo/bioperl-l

[Chris Fields-5]

On Nov 9, 2009, at 5:44 PM, Alex Lancaster wrote:

>>>>>> Chris Fields  writes:
>
>> Alex, Not sure why ExtUtils::Manifest can't be bundled as a separate
>> perl package alone.  It is part of perl core but it's also available
>> on CPAN separately from perl itself:
>
>> http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.57/lib/ExtUtils/Manifest.pm
>
> Hi Chris,
>
> Yes, in principle it would be possible to have this split out as a
> separate package (currently it's a "subpackage" under the main perl
> package), unfortunately that's just not the way it's currently done in
> Fedora (probably because it's part of the core set and they like to
> update all relevant packages in one step) and I have little control  
> over
> that.
>
> As I suspected, the perl maintainer is not at all enthusiastic for
> updating the whole of perl just for that package (except for rawhide
> which would mean that bioperl 1.6.1 would not be available until F-13,
> about 6 months from now).  See:
>
> http://bugzilla.redhat.com/show_bug.cgi?id=533562#c1
>
> Obviously I am not happy with this situation either, because it will
> freeze bioperl on Fedora at 1.6.0 for about 6 months, so can you
> recommend any temporary workarounds in the meantime?

Well, if you don't absolutely require the MANIFEST for the final  
package you can forego the requirement.  The file in question that  
triggered the requirement is a data file used only for testing:

t/data/test 2.txt

>> This is the commit message for that BTW.  This allows spaces in file
>> names for the MANIFEST.  v1.52 is a bug fix and is required.
>
>> http://code.open-bio.org/svnweb/index.cgi/bioperl/revision/?rev=15673
>
> Perhaps I could create a patch that renamed files with spaces in  
> them to
> ones with no spaces and then rename them again upon installation.
>
> Can you point me to which files are the problematic ones that  
> triggered
> the dependency for 1.52?  Perhaps I can figure a workaround.
>
> Meanwhile I will press the maintainer of perl in Fedora to perhaps
> reconsider his position (e.g. if another update for perl is going out
> for another reason, like a security update, perhaps he could roll in  
> the
> 1.52 update at the same time).
>
> Cheers,
> Alex

I would point out that this is a fairly significant bug fix for  
ExtUtils::Manifest.  A newer point release of perl is now available  
(5.10.1) that contains the fix and has a fix for a performance  
regression that popped up in 5.10.0.

chris
_______________________________________________
Bioperl-l mailing list
Bioperl-l@...
http://lists.open-bio.org/mailman/listinfo/bioperl-l