Bug 1030603 - Auto-requires issue with certain modules
Auto-requires issue with certain modules
Product: Fedora EPEL
Classification: Fedora
Component: drupal7 (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Shawn Iwinski
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-11-14 14:07 EST by Shawn Iwinski
Modified: 2013-11-24 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-24 17:10:21 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Shawn Iwinski 2013-11-14 14:07:51 EST
Created attachment 824122 [details]

Description of problem:

Auto-requires throws an rpmbuild error for certain modules.

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

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 17:10:21 EST
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.