Red Hat Bugzilla – Bug 209581
obstacles to using mock as a non-500:500 user
Last modified: 2013-01-09 23:06:16 EST
My userid is 404, I belong to group mock (408), but I run into numerous problems
attempting to use mock to build packages:
- mock init fails to write to builddir/.rpmmacros, because builddir is created
with mode 700 user 500, and I don't have permission to access or write to that
- mock init fails to write to etc/yum.conf, even if I add myself to group
mockbuild, if (umask&0020)!=0
- mock rebuild fails to copy the src.rpm file to builddir/build/originals,
because it doesn't have permission to write to that directory. Adding self to
the mockbuild group and adjusting umask doesn't help.
There might be more, but at this point I gave up trying to use mock as non-root.
Version-Release number of selected component (if applicable):
Only to find out a moment later that mock doesn't want to run as root either :-(
Did you add yourself to the mock group, as per the directions? You add yourself
to mock group, then you can call mock and mockhelper to build packages and do
things in the chroots...
Yes, I thought that would be implied, otherwise I wouldn't have got anywhere as
far as I did.
In the end, I had to create a user with uid 500 gid 500, add *that* user to
group mock and use it in order to get mock to work.
Strange. I'll let Clark take a look at this...
yes, very strange.
Alex, what release/kernel(s) are you using? Have you seen this change behavior
between kernel releases?
I believe the current version of mock (0.8.15+) addresses these issues, although
I'm not positive that they're all fixed. Would you please see if it still fails