Red Hat Bugzilla – Bug 287321
caching-nameserver listing files not created by package
Last modified: 2013-04-30 19:37:11 EDT
Description of problem: rpm -ql output of package lists a number of files, not in fact created by the package. Version-Release number of selected component (if applicable): 9.4.2-0.3.b1.fc7 How reproducible: Everytime Steps to Reproduce: 1. Install caching-nameserver 2. run rpm -ql caching-nameserver 3. Scratch your head as you try and find the files rpm claims package creates. Also wonder why the hell rpm -V caching-nameserver returns no errors about missing files Actual results: Expected results: Additional info:
Example below: [root@firefly named]# rpm -ql caching-nameserver /etc/named.caching-nameserver.conf /etc/named.conf /etc/named.rfc1912.zones /usr/share/doc/caching-nameserver-9.4.2 /usr/share/doc/caching-nameserver-9.4.2/Copyright /usr/share/doc/caching-nameserver-9.4.2/rfc1912.txt /var/named/chroot/etc/named.caching-nameserver.conf /var/named/chroot/etc/named.conf /var/named/chroot/etc/named.rfc1912.zones /var/named/chroot/var/named/named.ca /var/named/chroot/var/named/named.empty /var/named/chroot/var/named/named.localhost /var/named/chroot/var/named/named.loopback /var/named/named.ca /var/named/named.empty /var/named/named.localhost /var/named/named.loopback [root@firefly named]# ls /etc/name* /etc/named.caching-nameserver.conf /etc/named.rfc1912.zones [root@firefly named]# ls /var/named/chroot/var/named/ [root@firefly named]# [root@firefly named]# ls /var/named/chroot/etc/ [root@firefly named]# RPM should -not- list files that the packge does not create or if they are files that -might- be used by the package then dummy files (simple commented out examples) should be created. Confusion is caused by having files listed that do not in fact exist. Confusion is further compounded when the rpm verifcation process states that there is no issue (ie displays nothing about missing files). [root@firefly named]# rpm -V caching-nameserver [root@firefly named]#
That files are marked as %ghost in specfile so they will not exist. But it makes sence to have chroot stuff in bind-chroot package.
Commited + tagged into CVS but I'm not going to release this now. We should wait for more serious issue Adam