From: "Sebastian Pipping" <sping@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/dcfldd/
Date: Sun, 12 Jan 2025 17:48:22 +0000 (UTC) [thread overview]
Message-ID: <1736703990.a3f668d0f70f94d7c5154084703ac75355b17998.sping@gentoo> (raw)
commit: a3f668d0f70f94d7c5154084703ac75355b17998
Author: Sebastian Pipping <sping <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 12 17:46:30 2025 +0000
Commit: Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Sun Jan 12 17:46:30 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a3f668d0
sys-apps/dcfldd: Improve test for miscompilation
Closes: https://bugs.gentoo.org/947985
Signed-off-by: Sebastian Pipping <sping <AT> gentoo.org>
sys-apps/dcfldd/dcfldd-1.9.2-r1.ebuild | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/sys-apps/dcfldd/dcfldd-1.9.2-r1.ebuild b/sys-apps/dcfldd/dcfldd-1.9.2-r1.ebuild
index 9ed9f564a117..3a9a2897ec46 100644
--- a/sys-apps/dcfldd/dcfldd-1.9.2-r1.ebuild
+++ b/sys-apps/dcfldd/dcfldd-1.9.2-r1.ebuild
@@ -44,10 +44,9 @@ src_test() {
# Smoke test for Gentoo bug #930996
# Inspired by https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698#c0
- expected_sha256sum="$(sha256sum <<<TestInput | awk '{print $1}' \
- | tee /dev/stderr)"
+ expected_sha256sum="$(sha256sum <<<TestInput | awk '{print $1}')"
actual_sha256sum="$(dcfldd hash=sha256 2>&1 <<<TestInput \
- | grep -F sha256 | awk '{print $3}' | tee /dev/stderr)"
+ | grep -F sha256 | awk '{print $3}')"
[[ ${actual_sha256sum} = ${expected_sha256sum} ]] \
- || die "dcfldd did not produce the expected SHA256 sum."
+ || die "dcfldd produced \"${actual_sha256sum}\" instead of expected \"${expected_sha256sum}\"."
}
next reply other threads:[~2025-01-12 17:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 17:48 Sebastian Pipping [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 9:53 [gentoo-commits] repo/gentoo:master commit in: sys-apps/dcfldd/ Sebastian Pipping
2025-01-11 21:57 Sebastian Pipping
2024-12-21 3:11 Sam James
2024-12-21 3:11 Sam James
2024-10-21 0:45 Sebastian Pipping
2024-10-21 0:45 Sebastian Pipping
2024-05-06 13:27 Sam James
2024-05-06 13:27 Sam James
2024-05-01 18:42 Sebastian Pipping
2023-04-26 14:41 Sebastian Pipping
2023-04-26 14:41 Sebastian Pipping
2023-02-12 4:47 Sebastian Pipping
2023-02-11 0:22 Sebastian Pipping
2023-02-11 0:20 Sebastian Pipping
2023-01-11 22:59 Sam James
2023-01-11 21:43 Sam James
2022-11-29 1:18 Sebastian Pipping
2022-10-17 22:50 Sebastian Pipping
2022-05-25 16:50 Jakov Smolić
2021-08-18 11:02 Sebastian Pipping
2021-03-13 13:43 Sebastian Pipping
2021-03-13 11:37 Sam James
2021-03-13 11:36 Sam James
2020-04-15 11:28 Sebastian Pipping
2020-01-27 0:27 Jeroen Roovers
2020-01-02 0:06 Jeroen Roovers
2019-02-10 12:12 Mikle Kolyada
2019-02-10 12:12 Mikle Kolyada
2019-02-10 12:12 Mikle Kolyada
2018-08-11 9:06 Andreas Sturmlechner
2017-08-11 17:38 Michał Górny
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=1736703990.a3f668d0f70f94d7c5154084703ac75355b17998.sping@gentoo \
--to=sping@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