Bug 838657 - Invalid %verify token: owner
Summary: Invalid %verify token: owner
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 17
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-09 17:40 UTC by Jiri Popelka
Modified: 2012-07-10 09:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-10 07:29:28 UTC


Attachments (Terms of Use)

Description Jiri Popelka 2012-07-09 17:40:09 UTC
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

Comment 1 Panu Matilainen 2012-07-10 07:29:28 UTC
It's an error in max-rpm: the verify attribute is (and always has been) "user", not "owner".

Comment 2 Panu Matilainen 2012-07-10 09:57:22 UTC
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


Note You need to log in before you can comment on or make changes to this bug.