Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-12 Thread Guillem Jover
On Sat, 2019-10-12 at 09:29:18 +0200, Ansgar wrote: > Guillem Jover writes: > > On Thu, 2019-10-10 at 09:44:21 +0200, Ansgar wrote: > >> Guillem Jover writes: > >> > On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > >> >> With the first binNMU the changelog used 5.2.17+1+b1 as the version > >>

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-12 Thread Holger Levsen
On Sat, Oct 12, 2019 at 09:29:18AM +0200, Ansgar wrote: > > Why should it generate a new source? > Because sourceful uploads need a new source package. [...] > > This is using the version suffix > > for binNMUs, using this convention for something that is not a binNMU > > seems just wrong. I agre

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-12 Thread Ansgar
Guillem Jover writes: > On Thu, 2019-10-10 at 09:44:21 +0200, Ansgar wrote: >> Guillem Jover writes: >> > On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: >> >> With the first binNMU the changelog used 5.2.17+1+b1 as the version >> >> and this caused disagreement between different parts of dpkg.

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-11 Thread Guillem Jover
On Thu, 2019-10-10 at 09:44:21 +0200, Ansgar wrote: > Guillem Jover writes: > > On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > >> With the first binNMU the changelog used 5.2.17+1+b1 as the version > >> and this caused disagreement between different parts of dpkg. > >> dpkg-source generates

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-10 Thread Denise Oshesky
http://www.centralpacificbank.com From: Guillem Jover Sent: Wednesday, October 9, 2019 9:26 PM To: Ansgar ; 942...@bugs.debian.org <942...@bugs.debian.org> Subject: Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1 * T

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-10 Thread Ansgar
Guillem Jover writes: > On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: >> With the first binNMU the changelog used 5.2.17+1+b1 as the version >> and this caused disagreement between different parts of dpkg. >> dpkg-source generates linux-signed-amd64_5.2.17+1+b1.dsc, but >> dpkg-genchanges str

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-10 Thread Guillem Jover
Control: reassign -1 dpkg-dev/1.18.25 On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > Package: dpkg > Version: 1.18.25 > Severity: normal > For the Secure Boot support in Debian we automatically generate source > packages that include the signatures (linux-signed-*) from files > shipped in

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

2019-10-09 Thread Ansgar
Package: dpkg Version: 1.18.25 Severity: normal For the Secure Boot support in Debian we automatically generate source packages that include the signatures (linux-signed-*) from files shipped in linux-image-amd64-signed-template below /usr/share/code-signing/linux-image-amd64-signed-template/sourc