From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e84497de672c38d17bace334ef6c67dde54c49ff
Date: Wed, 22 Jun 2022 14:33:02 +0000 [thread overview]
Message-ID: <4LSm7y65M3z2y7l@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1640 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 e84497de672c38d17bace334ef6c67dde54c49ff (commit)
from 2f52d27a829a891b3cff549f2b0a0763915f8311 (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 e84497de672c38d17bace334ef6c67dde54c49ff
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Wed Jun 22 14:32:39 2022 +0000
Crap, OpenSSL download server returned a corrputed file :-/
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/openssl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/openssl b/lfs/openssl
index 43401237a..88f533323 100644
--- a/lfs/openssl
+++ b/lfs/openssl
@@ -74,7 +74,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 723c7784f39d7a475c190f0399b3721a6f315e1ea6f92617e12bfed3701609398b52d7881a6111c9260337cf369a85cc66f3d368043ab31a19ca5c8eb2237214
+$(DL_FILE)_BLAKE2 = 4354753a5e52393c9cc4569954c2cac6d89a1e204fa4f9ca00a60492782d29f8952fb92664cdbb3576c6443d3cb2eacebea51db584738589f3598b40df579b12
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-06-22 14:33 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=4LSm7y65M3z2y7l@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