On Mon, Dec 03, 2007 at 04:39:26PM -0600, Michael E Brown wrote:
On Mon, Dec 03, 2007 at 04:49:41PM +0000, Paul Howarth wrote:
> Michael E Brown wrote:
> If you're not using the policy module, I'd expect you to have problems
> building packages that run mono and/or java code at build time as
> described at
http://fedoraproject.org/wiki/PackageMaintainers/MockTricks
Can you explain to me what you mean by "if you're not using the policy
module"? I'm sorta-slow when it comes to selinux (as evidenced by this
thread...)
> The package I came across that exhibited this problem and led me
to
> write the policy module was "lat", a mono-based package.
Using unmodified current mock (0.8.12) on Fedora 8 with selinux
enforcing, I was able to compile current F8 lat:
$ mock -r fedora-8-x86_64 --rebuild --resultdir=./try/out ./try/lat-1.2.3-1.fc8.src.rpm
INFO: mock.py version 0.8.12 starting...
State Changed: init plugins
State Changed: start
State Changed: lock buildroot
State Changed: clean
INFO: Start(./try/lat-1.2.3-1.fc8.src.rpm) Config(fedora-8-x86_64)
State Changed: init
State Changed: lock buildroot
INFO: enabled yum cache
State Changed: cleaning yum metadata
INFO: enabled root cache
State Changed: unpacking cache
State Changed: running yum
State Changed: setup
State Changed: build
INFO: Done(./try/lat-1.2.3-1.fc8.src.rpm) Config(fedora-8-x86_64) 9 minutes 42 seconds
INFO: Results and/or logs in: ./try/out
INFO: Cleaning up build root ('clean_on_success=True')
State Changed: lock buildroot
State Changed: clean
--
Michael