Bug 838657
| Summary: | Invalid %verify token: owner | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jiri Popelka <jpopelka> |
| Component: | rpm | Assignee: | Fedora Packaging Toolset Team <packaging-team> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | ffesti, jnovy, packaging-team, pknirsch, pmatilai, thozza |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-07-10 07:29:28 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: | |||
It's an error in max-rpm: the verify attribute is (and always has been) "user", not "owner". Ugh, this same error is present in the newer RPM Guide as well: http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s05.html I've "fixed" this upstream now by accepting "owner" as an alias to "user" since its so widely documented and trivial to address: http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=d1dcc53dfb7658b46c108a4cd011439c2a6b45ea |
In dhcp.spec I have: %attr(0644,dhcpd,dhcpd) %verify(not size md5 mtime) %config(noreplace) %{_localstatedir}/lib/dhcpd/dhcpd.leases when I change the owner:group of the file and run 'rpm -V dhcp' I get .....UG.. c /var/lib/dhcpd/dhcpd.leases So good so far. But when I try to add 'owner' and 'group' to the list of %verify exclusions to look like %verify(not size md5 mtime owner group) rpm keeps telling me that: 'Invalid %verify token: owner' http://www.rpm.org/max-rpm/s1-rpm-inside-files-list-directives.html#FTN.AEN8744 says that: "RPM will automatically exclude file attributes from verification if it doesn't make sense for the type of file.", but this doesn't seem to be the case because as I pointed above rpm obviously use the 'owner' attribute for verification by default. What am I missing ? Version-Release number of selected component (if applicable): 4.9.1.3-1.fc16 4.9.1.3-7.fc17 4.10.0-5.fc18