Learn more about these different git repos.
Other Git URLs
This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F23 release freezes. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process . Similar to TC/RC request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed.
First request: [https://bodhi.fedoraproject.org/updates/FEDORA-2016-64146d940c systemd-229-6.fc24] for [https://bugzilla.redhat.com/show_bug.cgi?id=1313085 #1313085] . I've been trying to build a live image with livemedia-creator to test the fix, but haven't had any luck getting it to run at all, so I figure we can push the update stable and see how the next round of nightlies looks.
systemd-229-6.fc24 has been pushed stable
Re-opening, we have a couple more that can go:
builds pushed stable
A few more can go stable:
Edit: some more:
Pushed the following to f24 stable:
In fact it seems you only pushed yumex-dnf and mesa. All the other listed updates still need to be pushed:
Got the other 5 builds pushed to stable.
There's a few more that need to go stable as they were part of the Alpha compose:
I think that would get F24 stable in line with Alpha-1.7.
All of the NVRs in comment 8 have been pushed to stable.
Re-opening for the first post-Beta freeze stable push, please push:
== Blocker ==
== FE ==
I also propose we push [https://admin.fedoraproject.org/updates/FEDORA-2016-c38dadce8c pykickstart-2.25-2.fc24] for [https://bugzilla.redhat.com/show_bug.cgi?id=1327460 #1327460], even though it has 1 karma, because we currently don't really have a good way to test the fix without a compose, and it's a pretty minimal change. I did test that it didn't break a live install.
Re-opening for a couple more:
Also requesting some pushes to F22 and F23 for 'AcceptedPreviousRelease' blockers:
Done. (The f24 ones are tagged for the branched compose tonight and the f22/f23 ones are in the push I just started).
Re-opening for another:
libhif has +2, but I think we should let that one bake a bit longer before pushing stable...let's do kdepim4 now, though, as it's a 0-day and it needs the mirror metadata to be updated.
Re-opening for more Beta blockers and FEs:
Thanks! Note: we don't need to push Pungi stable for F24; it doesn't go into any of the composes and we actually use the F23 Pungi to build F24, dgilmore tells me.
the following have been pushed stable:
kernel-4.5.2-302.fc24 libhif-0.2.2-3.fc24 docker-1.10.3-5.gitef2fa35.fc24 f24-backgrounds-24.1.1-1.fc24 java-1.8.0-openjdk-18.104.22.168-2.b14.fc24 firefox-46.0-4.fc24
Re-opening for one more:
I don't know whether we should also push [https://bodhi.fedoraproject.org/updates/FEDORA-2016-66d3344495 pungi-4.0.15-1.fc24]; according to dgilmore the compose is run with F23, but that would be the equivalent pungi build. I guess ask Dennis whether we should push that or not.
That should bring us in line with Beta-1.6, I believe.
were tagged in stable yesterday
Re-opening for some Final pushes:
Re-opening, please push:
Re-opening, some more to go:
Let's push more stuff! Woo! Pushing! Yeah!
The following are pushed:
These still need some more karma:
karma is kinda negotiable for blocker/FE fixes, we usually just push them when they look good. you should have powahz to override the minimums.
anyway, some more, please push:
thanks! I think that would bring us even with RC-1.2.
So these went to stable:
The requested keepassx builds are obsoleted, so bodhi2 does not want to push those to stable. I'll keep the ticket open to see if there is a way to force the request. Thanks --Jon
We completed the stable request in #comment:30 by finishing keepassx requests.
Metadata Update from @adamwill:
- Issue set to the milestone: Fedora 24 Final
to comment on this ticket.