From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: problem with downloading zstd from the IPFire source tree Date: Tue, 22 Jun 2021 13:56:06 +0200 Message-ID: <691b42be-c8dc-9fe3-1430-a62fcec506e4@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5863793068695997600==" List-Id: --===============5863793068695997600== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 22/06/2021 10:56, Michael Tremer wrote: > Hello, >=20 > Thanks for letting me know. It looks like Marcel has replaced that file on = the source server. >=20 > @Marcel: You cannot do this. At all. Ever. Never never do it again. >=20 > I have replaced it with the correct file (the released and signed tarball f= rom upstream) and the download should work now. Yep, it's working fine now Thanks very much. Adolf. >=20 > Best, > -Michael >=20 >> On 22 Jun 2021, at 08:40, Adolf Belka wrote: >> >> Hi All, >> >> On the forum someone flagged they were having a failure when doing a build= with the download stage for zstd. >> >> >> I checked and confirmed the problem if i removed the zstd source file I ha= d downloaded when doing the last update of zstd. >> >> >> The file in the source tree has a different md5 sum as the one I used for = the lfs file in my update build. >> >> >> 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. >> >> Checking the md5 sums the one used in my build patch submission was the di= rect zstd-1.5.0.tar.gz file and the one in the IPFire source tree is the "Sou= rce code (tar.gz)" file. >> >> The source tree needs to be changed to use the direct file location. >> >> >> Regards, >> >> Adolf. >> >=20 --===============5863793068695997600==--