[buildd-tools-devel] Bug#844583: sbuild: allow arbitrary version suffix for binary rebuild (binNMU)

[Johannes Schauer]

Hi Raphaël,

On Thu, 17 Nov 2016 09:03:43 +0100 =?utf-8?q?Rapha=C3=ABl_Hertzog?= <hertzog at debian.org> wrote:
> It would be nice if sbuild could let me set an arbitrary suffix when I
> request a binNMU. While binNMU was once defined by the "+bX" suffix, nowadays
> it's defined by the "binary-only=yes" changelog attribute.
> 
> This means that we can use any version suffix for the binNMU (except "one
> starting with "~") and I expect that we will want to be able to use this
> possibility in the context of PPA (or bikesheds) where we will have
> bin-nmu versions like <version>+ppafoo1 in one repo and <version>+ppabar1
> in another repository.
> 
> dpkg already does the right thing by setting the source version from the
> former changelog entry so it would be nice if sbuild could support that
> feature.
> 
> Maybe it can be smart and if the parameter to --binNMU-version contains
> (or starts with?) non-digits, then it should assume that it's the full
> bin-NMU suffix that is passed.

what do you want to do that the --append-to-version option cannot yet do?

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20161222/a9b1e26d/attachment.sig>