Re: Script for automatically backporting
On Tue, Dec 13, 2011 at 08:39:00PM +0100, Paul van der Vlis wrote:
> Op 10-12-11 12:59, Paul van der Vlis schreef:
>
> > In my opinion the best way for backporting would be to automatically
> > make a stable-backport for every package what's uploaded to sid and to
> > add it to the backports when it enters testing. But that's another
> > discussion. Was there such a discussion in the past?
>
> I thought about this idea, maybe it's realistic to try it as a seperate
> process, like sometimes the full archive is rebuilded by somebody.
>
> Maybe all packages what does not need any build-dep's from others first,
> then as a next run the packages what only needs packages from the first
> run, and so on.
> But it's much work to make it work, I think...
>
> And signing is a problem, because officially a package needs to be
> modified for backporting, e.g. the version number.
That's not a problem. Tools like sbuild (used for building packages
on the buildds), are capable of automatically adding changelog
entries for builds, primarily for binNMUs, but the mechanism could
also be used for backporting. It has an --append-to-version=<string>
option which could be used to add the "~bponn+m" suffix.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Reply to: