Bug 1030603 - Auto-requires issue with certain modules
Summary: Auto-requires issue with certain modules
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: drupal7
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Shawn Iwinski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-14 19:07 UTC by Shawn Iwinski
Modified: 2013-11-24 22:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-11-24 22:10:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
drupal7-ultimate_cron.spec (1.26 KB, text/x-rpm-spec)
2013-11-14 19:07 UTC, Shawn Iwinski
no flags Details

Description Shawn Iwinski 2013-11-14 19:07:51 UTC
Created attachment 824122 [details]
drupal7-ultimate_cron.spec

Description of problem:

Auto-requires throws an rpmbuild error for certain modules.


Version-Release number of selected component (if applicable):
drupal7-7.23-3


How reproducible:
* rpmbuild the attached RPM spec file


Actual results:

RPM build errors:
    line 53: Dependency tokens must begin with alpha-numeric, '_' or '/': - Initial package


Expected results:

Successful RPM build and correct auto-requires being set

Comment 1 Shawn Iwinski 2013-11-24 22:10:21 UTC
I figured out the issue here... on RHEL 5/6, "/usr/lib/rpm/find-requires" does not correctly ignore the missing "#!" line in wrongfully executable PHP files and tries to add invalid "<?php" as a dependency.  The solution here is for the packager to remove the executable bit from Drupal files that do not begin with "#!".  The packager could bypass the auto-requires (by adding "AutoReqProv: no" to the spec), and manually specify the dependencies, but when he/she runs rpmlint against the resulting RPMs it should throw "E: script-without-shebang" errors which the packager should fix anyway (and then auto-requires could then again be used).  I will add this information to the packaging guidelines draft.


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