#5767: F20 stable push requests

[Fedora Release Engineering]

#5767: F20 stable push requests
-----------------------------+-----------------------
  Reporter:  pschindl        |      Owner:  rel-eng@…
      Type:  task            |     Status:  reopened
 Milestone:  Fedora 20 Beta  |  Component:  koji
Resolution:                  |   Keywords:
Blocked By:                  |   Blocking:
-----------------------------+-----------------------
Changes (by adamwill):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 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...

  * [https://admin.fedoraproject.org/updates/FEDORA-2013-23257 python-
 blivet-0.23.9-1.fc20,anaconda-20.25.15-1.fc20]
  * [https://admin.fedoraproject.org/updates/FEDORA-2013-22956 fedup-
 dracut-0.8.0-2.fc20]
  * [https://admin.fedoraproject.org/updates/FEDORA-2013-23169
 langtable-0.0.23-1.fc20]
  * [https://admin.fedoraproject.org/updates/FEDORA-2013-23254 spin-
 kickstarts-0.20.24-1.fc20]
  * [https://admin.fedoraproject.org/updates/FEDORA-2013-23185
 bluez-5.12-1.fc20] '''THIS ONE HAS BEEN SUPERSEDED''' by a 5.12-2 build,
 but we need to push 5.12-1, that is what was in RC1.1
  * [https://admin.fedoraproject.org/updates/lorax-20.4-2.fc20
 lorax-20.4-2.fc20]
  * [https://admin.fedoraproject.org/updates/FEDORA-2013-22356 php-
 symfony-2.3.7-3.fc20]

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

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5767#comment:32>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project