Learn more about these different git repos.
Other Git URLs
I noticed mostly from https://apps.fedoraproject.org/packages that there are stable released builds in koji which are still tagged also with updates-testing.
To investigate I wrote a little script which generates:
{{{ $ ./both-updates-testing f18 = f18-updates-testing and f18-updates = 0 = f18-updates-testing and f18 = 1436 $ ./both-updates-testing f19 = f19-updates-testing and f19-updates = 6 = f19-updates-testing and f19 = 1 }}}
It would be nice to untag f18-updates-testing particularly from the 1436 builds in f18.
I wonder if this was caused by some Bodhi bug when moving packages from f-updates-testing to f?
improved script using grep -F ;) fedora-both-testing-stable
Example is kernel-3.10.4-300.fc19:
https://apps.fedoraproject.org/packages/kernel
https://admin.fedoraproject.org/updates/kernel-3.10.4-300.fc19
Here is a new example from a package build that just got pushed to stable:
http://koji.fedoraproject.org/koji/buildinfo?buildID=469466
So maybe this is really Bodhi's fault for not untagging packages from f-updating-testing when they get pushed to f before final release rather than f*-updates? Known issue?
Replying to [comment:1 petersen]:
Example is kernel-3.10.4-300.fc19: https://apps.fedoraproject.org/packages/kernel https://admin.fedoraproject.org/updates/kernel-3.10.4-300.fc19 [[BR]] This due to a bodhi bug that occurs when an update reaches the stable karma threshold while getting pushed to testing.
https://admin.fedoraproject.org/updates/kernel-3.10.4-300.fc19 [[BR]] This due to a bodhi bug that occurs when an update reaches the stable karma threshold while getting pushed to testing.
I think we might be able to work around this bug in the current version on bodhi, but it won't be pretty. We can solved this properly in bodhi2 by having a requests table/queue, as opposed to having a single mutable property that causes all sorts of race-conditions.
Upstream ticket: https://fedorahosted.org/bodhi/ticket/679
I am almost positive the builds tagged with f18-updates-testing + f18 were pushed during the pre-release timeframe. During these pushes, bodhi simply adds the tag instead of moving between them. Right now there is nothing in the process that cleans those builds up once when the release changes to GA.
I am working on untagging these builds now
Metadata Update from @petersen: - Issue assigned to lmacken
Log in to comment on this ticket.