Bug 1818 - perl-File-MimeInfo doesn't build with perl-5.14.0
Summary: perl-File-MimeInfo doesn't build with perl-5.14.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Jerome Quelin
QA Contact:
URL: https://rt.cpan.org/Public/Bug/Displa...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-16 05:18 CEST by Ahmad Samir
Modified: 2011-06-20 22:36 CEST (History)
0 users

See Also:
Source RPM: perl-File-MimeInfo
CVE:
Status comment:


Attachments

Description Ahmad Samir 2011-06-16 05:18:13 CEST
Hello, there're two issues here:
- perl-File-MimeInfo doesn't build with perl-5.14.0, there seems to be a possible fix https://rt.cpan.org/Public/Bug/Display.html?id=66841

- /usr/bin/mimetype hardcodes the perl version:
$ mimetype 1
bash: /usr/bin/mimetype: /usr/bin/perl5.12.2: bad interpreter: No such file or directory

so it should depend on the specific perlapi-$VERSION of the perl it was built with, so that we don't forget to rebuild it with the next perl major upgrade.

Assigning to the perl maintainer.
Comment 1 Jerome Quelin 2011-06-17 13:58:24 CEST
- patch added to package.

- perl scripts installed in /usr/bin have their shebang line replaced with the exact path to the perl that built the package. and adding a perlapi requires would not work, since it *also* breaks on minor perl upgrades. we need to rebuild all of those every time there's a perl upgrade. i need to check whether it's possible to keep /usr/bin/perl in the shebang line

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 2 Ahmad Samir 2011-06-17 21:48:41 CEST
OK, thanks for the clarification.
Comment 3 Jerome Quelin 2011-06-19 19:47:03 CEST
fyi - i've committed in svn+ssh://svn.mageia.org/svn/packages/cauldron/perl/current a script named find-need-rebuild which will find all packages providing a perl script with a wrong shebang.
Comment 4 Ahmad Samir 2011-06-20 00:49:47 CEST
That should improve things.

The problem is, it'll only catch installed packages, but usually there're many uninstalled packages than installed ones.
Comment 5 Jerome Quelin 2011-06-20 13:45:36 CEST
indeed, but there's no way to know the shebang used by a non-installed package. note however that i have almost all perl packages installed locally.
Comment 6 Ahmad Samir 2011-06-20 22:36:55 CEST
(All of them? great, that should work then :)).

Note You need to log in before you can comment on or make changes to this bug.