[Debian-ports-devel] Corrupted APT meta-deta for sh4

John Paul Adrian Glaubitz glaubitz at physik.fu-berlin.de
Sat Mar 26 13:43:08 UTC 2016


Hi Aurelien!

We are still having issues with the APT meta-data, this time sh4 is
affected [1]:

Err:60 ftp://ftp.debian-ports.org/debian unstable/main sh4 libopenexr22
sh4 2.2.0-10
  Writing more data than expected (630654 > 630196) [IP: 206.12.19.127 21]
Err:61 ftp://ftp.debian-ports.org/debian unstable/main sh4
libopenexr-dev sh4 2.2.0-10
  Undetermined Error [IP: 206.12.19.127 21]
Err:62 ftp://ftp.debian-ports.org/debian unstable/main sh4 libpaper1 sh4
1.1.24+nmu4
  Undetermined Error [IP: 206.12.19.127 21]
Err:63 ftp://ftp.debian-ports.org/debian unstable/main sh4 libpcrecpp0v5
sh4 2:8.35-8
  Undetermined Error [IP: 206.12.19.127 21]
Err:64 ftp://ftp.debian-ports.org/debian unreleased/main sh4 libproxy1
sh4 0.4.11-4+sh4.1
  Undetermined Error [IP: 206.12.19.127 21]
Err:65 ftp://ftp.debian-ports.org/debian unstable/main sh4 libsm6 sh4
2:1.2.2-1
  Undetermined Error [IP: 206.12.19.127 21]

We had a similar problem with m68k before when two buildds uploaded the
same package shortly after each other and therefore the meta-data did
no longer match the actual files in the archive.

I'm not sure what happened with sh4 this time, but do you think you
could apply the same fix you applied for m68k by forcing the
regeneration of the archive meta-data?

Thanks,
Adrian

> [1]
https://buildd.debian.org/status/fetch.php?pkg=opencv&arch=sh4&ver=2.4.9.1%2Bdfsg-1.4&stamp=1458706211

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz at debian.org
`. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



More information about the Debian-ports-devel mailing list