I commonly turn off kojira when I'm doing a mass rebuild as each time a build finishes kojira will detect this and run. At least that's my experience. Generally speaking, I'd turn kojira off, then do all of the builds, then tell koji to do a regen-repo on its own, then restart kojira.
Cheers, herlo On Mon, May 11, 2015 at 12:56 PM, John Florian <[email protected]> wrote: > I’m relatively new to Koji and my setup works very well, until it > doesn’t. A recurring theme is that the buildroot sometimes cannot be > populated. Today’s example: > > > > DEBUG util.py:388: Transaction Summary > > DEBUG util.py:388: > ================================================================================ > > DEBUG util.py:388: Install 11 Packages (+174 Dependent packages) > > DEBUG util.py:388: Total download size: 104 M > > DEBUG util.py:388: Installed size: 429 M > > DEBUG util.py:388: http://our-local-mirror-host > /pub/fedora/updates/21/i386/p/perl-Encode-2.72-1.fc21.i686.rpm: [Errno 14] > HTTP Error 404 - Not Found > > DEBUG util.py:388: Trying other mirror. > > DEBUG util.py:388: Error downloading packages: > > DEBUG util.py:388: 1:perl-Encode-2.72-1.fc21.i686: failed to retrieve > perl-Encode-2.72-1.fc21.i686.rpm from build > > DEBUG util.py:388: error was [Errno 14] HTTP Error 404 - Not Found > > DEBUG util.py:499: Child return code was: 1 > > DEBUG util.py:183: kill orphans > > > > When this happens I can regen-repo and then resubmit the build and > everything will be fine. Is this normal? I was kind of under the > impression that kojira maybe took care of this kind of thing, but the > documentation vacuum leaves one to wonder quite a bit. > > > > -- > > John Florian > > > > -- > buildsys mailing list > [email protected] > https://admin.fedoraproject.org/mailman/listinfo/buildsys >
-- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
