Description of problem: build root contents for a package is hard to track when root caching is enabled Version-Release number of selected component (if applicable): How reproducible: Always when using a cached root Steps to Reproduce: 1. Enable root cache 2. 3. Actual results: root.log only shows packets added/upgraded Expected results: Before build starts it's desireable to have a full listing of currently installed packages, i.e. an "rpm -q -a" listing or equivalent. Additional info:
I've added a routine to do an 'rpm -q -a' in the chroot at the end of the 'init' phase. This should be the base chroot plus any updates from yum, but before any package dependencies are added.
Thanks. It's imho even better if the list is generated after build dependencies have been added, giving a consistent view of what was installed in the build root while the package is being built. Same if --noclean is being used to run the build in an already existing root fs. but if the list is already generated when --noclean is used as well then the current change is sufficient even if it means having to parse two different package list formats in determining what was available in the buildroot while the package was being built.
mock-1.1.18-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.18-1.el6
mock-1.1.18-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mock-1.1.18-1.fc15
mock-1.0.25-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mock-1.0.25-1.el5
mock-1.1.18-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/mock-1.1.18-1.fc14
mock-1.1.18-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mock-1.1.18-1.fc16
Package mock-1.0.25-1.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mock-1.0.25-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2011-5097/mock-1.0.25-1.el5 then log in and leave karma (feedback).
mock-1.1.18-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.18-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.18-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.18-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.
mock-1.0.25-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
This causes mock to fail if the chroot does not contain the rpm package (which is not uncommon). This will also fail if the host rpmdb version does not match the chroot rpmdb version.