From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: problem with downloading zstd from the IPFire source tree Date: Tue, 22 Jun 2021 09:56:29 +0100 Message-ID: In-Reply-To: <5f210a0a-2679-1464-bcd4-590f378eb5f5@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9160974503144428732==" List-Id: --===============9160974503144428732== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Thanks for letting me know. It looks like Marcel has replaced that file on th= e source server. @Marcel: You cannot do this. At all. Ever. Never never do it again. I have replaced it with the correct file (the released and signed tarball fro= m upstream) and the download should work now. Best, -Michael > On 22 Jun 2021, at 08:40, Adolf Belka wrote: >=20 > Hi All, >=20 > On the forum someone flagged they were having a failure when doing a build = with the download stage for zstd. >=20 >=20 > I checked and confirmed the problem if i removed the zstd source file I had= downloaded when doing the last update of zstd. >=20 >=20 > The file in the source tree has a different md5 sum as the one I used for t= he lfs file in my update build. >=20 >=20 > The download site https://github.com/facebook/zstd/releases/tag/v1.5.0 has = both a zstd-1.5.0.tar.gz and "Souce code (tar.gz)" entry. >=20 > Checking the md5 sums the one used in my build patch submission was the dir= ect zstd-1.5.0.tar.gz file and the one in the IPFire source tree is the "Sour= ce code (tar.gz)" file. >=20 > The source tree needs to be changed to use the direct file location. >=20 >=20 > Regards, >=20 > Adolf. >=20 --===============9160974503144428732==--