[pkg-crosswire-devel] Fixing "invalid hash size for sword"

Roberto C. Sánchez roberto at debian.org
Sat Nov 28 14:24:20 GMT 2020


On Sat, Nov 28, 2020 at 09:54:39AM +0100, Teus Benschop wrote:
> On Fri, 27 Nov 2020 at 22:04, Debian FTP Masters <
> ftpmaster at ftp-master.debian.org> wrote:
> 
> >
> >
> > sword_1.9.0+dfsg-3.dsc: Invalid size hash for sword_1.9.0+dfsg.orig.tar.xz:
> > According to the control file the size hash should be 1051424,
> > but sword_1.9.0+dfsg.orig.tar.xz has 1047076.
> >
> > If you did not include sword_1.9.0+dfsg.orig.tar.xz in your upload, a
> > different version
> > might already be known to the archive software.
> >
> >
> >
> Hello,
> 
> Once in a while the 'invalid hash size for ..." come up.
> The latest is the one from yesterday, where
> the sword_1.9.0+dfsg.orig.tar.xz was uploaded to the archive tagged for the
> experimental suite already, and yesterday I uploaded to the unstable suite,
> and then this invalid hash size message comes up.
> The special part here is that I am not aware of having made changes to the
> gbp.conf settings for sword. What was done though was an update of sid.
> Is this something weird in gbp?

I'm glad this got sorted out.  Though, to ensure smooth operations going
forward, I wonder if we should consider committing a debian/gbp.conf to
the repository.  It is entirely likely that differences between each of
our personal ~/.gbp.conf settings could result in subtle issues.

Regards,

-Roberto
-- 
Roberto C. Sánchez



More information about the pkg-crosswire-devel mailing list