One more to end the week!
https://fedoraproject.org/wiki/Pushing_fedora_updates
Jesse Keating said the following on 09/03/2010 02:24 PM Pacific Time:
Fedora updates for released er releases are typically pushed once a
work
day. This SOP covers the steps involved.
install bodhi-client on workstation
refresh login cache
$ bodhi -m
Get a list of packages to push
$ bodhi -P --push-release F12 --push-release F13
DO NOT PRESS YES YET
Copy build names to signing host, one package name per line
Sign builds using scripts/sigulsign_unsigned.py from releng git repo
$ ./sigulsign_unsigned.py -vv --write-all fedora-13 $(cat tosign)
Strongly suggest doing the above in screen. Requires a host configured
for being a sigul client, beyond this SOP scope.
Press yes on bodhi push command. If prompted for a password ^c and
start over.
To verify:
Tail the bodhi server log to watch progress on releng2:
$ sudo tail -f /var/log/bodhi/server.log
Wait for the bodhi masher report (sent tobodhi-adminmember(a)fp.o) for
success/failure
To Consider:
Pushes often fall over due to tagging issues or unsigned packages. Be
prepared to work through the failures and restart pushes from time to time
$ bodhi -P --resume-push
* FIXME start listing common failure cases and how to work around them