|Summary:||RFE: Create/Store/Use list of builds to be pushed|
|Product:||[Fedora] Fedora||Reporter:||David Aquilina <dwa>|
|Component:||bodhi||Assignee:||Patrick Uiterwijk <puiterwijk>|
|Status:||CLOSED UPSTREAM||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||a.badger, flanagan, pfrields, tla|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2016-10-18 15:26:59 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description David Aquilina 2014-01-20 17:47:33 UTC
Description of problem: Currently, the process to push Fedora updates works like this: 1) Run "bodhi -P --push-release F20", then say no at the 'Push these updates?' confirmation. This creates Stable-F20 and Testing-F20 files with a list of NVRs. 2) Use the Stable-F20 and Testing-F20 files as input to sigul to sign the packages, with "sigulsign_unsigned.py -v --write-all fedora-20 $(cat Stable-F20 Testing-F20)" 3) Re-run the bodhi command from step 1, **and hope that nobody has created new updates while you were signing**. If new updates have been created you have to once again say 'no', sign the new list of NVRs, then try again. It would make life easier if bodhi could use the list of NVRs it created in Step 1 as the basis for the push after they've been signed. We often have to repeat these steps many times before we get all the updates in step 3 signed without new updates being created.
Comment 2 Randy Barlow 2016-10-18 15:26:59 UTC
I believe that the incredible puiterwijk has solved this problem for us! It should appear in the upcoming 2.3.0 release.