Should "koji regen-repo" be necessary?

[Dennis Gilmore]

On Monday, May 11, 2015 06:56:39 PM John Florian 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.

kojira handles it for internally generated builds,  however it does not have 
any way to check if an external repo has changed and trigger new repos for 
external repos.  so you will need to do something that triggers kojira to 
generate a new repo or run regen-repo

Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.fedoraproject.org/pipermail/buildsys/attachments/20150511/c3bdf8db/attachment.sig>