Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13552

Re: python-django-js-asset_1.2.2-3_source.changes REJECTED

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

On Sun, Sep 19, 2021 at 10:27:21AM +0200, Carsten Schoenert wrote:
> Hello Antonio,
> 
> as you initially did the first upload for this package I'm now heading
> over to you.
> 
> Am 19.09.21 um 09:48 schrieb Debian FTP Masters:
> > 
> > python-django-js-asset_1.2.2-3.dsc: Invalid size hash for python-django-js-asset_1.2.2.orig.tar.gz:
> > According to the control file the size hash should be 6360,
> > but python-django-js-asset_1.2.2.orig.tar.gz has 6367.
> > 
> > If you did not include python-django-js-asset_1.2.2.orig.tar.gz in your upload, a different version
> > might already be known to the archive software.
> 
> I've no idea where the size of 6360 for the orig.tar.gz file is coming
> from which DAK refers.
> 
> If I look at the source package sites or on snapshot.d.o I always see a
> size of 6367.
> 
> https://packages.debian.org/source/unstable/python-django-js-asset
> http://snapshot.debian.org/package/python-django-js-asset/1.2.2-1/
> 
> And this size was recreated by gbp locally.
> But the question is now how to proceed now. A quick & dirty solution
> would be to simply use the old tar.gz file (if available).
> Another option would be more dramatically and let remove the package
> completely from the archive. Do you have opinions on that?

Looking from my side, the tarball from the archive (apt source
python-django-js-asset) and the one generated by pristine-tar are
identical:

4b6a2c8625b8e96bbc4ff1588a27238d7d418b03  /tmp/python-django-js-asset_1.2.2.orig.tar.gz
4b6a2c8625b8e96bbc4ff1588a27238d7d418b03  /tmp/archive/python-django-js-asset_1.2.2.orig.tar.gz

From reading the REJECT email, I think it implies that the .dsc/.changes
you uploaded refer to an orig tarball with 6360 bytes. Do you still have
the exact artifacts that you uploaded?

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-19 21:30 +0200
  Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Carsten Schoenert <c.schoenert@t-online.de> - 2021-09-19 23:10 +0200
    Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Andrey Rahmatullin <wrar@debian.org> - 2021-09-20 09:30 +0200
    Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-20 13:30 +0200
      Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-20 17:20 +0200
        Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Andrey Rahmatullin <wrar@debian.org> - 2021-09-20 17:30 +0200
          Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-21 03:20 +0200
        Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Thomas Goirand <zigo@debian.org> - 2021-09-20 21:50 +0200
        Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-21 23:10 +0200
          Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-22 00:40 +0200
          Re: writing debian/gbp.conf considered harmful [was:  python-django-js-asset_1.2.2-3_source.changes REJECTED] Thomas Goirand <zigo@debian.org> - 2021-09-22 09:30 +0200

csiph-web