Red Hat Bugzilla – Bug 820162
Transcient error in Koji/F15
Last modified: 2014-06-30 18:11:53 EDT
Description of problem:
While packaging a new version of xca, the initial "fedpkg build" for F15 failed with error "BuildrootError: could not init mock buildroot, mock exited with status 4; see root.log for more information". See http://koji.fedoraproject.org/koji/taskinfo?taskID=4059840
I thus examined all the log files and could not find a real error. Resubmitting exactly the same build 50min later succeeded: http://koji.fedoraproject.org/koji/taskinfo?taskID=4059927
- This problem occurred in Koji, not in a locally installed system.
- Initially reported to the fedora-devel list: http://lists.fedoraproject.org/pipermail/devel/2012-May/166749.html
Version-Release number of selected component (if applicable):
God knows :-/
Thanks for reassigning it if it is not mock's fault.
Dennis and I talked about it and we're not sure where it should be fixed yet. The issue seems to be a GID collision inside the chroot between the package and mock.
We're looking at it.
Well, now I don't remember what we decided, if anything. Dennis, do you recall?
Ok this was the gid collision where the gid claimed by mock on the host collided with a system gid from a package installed in the chroot. I've request that the 'setup' package allocate a static gid for mock.
Here's the request BZ:
Once this is done the mock gid should be consistent between the host and the chroot environment.
Thanks for your action. I must say it never occurred for me again since then.
Yeah, it's going to be somewhat rare, but as you've seen, it will happen.
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:
Mock gid has been static since 1.1.31