branch libreelec-10.0 download failures

doejohn · January 2, 2022 at 11:52 PM

Hello,

When trying to download packages for libreelec-10.0, I get following errors:

Code

2022-01-03 00:43:23 (62.8 MB/s) - '/m/s/rep/git/foreign/LibreELEC.tv/sources/ntfs-3g_ntfsprogs/ntfs-3g_ntfsprogs-2017.3.23AR.5.tgz' saved [3408]


WARNING      Incorrect checksum calculated on downloaded file: got 0eba1944975ef2d4a399c90a934c205720dd2c515bc953895668d9bc52158c5c wanted 04ccf583b495806cefb71850e5899e50aed5e7bf23365259f2badaa9af21e5ed
--2022-01-03 00:43:23--  http://sources.libreelec.tv/mirror/ntfs-3g_ntfsprogs/ntfs-3g_ntfsprogs-2017.3.23AR.5.tgz
[/code[


and


[code]
2022-01-03 00:44:16 (3.91 MB/s) - '/m/s/rep/git/foreign/LibreELEC.tv/sources/libretro-mame2016/libretro-mame2016-d53c379892b0bd91b4a52fc2de491e1199f03e32.tar.gz' saved [114716556]


WARNING      Incorrect checksum calculated on downloaded file: got 3d73ea1d7d3a1322495da60216c07bf3198b9eb7cfbc3b57f92014b381e020c2 wanted bafcac133ff37fb3adeafd9960427e3314e682caf22d455395855d64553d46fe
--2022-01-03 00:44:17--  http://sources.libreelec.tv/mirror/libretro-mame2016/libretro-mame2016-d53c379892b0bd91b4a52fc2de491e1199f03e32.tar.gz

Display More

Are those files corrupt?

**chewitt** · January 3, 2022 at 6:35 PM

Fixed in https://github.com/LibreELEC/Libr…31039a7c3586a84

doejohn · January 3, 2022 at 7:06 PM

Unfortunately, this fixes only ntfs.

It does not fix libretro-mame2016

**heitbaum** · January 4, 2022 at 2:38 AM Best Answer

PRs created:
https://github.com/LibreELEC/LibreELEC.tv/pull/6081

[le10] libretro-mame2016: update githash to 2021-12-07 by heitbaum · Pull Request #6082 · LibreELEC/LibreELEC.tv

backport of #6081 Incorrect checksum calculated on downloaded file reported in…

github.com

doejohn · January 4, 2022 at 9:15 AM

Thanks heitbaum!

I have an additional question, just to get a better understanding:

In the case of libretro-mame2016, isn't ${PKG_VERSION} the git sha of a specific commit in the upstream repository? How comes that the contents of this commit have changed over time? I always assumed git commits are unmodifiable?

**chewitt** · January 4, 2022 at 10:43 AM

As a developer I don't push zipped/rar'd/gunziped/xz'd archive files to the repo for people to download, I push source code and GitHub does magic in the background that allows people to download "packaged" sources. As long as nothing changes in the way that GitHub compresses things, we download the same file with the same SHA256 every time. However if GitHub updates the underlying infrastructure to get better compression etc. the file served for any githash can change and the SHA256 will need updating. It doesn't happen often, but it can and does happen occasionally.