I see some code in mock that picks up the mockuser uid/gid from the host machine. why is it so?
I ask because recently, we came across some issues while building in koji where the builds failed with this : DEBUG util.py:280: Executing command: ['/usr/sbin/groupadd', '-g', '499', 'mockbuild'] DEBUG util.py:256: groupadd: GID 499 is not unique DEBUG util.py:319: Child returncode was: 4 (http://arm.koji.fedoraproject.org/koji/getfile?taskID=45343&name=root.lo...)
GID 499 is already taken (in this case, by avahi). What is a good way to workaround this problem?
Regards, Jitesh
(PS: I am not sure whether this is the right place to ask mock-related questions. Let me know if I need to redirect it to the mock community)
On Thu, 2009-07-09 at 14:24 +0530, Jitesh Shah wrote:
I see some code in mock that picks up the mockuser uid/gid from the host machine. why is it so?
I ask because recently, we came across some issues while building in koji where the builds failed with this : DEBUG util.py:280: Executing command: ['/usr/sbin/groupadd', '-g', '499', 'mockbuild'] DEBUG util.py:256: groupadd: GID 499 is not unique DEBUG util.py:319: Child returncode was: 4 (http://arm.koji.fedoraproject.org/koji/getfile?taskID=45343&name=root.lo...)
GID 499 is already taken (in this case, by avahi). What is a good way to workaround this problem?
Regards, Jitesh
(PS: I am not sure whether this is the right place to ask mock-related questions. Let me know if I need to redirect it to the mock community)
I do believe it picks the mock uid/gid from the host system so that the correct write permissions exist inside the chroot, particularly for doing things as non-root such as the rpm build. Perhaps we need to do the group addition step before we install the BuildRequirements. I assume that avahi picks a somewhat random UID when it installs itself?
buildsys@lists.fedoraproject.org