Description of problem: Intermittent build failures with symptoms: INFO: mock.py version 1.0.31 starting... Start: init plugins INFO: selinux enabled WARNING: selinux: 'yum' does not support '--setopt' option Finish: init plugins Start: run ERROR: Namespace unshare failed. Version-Release number of selected component (if applicable): mock-1.0.31-1.el5 How reproducible: Using mock to build package Steps to Reproduce: 1.Can happen on any build Actual results: Build fails Expected results: Build succeeds Additional info: I never saw this with mock-1.0.28-1.el5
reverted addition of CLONE_NEWUTS flag to unshare(2) call (not supported by 2.6.18 kernel). should be a 1.0.33 up shortly.
mock-1.0.33-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mock-1.0.33-1.el5
Package mock-1.0.33-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.33-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6586/mock-1.0.33-1.el5 then log in and leave karma (feedback).
mock-1.1.26-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.26-1.fc17
mock-1.1.26-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.26-1.el6
mock-1.1.26-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mock-1.1.26-1.fc16
mock-1.0.34-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mock-1.0.34-1.el5
mock-1.1.26-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.26-2.fc17
mock-1.1.26-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.26-2.el6
mock-1.1.26-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mock-1.1.26-2.fc16
mock-1.1.26-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.27-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.27-2.el6
mock-1.1.27-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mock-1.1.27-2.fc16
mock-1.0.35-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mock-1.0.35-1.el5
mock-1.1.27-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.27-2.fc17
mock-1.1.28-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.28-1.el6
mock-1.1.28-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.28-1.fc18
mock-1.0.36-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mock-1.0.36-1.el5
mock-1.1.28-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.28-1.fc17
mock-1.1.28-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mock-1.1.28-1.fc16
mock-1.1.28-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.28-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.0.36-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 seems to have gotten unfixed in 1.0.36. I am getting the same symptom as the OP installing from EPEL 5.
Tried to build a package using mock-1.0.36 and got: Traceback (most recent call last): File "/usr/sbin/mock", line 66, in ? import mockbuild.backend File "/usr/lib/python2.4/site-packages/mockbuild/backend.py", line 237 finally: ^ SyntaxError: invalid syntax
Yes, when I was merging some fixes from the mock-1.1 branch I let the unshare bug creep in as well as some python2.6+ syntax. mock-1.0.37 will be on testing shortly and should fix this problem.