Re: source.changes has wrong hash sum (Was: ftp master uploads disappearing?)
On Fri, Oct 06, 2017 at 10:04:00AM +0200, Guido Günther wrote:
> On Thu, Oct 05, 2017 at 09:26:04PM +0200, IOhannes m zmölnig (Debian/GNU) wrote:
> > On 10/05/2017 06:53 PM, Andreas Tille wrote:
> > > Bad checksums on loki_220.127.116.11-7_source.changes: Checksum mismatch for file loki_18.104.22.168-7.dsc: b4d2841416822842e6e6b85c44e3f4f3 != 7acc0c03ab3a269d117decd6dd692967
> > >
> > > What to try next?
> > following this conversation with interest, i also tried telling my gbp
> > builds to produce both source and binary packages.
> > i also get the "checksum mismatch" for the source.changes (not for the
> > amd64.changes).
> > my workaround for now is to just (re)run "debsign" on the source.changes.
> > maybe someone has a better alternative (though my workaround is good
> > enough to be able to test the binary packages and do a sources-only
> > upload with a single build).
> Doesn't happen here. The _source and _arch changes files only differ by
> the generate binaries:
I assume this is because in Andreas's case, debsign is automatically run
on one of the .changes files after the build, which will also sign the
.dsc (and thus change its contents since it now has an inline signature
around it), but the hash in the other .changes file is for the original
unsigned .dsc. Really, you should only be signing the .changes you want
to upload, and *after* you've already checked it for errors :)