Neal Becker wrote:
I'm trying to automate the upstream updates of my packages (somewhat). The procedure seems to be: 1. In devel: 1.1 make new-sources 1.2 update .spec 1.3 cvs ci -m 'update to xxx'
make clog && cvs commit -F clog
1.4 make tag build 2. cp -l -f .spec sources .cvsignore ../F9 cp -l -f .spec sources .cvsignore ../F9
Those two cp lines should probably end with F-9 and F-8, right?
3. for n in 9 8; do ( cd F-$n; cvs ci -m 'update to 1.0.1' && make tag build && bodhi -n -r F$n -t enhancement mercurial-1.0.1-4.fc$n ); done
Shouldn't "make update" do some of the bodhi part?
What's not automated?
"make help" may help.
Howto get the current tag (e.g., mercurial-1.0.1-4.fc9)?
make verrel
Optional - extract cvs ci message from spec changelog
make clog -- Hans Ulrich Niedermann
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
