On 2017-09-24 10:41, Christoph Biedl wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: binnmu
> 
> Hello,
> 
> a few days ago, a binNMU for the src:libselinux Debian package hit
> stretch-proposed-updates, providing among others a file named
> libselinux1_2.6-3+b2_amd64.deb - unfortunately such a file name has been
> in use at the very same place for another upload that took place in
> June[2]. As a result, there is a duplicate.
> 
> TTBOMK, such duplicates are not forbidden but fairly confusing. Also,
> the apt-cacher-ng proxy appearently does not take such re-usal into
> account and serves the old copy if still in the cache, subsequently
> triggering a "Hash Sum mismatch" error from apt:
> 
> E: Failed to fetch 
> http://ftp.de.debian.org/debian/pool/main/libs/libselinux/libselinux1_2.6-3+b2_amd64.deb
>   Hash Sum mismatch
>    Hashes of expected file:
>     - SHA256:afe008cdd2ca9d9de483ecada93459b33cf40f0d7c61f4652c4839651515725e
>     - MD5Sum:b8ddc8ad9229d17a6fb900538e5c45cb [weak]
>     - Filesize:101394 [weak]
>    Hashes of received file:
>     - SHA256:06434e32a91558ecae41dab74d3ffd0cce90f9868cff82bb4ddfe15f9a66e740
>     - MD5Sum:9e47c78ec70f36d03fd85f8775326d21 [weak]
>     - Filesize:101302 [weak]
>    Last modification reported: Fri, 30 Jun 2017 00:12:30 +0000
> 
> diffoscope shows for debian/changelog:
> 
> │ │ │ │ -libselinux (2.6-3+b2) sid; urgency=low, binary-only=yes
> │ │ │ │ +libselinux (2.6-3+b2) stretch; urgency=low, binary-only=yes
> │ │ │ │  
> │ │ │ │    * Binary-only non-maintainer upload for amd64; no source changes.
> │ │ │ │ -  * Rebuild with python3.6 as a supported python3.
> │ │ │ │ +  * Rebuild with current sbuild to fix changelog date
> │ │ │ │  
> │ │ │ │ - -- amd64 / i386 Build Daemon (x86-ubc-01) 
> <buildd_amd64-x86-ubc...@buildd.debian.org>  Thu, 29 Jun 2017 23:57:24 +0000
> │ │ │ │ + -- amd64 / i386 Build Daemon (x86-ubc-01) 
> <buildd_amd64-x86-ubc...@buildd.debian.org>  Wed, 20 Sep 2017 03:33:46 +0000
> 

Hmm I wonder what would have been the correct version for the binNMU
there. Using +b3 instead would have been forbidden as the version in
stretch needs to be lower than the version in buster/sid.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature

Reply via email to