[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#597164: mock: fails with ImportError: No module named root_cache

I cannot reproduce this bug, I just built rpms for both epel-5-x86_64
and epel-5-i386 on two different machines running squeeze (one
being a x86_64 machine, the other one is an i386).

# dpkg -l mock
ii  mock           1.0.8-1        Build rpm packages inside a chroot
# mock -r epel-5-i386 nc-1.84-10.fc6.src.rpm 
INFO: mock.py version 1.0.8 starting...
State Changed: init plugins
/bin/sh: /usr/sbin/getenforce: No such file or directory
State Changed: start
INFO: Start(nc-1.84-10.fc6.src.rpm)  Config(epel-5-i386)
State Changed: lock buildroot
State Changed: clean
State Changed: init
State Changed: lock buildroot
Mock Version: 1.0.8
INFO: Mock Version: 1.0.8
INFO: enabled root cache
State Changed: unpacking root cache
INFO: enabled yum cache
State Changed: cleaning yum metadata
INFO: enabled ccache
State Changed: running yum
State Changed: setup
State Changed: build
INFO: Done(nc-1.84-10.fc6.src.rpm) Config(epel-5-i386) 1 minutes 22
seconds INFO: Results and/or logs in: /var/lib/mock/epel-5-i386/result

I noticed that mock tries to use /usr/sbin/getenforce from
selinux-utils which is not a dependency of the mock package. I
tested building packages with and without the selinux-utils package
being installed and it worked either way. I'd guess that it assumes
that selinux is disabled when the userspace tools aren't installed, but
it would be nicer to add it to the list of dependencies to get rid of
the ugly error message.


Attachment: signature.asc
Description: PGP signature

Reply to: