From: "Matthew Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/releng:master commit in: tools-musl/
Date: Fri, 24 May 2019 03:50:27 +0000 (UTC) [thread overview]
Message-ID: <1558669812.96fc8a991b72df2bec314ea15a39c65691612a59.prometheanfire@gentoo> (raw)
commit: 96fc8a991b72df2bec314ea15a39c65691612a59
Author: Matthew Thode <mthode <AT> mthode <DOT> org>
AuthorDate: Fri May 24 03:50:12 2019 +0000
Commit: Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Fri May 24 03:50:12 2019 +0000
URL: https://gitweb.gentoo.org/proj/releng.git/commit/?id=96fc8a99
new musl stage4 uses xz
tools-musl/run-stage4.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools-musl/run-stage4.sh b/tools-musl/run-stage4.sh
index 5bfe74e6..2a5263bb 100755
--- a/tools-musl/run-stage4.sh
+++ b/tools-musl/run-stage4.sh
@@ -16,8 +16,8 @@ sed -i "s|MY_DATE|${MY_DATE}|g" "${MUSL_DIR}"/stage4-hardened-amd64-configured.s
catalyst -f "${MUSL_DIR}"/stage4-hardened-amd64-configured.spec | tee -a "${MUSL_DIR}"/zzz.log
# update link, rm -f returns 0 if file isn't there yet
-rm -f "${storedir}/builds/musl/hardened/amd64/stage4-amd64-musl-hardened.tar.bz2"
-ln -s "${storedir}/builds/musl/hardened/amd64/stage4-amd64-musl-hardened-${MY_DATE}.tar.bz2" "${storedir}/builds/musl/hardened/amd64/stage4-amd64-musl-hardened.tar.bz2"
+rm -f "${storedir}/builds/musl/hardened/amd64/stage4-amd64-musl-hardened.tar.xz"
+ln -s "${storedir}/builds/musl/hardened/amd64/stage4-amd64-musl-hardened-${MY_DATE}.tar.xz" "${storedir}/builds/musl/hardened/amd64/stage4-amd64-musl-hardened.tar.xz"
# remove old specfile
rm "${MUSL_DIR}"/stage4-hardened-amd64-configured.spec
next reply other threads:[~2019-05-24 3:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 3:50 Matthew Thode [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-14 19:11 [gentoo-commits] proj/releng:master commit in: tools-musl/ Anthony G. Basile
2019-04-13 10:54 Anthony G. Basile
2019-04-11 1:37 Anthony G. Basile
2018-03-02 16:25 Anthony G. Basile
2017-01-05 5:41 Matt Thode
2017-01-03 3:01 Matt Thode
2017-01-02 23:59 Matt Thode
2017-01-02 4:30 Matt Thode
2017-01-02 4:21 Matt Thode
2017-01-02 4:08 Matt Thode
2016-06-04 16:07 Anthony G. Basile
2015-12-07 0:54 Anthony G. Basile
2015-06-14 21:32 Anthony G. Basile
2015-06-14 21:01 Anthony G. Basile
2015-01-20 23:38 Anthony G. Basile
2014-08-18 21:59 Robin H. Johnson
2014-08-18 21:59 Robin H. Johnson
2014-08-13 14:28 Anthony G. Basile
2014-08-11 22:43 Anthony G. Basile
2014-06-28 10:43 Anthony G. Basile
2014-06-18 11:14 Anthony G. Basile
2014-02-18 21:04 Anthony G. Basile
2014-02-06 13:06 Anthony G. Basile
2014-02-05 20:13 Anthony G. Basile
2014-02-05 20:11 Anthony G. Basile
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=1558669812.96fc8a991b72df2bec314ea15a39c65691612a59.prometheanfire@gentoo \
--to=prometheanfire@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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