automating updates
Neal Becker
ndbecker2 at gmail.com
Sun Jun 15 15:43:40 UTC 2008
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'
1.4 make tag build
2. cp -l -f .spec sources .cvsignore ../F9
cp -l -f .spec sources .cvsignore ../F9
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
What's not automated?
Howto get the current tag (e.g., mercurial-1.0.1-4.fc9)?
Optional - extract cvs ci message from spec changelog
Howto get bodhi to stop asking for a password?
More information about the devel
mailing list