Description of problem:

There still seems to be permissions issues with the SRPM build process (similar to RHBZ#1178576). If you prebuild a source tarball, owned 0600 as yourself, and try to run a build using an external source dir, the source tarball is copied into /tmp using 0600 perms except owned root:root. Later on, mock attempts to copy the /tmp src tarball (now owned by root) into your chroot, except this is run as yourself, resulting in an EACCES. If you then chmod the original src tarball as 0644 (rather than 0600), the tarball copied into /tmp then has 0644 root:root permissions, allowing you to read it, and the build succeeds.

Explicitly:

Say you have a src tarball /path/to/your/SOURCES/somepkg-1.0.0.tar.gz owned by your mock build user (say, johndoe:johndoe) with 0600 permissions.

Now run mock using that ext_src_dir:

mock --scm-enable --scm-option method=git --scm-option git_get="git clone git@gitserver:somepkg.git" --scm-option branch=master --scm-option spec=somepkg.spec --scm-option package=somepkg --scm-option ext_src_dir=/path/to/your/SOURCES -v

The build will fail with an EACCES on a shutil.copytree copying the tarball from /tmp into your chroot /builddir/build/SOURCES

(I'm building on a disconnected network, so sorry I don't have a full traceback, but here's a truncated version:

...snip...
/usr/sbin/mock, line 511, in do_buildsrpm
/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py, line 84, in trace
/usr/sbin/mock, line 440, in rebuild_generic
/usr/sbin/mock, line 509, in cmd
/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py, line 84, in trace
/usr/lib/python2.6/site-packages/mockbuild/backend.py, line 325, in buildsrpm
/usr/lib64/python2.6/shutil.py, line 173, in copytree
)


Version-Release number of selected component (if applicable):

mock-1.2.13