Bad data in tlnet mirror

[Norbert Preining]

On Fri, 29 Nov 2019, Fransson Mattias wrote:
> I've done multiple "rsync -av --delete", so I believe my copy should be in sync with the upstream.

Ok.

> How can I generate the checksum for a file myself? Are they all sha512?

Yes.

> Maybe I could manually try to verify the file on the webserver and see if it gets mangled on download?

Yes, that would be good. You can look up the checksum in the
texlive.tlpdb. It contains lines

	name a2ping
	...
	containerchecksum 983084ca3d70eff729d81d5d52a74e1bf1f95e384916bc81d17be81290f70c1da5ac891c1665a2451975f36fd56ea0036e1d0dc46b2e98b61ddc660ac044c23c
	doccontainerchecksum daeefb01a0197e3b7751614cb84e2926f670d36b7e8a389bfbbe39cbd941c4d10ef5112593bfb88e11fa15f7f7bb07f2538c7d0a68cefe1482bbdaf02d475512

	name a2ping.x86_64-linux
	...
	containerchecksum f4eeb76fbc182a73eccd3086b632005b8bed0615634247f84ddbe3e12b24d7c592bf7a8d158d7ad738ed536c5fa753fda86a670c0e899b48e7d05ac0e1c9c3e6

This gives the sha512 sums of 
	a2ping.tar.xz
	a2ping.doc.tar.xz
	a2ping.x86_64-linux.tar.xz
respectively.


> # cat ./tlnet/tlpkg/texlive.tlpdb.sha512
> 71721924df93f572b34b45507752271891037ce3ea19982911dc918e587996fa5477a3361c8b187f0eed1b6a709600b7b6d53e4befd4e63aa9fd45e48e28352a  texlive.tlpdb

That is from 2019-11-28.

> # find . -ls

I didn't check all the values, but the file sizes for a2ping which
crashed during installation were correct.

So it is **very** cryptic what is going on here.

Best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13