From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. cec532b4cc501ee5b97c64d7f042bbcdc58283bf
Date: Wed, 14 Jul 2021 08:30:42 +0000 [thread overview]
Message-ID: <4GPrLC1KXPz2xbk@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via cec532b4cc501ee5b97c64d7f042bbcdc58283bf (commit)
from 5621b0ef0a6b7e36966d9183979538ab5a0b08b5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit cec532b4cc501ee5b97c64d7f042bbcdc58283bf
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Jul 11 14:12:15 2021 +0100
make.sh: Explicitely call zstd to extract toolchain
Some older versions of tar do not recognise Zstandard, yet.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
Tested-by: Peter Müller <peter.mueller(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index 7bdeeaf62..13a48f461 100755
--- a/make.sh
+++ b/make.sh
@@ -1735,7 +1735,7 @@ build)
PACKAGENAME=${PACKAGE%.tar.zst}
print_build_stage "Packaged toolchain compilation"
if [ `md5sum $PACKAGE | awk '{print $1}'` == `cat $PACKAGENAME.md5 | awk '{print $1}'` ]; then
- tar axf $PACKAGE
+ zstd -d < "${PACKAGE}" | tar x
prepareenv
else
exiterror "$PACKAGENAME md5 did not match, check downloaded package"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-07-14 8:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4GPrLC1KXPz2xbk@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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