Learn more about these different git repos.
Other Git URLs
cld-0.2.1-1.fc12 is tagged in CVS and built in koji, but does not appear after several wait-repo executions:
[jgarzik@bd repo]$ koji wait-repo --target dist-f12 --build cld-0.2.1-1.fc12 Unsuccessfully waited 120:11 for cld-0.2.1-1.fc12 to appear in the dist-f12-build repo [jgarzik@bd repo]$ koji wait-repo --target dist-f12 --build cld-0.2.1-1.fc12 Unsuccessfully waited 120:08 for cld-0.2.1-1.fc12 to appear in the dist-f12-build repo
I attempted a "make update", filled out a bodhi template, but received "cld-0.2.1-1.fc12 not tagged as an update candidate" error.
Version 0.2.1 of cld includes nothing but bug fixes for major bugs (crashes, failure to communicate across network), and needs to get pushed out ASAP.
And in general, cld, chunkd and tabled packages are under heavy development, with major bug fixes appearing on a regular basis. This is the norm...
Finished: Wed, 26 Aug 2009 16:36:58 EDT
I'm finding your wait repo commands hard to comprehend - if the build has only been done for less than an hour...
Ah, so the 'finished' time printed by koji buildinfo is buggy (it assumes local timezone.)
Still, it's been in the repo since at least Wed, 26 Aug 2009 21:24:58 UTC.
wait-repo prints -elapsed- time, not finished time.
cld update is there now, but it took over four hours, apparently. Trac isn't so good at showing pre-formatted ASCII text, so I will break up the commands that show elapsed time:
[jgarzik@bd repo]$ koji wait-repo --target dist-f12 --build cld-0.2.1-1.fc12
Unsuccessfully waited 120:11 for cld-0.2.1-1.fc12 to appear in the dist-f12-build repo
Unsuccessfully waited 120:08 for cld-0.2.1-1.fc12 to appear in the dist-f12-build repo
Successfully waited 28:18 for cld-0.2.1-1.fc12 to appear in the dist-f12-build repo
The final "koji wait-repo" completed successfully about the same time as I received the email indicating attention on this Trac ticket.
So either you fixed it -- thanks!! -- or it took 4 1/2 hours to land in rawhide. koji wait-repo will intentionally exit after 2 hours, if the package has not appeared by that time.
In any case, life is good now :)
Here is what happend. Your cld build completed at 16:36 UTC. There was already a newRepo task running for dist-f12 that started at 16:09, too early for your build.
That running newRepo task finished at 17:18.
Due to a koji limit of I believe only 3 newRepo tasks at a time due to the DB load, a second newRepo task for dist-f12 didn't start until 19:29 and finished at 21:24.
This is about the longest you should ever expect to wait, and part of the problem is that we're managing far too many buildroots right now that are causing an explosion of newRepo tasks. I'll be investigating and hopefully pruning some unneeded roots.
Probably stating the obvious, but...
FWIW, this issue killed my chain-build; this koji chain-build failed at the wait-repo stage: http://koji.fedoraproject.org/koji/taskinfo?taskID=1636706
I am manually wait-repo'ing locally, and then will build tabled, so no [additional] need for action.
Login to comment on this ticket.