Hide Forgot
Created attachment 474831 [details] Build log for acl Description of problem: Rebuilding of acl (acl-2.2.49-8.fc14.src.rpm) does not work. Error seems to be: # group: mockbuild != # group: root Version-Release number of selected component (if applicable): acl-2.2.49-8.fc14.src.rpm How reproducible: always Steps to Reproduce: 1. sudo bash 2. mock -r ck --clean 3. sudo mock -r ck --rebuild acl-2.2.49-8.fc14.src.rpm 4. See build.log (atttached) Actual results: Does not build. Expected results: Correct build. Additional info: 1. /etc/mock/ck.cfg is my config file Change is only different repo URLs filled up with current versions including all updates until now (23.01.2011) 2. I did not figure out why the "sudo mock ..." is necessary despite there was already a "sudo bash". Without it I will get: DEBUG util.py:281: Executing command: ['ccache', '-M', '4G'] DEBUG util.py:247: Could not set cache size limit. DEBUG util.py:320: Child returncode was: 1 This seems to be a bug in mock.
Although I have never found it anywhere documented, mock is not supposed to be run as root: bug #507309 comment #8 Please try adding self to the group mock and build it as a regular user.
I just tried to build as regular user. This gives me: DEBUG util.py:281: Executing command: ['ccache', '-M', '4G'] DEBUG util.py:247: Could not set cache size limit. DEBUG util.py:320: Child returncode was: 1
What does 'id' say in the shell you are trying to run mock?
>id uid=30956(ckarl) gid=30956(ckarl) groups=30956(ckarl),486(mock)
My guess is that there persists something in the chroot from the previous (incomplete) run of mock under the root. Please make sure the chroot directory is clean and accessible by the group mock. But do it carefully, chances are that some mount points are still active in there.
Created attachment 474910 [details] new log file now i386
Created attachment 474911 [details] root.log file for i386
Created attachment 474912 [details] state.log for i386
Now I did: 1.) rm -r /var/cache/mock 2.) rm -r /var/cache/ccache 3.) mock -r ck --clean 4.) mock -r ck --rebuild /mnt/lager/ARCHIVE/fedora-14-repository/fedora/SRPMS/acl-2.2.49-8.fc14.src.rpm But still the same error with ccache, see log files Two Remarks: 1.) I now build on i386 (former was x86_64) 2.) IMO the problem is not acl related but either mock or ccache related, so feel free to forward this report
As for the acl package, the build is known to work in mock with the usual setup and it also runs in rpmbuild as either root or non-root. If you run it as root it performs some additional tests during %check. All other issues with mock and ccache are unrelated to the acl package.
I just rebuilt the latest acl SRPM using the x86_64 config for f14 and the just built mock-1.1.9. Please try this new mock version and see if you still have build problems.
I now use "mock-1.1.9-1.fc14.noarch.rpm" with x86_64 config, but I still get: DEBUG util.py:281: Executing command: ['ccache', '-M', '4G'] DEBUG util.py:247: Could not set cache size limit. DEBUG util.py:320: Child returncode was: 1
ccache version is: >rpm -qa ccache ccache-3.1.3-1.fc14.x86_64
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
(In reply to comment #13) > ccache version is: > > >rpm -qa ccache > ccache-3.1.3-1.fc14.x86_64 Try running: $ mock -r ck --scrub=c-cache and see if that cleans up the ccache issues
Just retried with mock -r ck --scrub=c-cache --rebuild /mnt/lager/ARCHIVE/fedora-14-repository/fedora/SRPMS/acl-2.2.49-8.fc14.src.rpm but gives me the very same error.
Additionally I create a brand new user on my system and tried it again, but also gives me the same error
I'm quite puzzled about this. The failure you're seeing is from running ccache inside the chroot and telling it that the cache limit is 4GB. Do you have 4GB free on your system?
I don't know how to exactly calculate if 4 GB free, but I attached the output of cat /proc/meminfo
Created attachment 497707 [details] Output of cat /proc/meminfo
now with f15 and mock-1.1.10-1.fc15 and ccache-3.1.4-4.fc15.src.rpm it seems to work as (not root) user.