[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#876633: nmu: libselinux_2.6-3+b2



Package: release.debian.org
Severity: normal
User: release.debian.org@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-01@buildd.debian.org>  Thu, 29 Jun 2017 23:57:24 +0000
│ │ │ │ + -- amd64 / i386 Build Daemon (x86-ubc-01) <buildd_amd64-x86-ubc-01@buildd.debian.org>  Wed, 20 Sep 2017 03:33:46 +0000



Long story short, while I can purge the files in my cache to unbreak my
private buildd, please still consider another binNMU for src:libselinux
to resolve this situation in a sane way.

This is the line as proposed by reportbug. Please double-check:

nmu libselinux_2.6-3+b2 . ANY . stretch . -m "Resolve version number collision"

Regards,
    Christoph

[1] http://ftp.debian.org/debian/pool/main/libs/libselinux/
[2] http://snapshot.debian.org/archive/debian/20170630T033759Z/pool/main/libs/libselinux/


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.51 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Attachment: signature.asc
Description: Digital signature


Reply to: