From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: misc/
Date: Sun, 19 Aug 2012 05:44:52 +0000 (UTC) [thread overview]
Message-ID: <1345355075.604eb9bd43ec035c4e26197ab21cba33b4faa8f9.zmedico@gentoo> (raw)
commit: 604eb9bd43ec035c4e26197ab21cba33b4faa8f9
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 19 05:44:35 2012 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sun Aug 19 05:44:35 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=604eb9bd
emerge-delta-webrsync: tweak "recompressing" msg
FEATURES=webrsync-gpg forces it to recompress in the foreground.
---
misc/emerge-delta-webrsync | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/misc/emerge-delta-webrsync b/misc/emerge-delta-webrsync
index e237c7f..102a991 100755
--- a/misc/emerge-delta-webrsync
+++ b/misc/emerge-delta-webrsync
@@ -541,15 +541,16 @@ fi
unset need_last_sync
if [ "$verified" == "1" ]; then
- echo "recompressing. (backgrounding)"
need_last_sync="dar"
if [[ ${WEBSYNC_VERIFY_SIGNATURE} == 1 ]] ; then
# BUG: Signature verification will fail if the local bzip2
# program does not produce output that is perfectly identical
# to the bzip2 program used to compress the signed tar file.
+ echo "recompressing ..."
bzip2 -vk9 "${TMPDIR}/portage-${final_date}.tar"
check_file_signature "${DISTDIR}/portage-${final_date}.tar.bz2.gpgsig" "${TMPDIR}/portage-${final_date}.tar.bz2" || exit 1
else
+ echo "recompressing. (backgrounding)"
bzip2 -vk9 "${TMPDIR}/portage-${final_date}.tar" &
fi
next reply other threads:[~2012-08-19 5:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 5:44 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-29 1:22 [gentoo-commits] proj/portage:master commit in: misc/ Zac Medico
2023-11-11 7:24 Sam James
2023-08-19 15:42 Sam James
2023-08-19 15:03 Sam James
2023-08-19 15:03 Sam James
2023-08-19 13:35 Sam James
2019-12-30 21:36 Zac Medico
2019-12-09 9:30 Zac Medico
2018-07-28 6:20 Zac Medico
2018-07-28 6:12 Zac Medico
2018-02-01 6:18 Zac Medico
2015-11-06 5:31 Zac Medico
2014-10-19 17:19 Zac Medico
2013-07-10 20:16 Zac Medico
2013-06-22 6:14 Zac Medico
2013-06-22 5:54 Zac Medico
2013-01-28 21:45 Zac Medico
2012-09-14 7:26 Zac Medico
2012-08-19 5:21 Zac Medico
2012-08-18 22:51 Zac Medico
2012-08-18 20:51 Zac Medico
2012-08-18 20:32 Zac Medico
2012-08-18 1:45 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 1:28 Zac Medico
2012-08-18 0:09 Zac Medico
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=1345355075.604eb9bd43ec035c4e26197ab21cba33b4faa8f9.zmedico@gentoo \
--to=zmedico@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