I have fifteen CPAN packages that I'm packaging as
RPMs for FC5, and one (and only one) of them seems to
hang mock. Is this an appropriate place to ask for
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
I'm not sure if it was the move to CentOS 4.4 or what, but now my
mock builds are failing on CentOS 4.4 hosts where they were working
fine a couple weeks ago...
Digging through root.log shows this message buried in the middle of
all the 'yum install' output:
error: can't create transaction lock on /var/lib/mock/fedora-4-i386-
So far, I've had similar results building for FC3/FC4/EL4, so I'm
guessing its a host machine issue rather than a chroot issue. Has
anyone else come across this already? I am using an older version of
mock - 0.4-2 on one machine, and 0.4-5 on another; has something
changed since then to fix this issue? I guess I need to upgrade
eventually to get the newer mock config setup, etc. but I've been
putting that off...
-----BEGIN PGP SIGNED MESSAGE-----
Ok, last unsolicited mock email of the day. Really! I promise...
We're currently shipping mock from the mock-0.6 branch of the mock CVS
repository. The HEAD (0.7) is the branch that contains the
re-architected launcher and the elevate/drop privilege logic. I'm
wondering when/how we push the new version of mock out to the world?
My preference would be to wait for FC6 to go gold, then switch over to
HEAD and deal with mock breakage at that point. Of course, the
complete lack of complaints from all you dedicated fedora buildsys
readers probably means that mock-0.7 is perfect in every way, so we
probably don't have to worry about that, eh? :)
Anyway, I'd be interested to hear what everyone thinks and I'd like to
learn what the mechanism is for implementing it. Is implementation
merely telling Jeremy or Jesse what branch to pull from? Or do we have
to do more?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----