On 6/21/26 19:20, John Paul Adrian Glaubitz wrote:
Hi Christoph,
On Sun, 2026-06-21 at 18:41 +0200, Christoph Biedl wrote:
Affected are these URLs:
http://ftp.de.debian.org/debian-ports/pool-hppa/main/g/gcc-16/libgomp1_16.1.0-2_hppa.deb
http://ftp.de.debian.org/debian-ports/pool-hppa/main/g/gcc-16/libgcc-s4_16.1.0-2_hppa.deb
http://ftp.de.debian.org/debian-ports/pool-hppa/main/g/gcc-16/libcc1-0_16.1.0-2_hppa.deb
http://ftp.de.debian.org/debian-ports/pool-hppa/main/g/gcc-16/libatomic1_16.1.0-2_hppa.deb
http://ftp.de.debian.org/debian-ports/pool-hppa/main/g/gcc-16/libstdc%2b%2b6_16.1.0-2_hppa.deb
Now I'm fairly certain this is outside my control. A check on a second
mirror returned the same result. Can someone take a look into this?
(...)
Further information, based on the mtime: The "received" package was
installed on the mirror on 1781589787 (2026-06-16T06:03:07) and
appearently replaced with the "expected" content on 1781805793
(2026-06-18 18:03:13.886190374 +0000). While TTBOMK there is no
guarantee a Debian package file name is unique in a mirror, violating
that causes confusion.
The issue is that gcc-16 was built and uploaded twice for the same version:
https://buildd.debian.org/status/logs.php?pkg=gcc-16&arch=hppa
There was indeed issues last week when the "pacific" buildd tried to upload the
packages
which were built there. I think the upload never finished, so I had to cancel
it manually and tried another upload.
In summary: Yes, there were upload issues. I hope the trigger to rebuild
the package fixes it.
Helge
