Re: automating updates

[Jeroen van Meeuwen <kanarip kanarip com>]

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'
>   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?

Hmm... although I'm not much of a packager nor a frequent user of the 
CVS system:

common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm
cvs up
cd devel; make build; cd ..
cd F-9; make build; make update [options]^1; cd ..

^1: takes the latest completed koji build of the appropriate tag even 
without specifying the package name -doesn't it?

Looks to me is a little easier to script... don't you think?

Kind regards,

Jeroen van Meeuwen
-kanarip