Bug 1030603

Summary: Auto-requires issue with certain modules
Product: [Fedora] Fedora EPEL Reporter: Shawn Iwinski <shawn>
Component: drupal7Assignee: Shawn Iwinski <shawn>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: gwync, peter.borsa, shawn, stickster
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-24 22:10:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
drupal7-ultimate_cron.spec none

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.