After installing a mock chroot on rawhide, I end with the following : # LC_ALL=C rpm -qf /var/lock/rpm/ file /var/lock/rpm is not owned by any package I do not know what created it, but given the name, i suspect it to be used by rpm, so that would be owned by it.
Interesting... rpm doesn't create or use such a path for anything, unless something is overriding %_rpmlock_path from its default value. I have such a directory too in my rawhide mock chroot so maybe its something to do with mock.
Indeed, this come from _setupDirs in /usr/lib/python2.7/site-packages/mockbuild/backend.py Reassigning to mock then.
Yup. And thinking some more, upstream rpm did use such a path between 2004-2005, and its possible RHEL-4 rpm might actually need it. This is where it got introduced into mock: commit 467b6734b41f1a01f6f9e6765fdcd72d0deb1adb Author: jcwillia <jcwillia> Date: Tue Sep 26 16:29:22 2006 +0000 RPM workaround So... like said, no even remotely recent rpm version needs it, but if its needed for compatibility with ancient versions, not a whole lot harm done. A better option might be grabbing the dirname from %_rpmlock_path macro.
I am trying to make a tool to check that no directory are unowned on package review, and I would prefer to have a chroot as clean of errors as possible, rather than carry a long list of exception. So if the file is unused, I think it should be either removed, or owned. Problem with remove is that of course, you do not know what it would break until it break. I do not have any rhel4 to test, and there is no epel config for it. At least, maybe put a note to remove once rhel 4 is EOL :)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
(In reply to comment #3) > Yup. And thinking some more, upstream rpm did use such a path between > 2004-2005, and its possible RHEL-4 rpm might actually need it. This is where > it got introduced into mock: > > commit 467b6734b41f1a01f6f9e6765fdcd72d0deb1adb > Author: jcwillia <jcwillia> > Date: Tue Sep 26 16:29:22 2006 +0000 > > RPM workaround > > > So... like said, no even remotely recent rpm version needs it, but if its > needed for compatibility with ancient versions, not a whole lot harm done. A > better option might be grabbing the dirname from %_rpmlock_path macro. Since we don't actually support RHEL4 anymore (mock that is), I'll look at pulling that out.
Ok, removing that from _setupDirs() didn't break my tests, so it's queued up for the next release (a week or so).
mock-1.1.33-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.33-1.fc19
mock-1.1.33-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.33-1.fc18
mock-1.1.33-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.33-1.el6
Package mock-1.1.33-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mock-1.1.33-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11294/mock-1.1.33-1.el6 then log in and leave karma (feedback).
mock-1.1.33-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.34-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.34-1.fc18
mock-1.1.34-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.34-1.el6
mock-1.1.34-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.1.34-1.fc20
mock-1.1.34-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.34-1.fc19
Package mock-1.1.34-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mock-1.1.34-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20329/mock-1.1.34-1.fc20 then log in and leave karma (feedback).
mock-1.1.35-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.35-1.fc19
mock-1.1.35-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.35-1.fc18
mock-1.1.35-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.35-1.el6
mock-1.1.35-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.1.35-1.fc20
mock-1.1.35-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.36-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.36-1.fc19
mock-1.1.36-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.1.36-1.fc20
mock-1.1.36-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.36-1.el6
mock-1.1.36-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.37-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.37-1.fc19
mock-1.1.37-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.1.37-1.fc20
mock-1.1.37-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.37-1.el6
mock-1.1.37-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.1.37-2.fc20
mock-1.1.37-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.37-2.fc19
mock-1.1.37-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.37-2.el6
mock-1.1.38-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.38-1.fc19
mock-1.1.38-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.38-1.el6
mock-1.1.38-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.1.38-1.fc20
mock-1.1.38-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.38-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.38-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.