Your message dated Sun, 18 Jun 2017 23:09:13 +0200
with message-id <[email protected]>
and subject line Missing file in Debian mirrors prevents debmirror working
has caused the Debian Bug report #686064,
regarding Packages.diff/Index is invalid on s390x and armhf, listing last entry
twice
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 [email protected]
immediately.)
--
686064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686064
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: important
The last entries in Packages.diff/Index of s390x and armhf are incorrectly
duplicated:
$ wget -q
http://ftp.fr.debian.org/debian/dists/wheezy/main/binary-armhf/Packages.diff/Index
-O - | sort | uniq -c| grep -E "^\s+2"
2 b56b4c25007235f27328d0ca38a9a4334528ab17 25767 2012-12-27-0211.10
2 bf74965092c8c5d15b028c604bfee0e2499342c1 27653345 2012-12-27-0211.10
$ wget -q
http://ftp.fr.debian.org/debian/dists/wheezy/main/binary-s390x/Packages.diff/Index
-O - | sort | uniq -c| grep -E "^\s+2"
2 b56b4c25007235f27328d0ca38a9a4334528ab17 25767 2012-12-27-0211.10
2 bf74965092c8c5d15b028c604bfee0e2499342c1 27653345 2012-12-27-0211.10
I detected this thanks to a warning generated by reprepro while trying to mirror
the Debian archive.
It also seems weird that both architectures are exactly identical and leading
to the same
Packages.diff/Index.
$ wget -q http://ftp.fr.debian.org/debian/dists/wheezy/Release -O - | sed -e
's|binary-[^/]*/|binary-foo/|' | sort| uniq -c | grep -v -E "^\s+1"
2 03326a2674f9b2c65e6a38ceebdd49b8 7819
non-free/binary-foo/Packages.diff/Index
2 11b6d244505f59e0fa0082c4927d74a7 7876
main/binary-foo/Packages.diff/Index
2 187f4a2e81c243b07df4eb42deec5c33cd75d85a 7876
main/binary-foo/Packages.diff/Index
2 a36e661f11a6025073ee1aba464665682ce05975 7819
non-free/binary-foo/Packages.diff/Index
2 bfcc09774bd884779ce9d195cc3385888d6ae9f5 7819
contrib/binary-foo/Packages.diff/Index
2 cb987e9baa77bff07f8a309686d100930a9185cd430765f2d3a78edb3fa69f7e
7819 contrib/binary-foo/Packages.diff/Index
2 d012373eb2d10c7ecc87617cc987d487 7819
contrib/binary-foo/Packages.diff/Index
2 e8e5258c24c588f20bf766991ef5ae8ea42d5dd74b0335eb9a2965f7df10f927
7819 non-free/binary-foo/Packages.diff/Index
2 ffae82effabfc6bdf61f9ffca3bb2e60f0eabb50bf014d314630c3a791287921
7876 main/binary-foo/Packages.diff/Index
If you check out those hashes, they correspond to armhf/s390x.
Maybe there's a misconfiguration that leads to the usage of the same file for
both architectures?
Cheers,
Raphaël Hertzog.
--- End Message ---
--- Begin Message ---
Hi
long ago, and by now that file definitely does not matter anymore.
The generation code also should be more stable, and somewhere between
then and now we also added more verification of mirror structure, which
all should hopefully help for this to not reappear.
--
bye, Joerg
--- End Message ---
