Your message dated Wed, 16 Feb 2022 19:47:29 +0100
with message-id <yg1gwc8dyatns...@x260.cruise.homelinux.net>
and subject line Re: Bug#1005132: drf-yasg-nonfree: File conflicts between two
different 1.20.1-1 versions
has caused the Debian Bug report #1005132,
regarding drf-yasg-nonfree: File conflicts between two different 1.20.1-1
versions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1005132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drf-yasg-nonfree
Version: 1.20.1-1
Severity: serious
User: de...@kali.org
Usertags: origin-kali
drf-yasg-nonfree 1.20.1-1 was uploaded as source only on January 23th,
the lack of binaries ended up in the package being removed by dak's
auto-cruft. Then the maintainer rebuilt a new source package while keeping
the 1.20.1-1 version and uploaded it again.
deb.debian.org is a CDN and keeps in cache the package files for a very
long time because they are supposed to be immutable so if you try to
download drf-yasg-nonfree from deb.debian.org you get the first version
of the package while the metadata refers to the second version and as
such you get a checksum error (as I did in Kali, while trying to mirror
bookworm):
Wrong checksum during receive of
'http://deb.debian.org/debian/pool/non-free/d/drf-yasg-nonfree/drf-yasg-nonfree_1.20.1-1.dsc':
md5 expected: 5c87ae878afc6adf6708439e2a0b4e97, got:
63c6925011f77e02306f451036181a13
sha256 expected:
2b3265636ef93b490b633cee9897c8462fb1cb42d1fb65226fb5a8601631ecd9, got:
834fa39b7b970704f936fc2a293ca47f9efc1939a62f5a33fcd0cea4e4a0767c
size expected: 2467, got: 2434
This bug is just a request to upload 1.20.1-2 to get rid of this
inconsistency that will last in deb.debian.org for as long as we don't
upload a new version.
The package has been temporarily removed from testing by Julien Cristau
to make sure that mirroring bookworm out of deb.debian.org will work
again shortly.
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'oldoldstable'), (500,
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-3-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.20.1-2
Hello Raphaël,
Am Mon, Feb 07, 2022 at 06:23:20PM +0100 schrieb Raphaël Hertzog:
> drf-yasg-nonfree 1.20.1-1 was uploaded as source only on January 23th,
> the lack of binaries ended up in the package being removed by dak's
> auto-cruft. Then the maintainer rebuilt a new source package while keeping
> the 1.20.1-1 version and uploaded it again.
>
> deb.debian.org is a CDN and keeps in cache the package files for a very
> long time because they are supposed to be immutable so if you try to
> download drf-yasg-nonfree from deb.debian.org you get the first version
> of the package while the metadata refers to the second version and as
> such you get a checksum error (as I did in Kali, while trying to mirror
> bookworm):
...
I've uploaded a new version -2 to get a higher version into the archive,
as also suggested from you by the direct email exchange.
This did make DAK happy again so I'll close this issue by this email.
Of course there was no intention behind the second upload to confuse
DAK, sorry for the mess and thank you for getting in contact with me!
Regards
Carsten
--- End Message ---
