Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJonathan Billings
2010-04-22 15:05:17 UTC
Description of problem:
The 'dhclient' package claims to own:
/usr/lib64/pm-utils
/usr/lib64/pm-utils/sleep.d
However those are in the filesystem package as well, with different modes:
$ rpm -q --qf "[%{NAME} %{FILEMODES:octal} %{FILENAMES}\n]" \
filesystem dhclient | egrep '/usr/lib64/pm-utils$'
filesystem 40555 /usr/lib64/pm-utils
dhclient 40755 /usr/lib64/pm-utils
$ rpm -q --qf "[%{NAME} %{FILEMODES:octal} %{FILENAMES}\n]" \
filesystem dhclient | egrep '/usr/lib64/pm-utils/sleep.d$'
filesystem 40555 /usr/lib64/pm-utils/sleep.d
dhclient 40755 /usr/lib64/pm-utils/sleep.d
Version-Release number of selected component (if applicable):
dhclient-4.1.0p1-15.el6.x86_64
filesystem-2.4.30-2.1.el6.x86_64
How reproducible:
Occurs when you install the packages
Steps to Reproduce:
1. Install filesystem and dhclient packages
2. run 'rpm -V filesystem'
3.
Actual results:
$ rpm -V filesystem
.M....... /dev
.M....... /usr/lib64/pm-utils
.M....... /usr/lib64/pm-utils/sleep.d
Expected results:
$ rpm -V filesystem
.M....... /dev
(the /dev results is an unrelated bug with filesystem)
Additional info:
This bug negatively affects configuration management systems that rely on the package database's verification to ensure the validity of installed packages. For example, bcfg2's Package managment marks the filesystem package as invalid.
Description of problem: The 'dhclient' package claims to own: /usr/lib64/pm-utils /usr/lib64/pm-utils/sleep.d However those are in the filesystem package as well, with different modes: $ rpm -q --qf "[%{NAME} %{FILEMODES:octal} %{FILENAMES}\n]" \ filesystem dhclient | egrep '/usr/lib64/pm-utils$' filesystem 40555 /usr/lib64/pm-utils dhclient 40755 /usr/lib64/pm-utils $ rpm -q --qf "[%{NAME} %{FILEMODES:octal} %{FILENAMES}\n]" \ filesystem dhclient | egrep '/usr/lib64/pm-utils/sleep.d$' filesystem 40555 /usr/lib64/pm-utils/sleep.d dhclient 40755 /usr/lib64/pm-utils/sleep.d Version-Release number of selected component (if applicable): dhclient-4.1.0p1-15.el6.x86_64 filesystem-2.4.30-2.1.el6.x86_64 How reproducible: Occurs when you install the packages Steps to Reproduce: 1. Install filesystem and dhclient packages 2. run 'rpm -V filesystem' 3. Actual results: $ rpm -V filesystem .M....... /dev .M....... /usr/lib64/pm-utils .M....... /usr/lib64/pm-utils/sleep.d Expected results: $ rpm -V filesystem .M....... /dev (the /dev results is an unrelated bug with filesystem) Additional info: This bug negatively affects configuration management systems that rely on the package database's verification to ensure the validity of installed packages. For example, bcfg2's Package managment marks the filesystem package as invalid.