From: Adolf Belka <adolf.belka@ipfire.org>
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 [thread overview]
Message-ID: <691b42be-c8dc-9fe3-1430-a62fcec506e4@ipfire.org> (raw)
In-Reply-To: <B1EB913A-FE97-4D82-8B81-E1DEE5538489@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi Michael,
On 22/06/2021 10:56, Michael Tremer wrote:
> Hello,
>
> Thanks for letting me know. It looks like Marcel has replaced that file on the 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 from upstream) and the download should work now.
Yep, it's working fine now
Thanks very much.
Adolf.
>
> Best,
> -Michael
>
>> On 22 Jun 2021, at 08:40, Adolf Belka <adolf.belka(a)ipfire.org> 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 had 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 direct zstd-1.5.0.tar.gz file and the one in the IPFire source tree is the "Source code (tar.gz)" file.
>>
>> The source tree needs to be changed to use the direct file location.
>>
>>
>> Regards,
>>
>> Adolf.
>>
>
prev parent reply other threads:[~2021-06-22 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:40 Adolf Belka
2021-06-22 8:56 ` Michael Tremer
2021-06-22 11:56 ` Adolf Belka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=691b42be-c8dc-9fe3-1430-a62fcec506e4@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox