Summary: | rpmbuild -ba errors out with "File not found by glob" | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | NWoodward |
Component: | Build | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | NWoodward, sewhyte |
Priority: | P2 | Keywords: | MassUpdate |
Version: | 2.2.22 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
NWoodward
2012-02-03 18:07:59 UTC
The man pages for ab, apxs and logresolve have been moved from man section 8 to 1 in r1221296 in order to reflect a changed installation directory (moved from sbin to bin). This seems to be an unintended side-effect of work for trunk, because trunk and 2.2 use the same build scripts for documentation including man pages. Need to check, whether we want to fix the specs file or move the man pages back for 2.2.x. Work Around: I recently encountered similar build errors: RPM build errors: File not found by glob: /var/tmp/httpd-2.2.22-1-root/usr/share/man/man8/ab* File not found by glob: /var/tmp/httpd-2.2.22-1-root/usr/share/man/man8/logresolve* File not found by glob: /var/tmp/httpd-2.2.22-1-root/usr/share/man/man8/apxs.8* My work-around was to edit the httpd.spec file and comment out the rules for these man pages. After that, I reran the build successfully $> rpmbuild --clean httpd.spec $> rpmbuild -ba --sign httpd.spec Hope this helps until the apache team finds and tell us the real problem and solution Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated. |