Am Sonntag, den 15.06.2008, 23:04 +0200 schrieb Jeroen van Meeuwen:
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'
As Ulrich already suggested yesterday:
1.3.1 make clog
1.3.2 cvs commit -F clog
> 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
Jeroen, please don't do that. We had this discussion back in Feb 2007
on the maintainers list, please search for the thread named "Discourage
cvs-import (was: Re: Plan for tomorrows (20070222) FESCO meeting)".
As a result of this discussion we set up a wiki page:
https://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo
Regards,
Christoph