Bug#898961: dscverify: accept .buildinfo from a build with unsigned .dsc which later was signed

2018-08-03 Thread Mattia Rizzolo
On Fri, Aug 03, 2018 at 01:39:19AM +0200, Thorsten Glaser wrote: > > `debsign` takes care of updating the checksums in the .buildinfo when > > you sign a .changes (or a .buildinfo). > > oh, that must be new then. "Yes", it was added around the time buildinfo appeared. > signs them with a only sl

Bug#898961: dscverify: accept .buildinfo from a build with unsigned .dsc which later was signed

2018-08-02 Thread Thorsten Glaser
Hi Mattia, > wait, but why is the checksum of the .dsc in the .buildinfo wrong? > `debsign` takes care of updating the checksums in the .buildinfo when > you sign a .changes (or a .buildinfo). And of course if you sign oh, that must be new then. I have a specific setup that copies the .dsc and

Bug#898961: dscverify: accept .buildinfo from a build with unsigned .dsc which later was signed

2018-05-18 Thread Mattia Rizzolo
Control: tag -1 moreinfo On Thu, May 17, 2018 at 10:47:07PM +0200, Thorsten Glaser wrote: > When I build a package for uploading into Debian (i.e. no --binary-arch) > a .buildinfo file gets generated which contains the checksum of the .dsc > file, which at that time is unsigned. > > When I later

Bug#898961: dscverify: accept .buildinfo from a build with unsigned .dsc which later was signed

2018-05-17 Thread Thorsten Glaser
Package: devscripts Version: 2.18.2 Severity: minor When I build a package for uploading into Debian (i.e. no --binary-arch) a .buildinfo file gets generated which contains the checksum of the .dsc file, which at that time is unsigned. When I later debsign, the .dsc file is signed alongside with