Re: minia_3.2.0-2_source.changes REJECTED
Hi Andrius,
I have no idea why but sometimes some wrong metadata sneaked into
pristine-tar branch. It might be that it happened in a short window
of time where I erroneously had set
pristine-tar = False
in my ~/.gbp.conf . Or may be you need to check your ~/.gbp.conf
whether this is set True? I think its a bug that you get a *wrong*
tarball if this is set to False - it rather should be none at all
IMHO. But I was to lazy to sort this out.
Kind regards (and thanks for fixing minia in any case)
Andreas
PS: Can you please also push mindthegap changes? May be there
was a conflict with my `mv patches debian/patches` .
On Thu, Jul 04, 2019 at 06:33:21AM +0000, Debian FTP Masters wrote:
>
>
> minia_3.2.0-2.dsc: Invalid size hash for minia_3.2.0.orig.tar.gz:
> According to the control file the size hash should be 546731,
> but minia_3.2.0.orig.tar.gz has 546757.
>
> If you did not include minia_3.2.0.orig.tar.gz in your upload, a different version
> might already be known to the archive software.
>
>
>
> ===
>
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
>
>
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
Reply to: