#5767 F20 stable push requests
Closed: Fixed None Opened 6 years ago by pschindl.


Please reopen for the next set. Thanks.

If you haven't started with pushing yet, please add this one too:

Thank you!

Looks like these are now ready to go:

and of course:

Done. They should go out in tomorrow's compose, then we will do a normal stable push tomorrow that will land monday morning.

kernel now has sufficient karma to go.

Done. Will appear in tomorrow's branched compose.

pushed stable. additionally i added [https://admin.fedoraproject.org/updates/FEDORA-2013-20033/pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20 pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20] for multiple blockers, and mostkly to make sure that the pykickstart missed in RC2 is pulled in

Re-opening for:

It would also be good if you could kill the older anaconda and python-blivet updates so they do not squelch the newer ones: https://admin.fedoraproject.org/updates/python-blivet-0.23.3-1.fc20 and https://admin.fedoraproject.org/updates/anaconda-20.25.5-1.fc20,python-blivet-0.23.3-1.fc20 .

Re-opening for more! Of the updates that went into RC5 (which we're shipping), these two have sufficient karma to go:

These do not, but they were in RC5, so we should probably force push them stable anyhow:

I think that's everything.

Re-opening for a bunch of blocker/FE fixes with sufficient karma:


pushed stable, thanks.

Pushed stable thanks

Re-opening for the last set of updates. Whatever we have to hack in terms of karma to push these, let's just do it: they're what we're shipping, so even if they eat babies, they have to go to the release repo. If it's not too much trouble, do just eyeball check no-one edited the versions in any of the updates vs. what we put in the RC1.1 build...

I think after those, the repos are consistent with RC1.1 as shipped.

Metadata Update from @pschindl:
- Issue set to the milestone: Fedora 20 Beta

2 years ago

Login to comment on this ticket.