On 05/30/2012 08:14 AM, Moray Henderson wrote:
I think that it was Koji housekeeping removing the mock root as fast
as I was building it. Do mock roots with failed builds last longer
than successful ones? I never had this problem going into a mock
root to investigate a failed build, but when I try to reinitialize an
older root - even when the mock config is still available - Koji
seems to find it and remove it almost immediately.
Yes. successful buildroots are cleared almost immediately. Failed ones
remain for 4 hours by default. The mock configs remain for 24 hours, as
do the top level buildroot dirs[*]
For buildroots of successful tasks, I recommend replicating the
buildroot, by either:
1) Generate a new config with a command like:
koji mock-config --task X myroot
and use that config with mock
2) If the mock config generated by koji is still around, *copy* it
elsewhere (under /etc/mock rather than /etc/mock/koji, preferably change
the name). Also *edit* it to remove the commented metadata left by koji
at the beginning and change the "config_opts['root']" line to a
different string.
These steps will prevent kojid from removing (or even noticing) your
buildroot. As such, you will want to remember to clear it yourself when
finished.
[*] this is a workaround for a very nasty bug in older versions of rpm:
https://bugzilla.redhat.com/show_bug.cgi?id=192153
--
buildsys mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/buildsys
