Bug 868590
| Summary: | build error: File not found (pesign.conf) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mr-4 <mr.dash.four> |
| Component: | pesign | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | pjones |
| 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: | 2012-10-22 14:36:48 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: | |
| Embargoed: | |||
This seems to have been caused by compilation of MASTER branch sources (from git, as I did not have any joy with v0.99). When I managed to finally compile v0.99 (see Comment #2 on Bug 868591) this is no longer an issue and this file is now generated and placed in its place in the resulting rpm, so this bug can now be closed. |
Description of problem: During build (using srpm) I get the following error: RPM build errors: File not found: /builddir/build/BUILDROOT/pesign-0.99-3.fc17.x86_64/usr/lib/tmpfiles.d/pesign.conf Version-Release number of selected component (if applicable): 0.99, *but* with the newest source from git (the 0.99 version can't get this far as I am getting other errors) How reproducible: Always Steps to Reproduce: 1. rpmbuild -bb pesign.spec, using the latest git source 2. 3. Actual results: The above error Expected results: Compilation and creating the rpm to succeed Additional info: The only reference to this file is in the .spec file as follows: %{_prefix}/lib/tmpfiles.d/pesign.conf but that file is nowhere to be seen in the sources, nor is it created during build. A "workaround" (if one could call it that!) is to delete that reference in order for the build to succeed.