From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: problem with downloading zstd from the IPFire source tree
Date: Tue, 22 Jun 2021 09:40:58 +0200 [thread overview]
Message-ID: <5f210a0a-2679-1464-bcd4-590f378eb5f5@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
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.
next reply other threads:[~2021-06-22 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:40 Adolf Belka [this message]
2021-06-22 8:56 ` Michael Tremer
2021-06-22 11:56 ` Adolf Belka
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=5f210a0a-2679-1464-bcd4-590f378eb5f5@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