From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/loop-aes-losetup/
Date: Thu, 20 Jun 2024 10:31:38 +0000 (UTC) [thread overview]
Message-ID: <1718879441.341b9bf36b212a4de56cc82c490e3aa4ddcbd480.sam@gentoo> (raw)
commit: 341b9bf36b212a4de56cc82c490e3aa4ddcbd480
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 20 10:30:41 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 20 10:30:41 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=341b9bf3
app-crypt/loop-aes-losetup: optimize src_unpack
As just done in util-linux & btrfs-progs.
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../loop-aes-losetup-2.40.1.ebuild | 23 ++++++++--------------
1 file changed, 8 insertions(+), 15 deletions(-)
diff --git a/app-crypt/loop-aes-losetup/loop-aes-losetup-2.40.1.ebuild b/app-crypt/loop-aes-losetup/loop-aes-losetup-2.40.1.ebuild
index 3d63e7cb0604..d73e67c758ad 100644
--- a/app-crypt/loop-aes-losetup/loop-aes-losetup-2.40.1.ebuild
+++ b/app-crypt/loop-aes-losetup/loop-aes-losetup-2.40.1.ebuild
@@ -51,24 +51,17 @@ PATCHES=(
)
src_unpack() {
- if use verify-sig ; then
- mkdir "${T}"/verify-sig || die
- pushd "${T}"/verify-sig &>/dev/null || die
-
- # Upstream sign the decompressed .tar
- # Let's do it separately in ${T} then cleanup to avoid external
- # effects on normal unpack.
- cp "${DISTDIR}"/${MY_P}.tar.xz . || die
- xz -d ${MY_P}.tar.xz || die
- verify-sig_verify_detached ${MY_P}.tar "${DISTDIR}"/${MY_P}.tar.sign "${BROOT}"/usr/share/openpgp-keys/karelzak.asc
-
- popd &>/dev/null || die
- rm -r "${T}"/verify-sig || die
+ # Upstream sign the decompressed .tar
+ if use verify-sig; then
+ einfo "Unpacking ${MY_P}.tar.xz ..."
+ verify-sig_verify_detached - "${DISTDIR}"/${MY_P}.tar.sign \
+ < <(xz -cd "${DISTDIR}"/${MY_P}.tar.xz | tee >(tar -x)) "${BROOT}"/usr/share/openpgp-keys/karelzak.asc
+ assert "Unpack failed"
verify-sig_verify_detached "${DISTDIR}"/${LOOPAES_P}.tar.bz2{,.sign}
+ else
+ default
fi
-
- default
}
src_prepare() {
next reply other threads:[~2024-06-20 10:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 10:31 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-13 5:56 [gentoo-commits] repo/gentoo:master commit in: app-crypt/loop-aes-losetup/ Sam James
2024-11-13 5:56 Sam James
2024-11-13 5:56 Sam James
2024-06-20 16:22 Sam James
2024-05-25 7:35 Sam James
2024-05-25 6:50 Sam James
2024-05-25 6:47 Sam James
2024-05-25 6:47 Sam James
2024-05-25 6:47 Sam James
2024-03-04 7:53 Joonas Niilola
2024-02-01 8:28 Joonas Niilola
2022-08-17 11:54 Andreas Sturmlechner
2020-06-08 13:41 Joonas Niilola
2020-06-08 13:41 Joonas Niilola
2020-06-08 13:41 Joonas Niilola
2017-03-25 21:46 Alon Bar-Lev
2017-03-18 11:21 Alon Bar-Lev
2017-03-05 9:19 Alon Bar-Lev
2017-02-04 1:31 Alon Bar-Lev
2017-01-13 19:16 Alon Bar-Lev
2015-12-24 17:10 Alon Bar-Lev
2015-12-23 11:16 Alon Bar-Lev
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=1718879441.341b9bf36b212a4de56cc82c490e3aa4ddcbd480.sam@gentoo \
--to=sam@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