From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core202, updated. f7898141e90ce8241ac31ee40417f3addb90599e
Date: Thu, 21 May 2026 09:51:03 +0000 (UTC) [thread overview]
Message-ID: <4gLkF31M2Gz2xJB@people01.haj.ipfire.org> (raw)
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, core202 has been updated
via f7898141e90ce8241ac31ee40417f3addb90599e (commit)
from dfcc64bd8aac6809d1c058cd891fddb373cb94d5 (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 f7898141e90ce8241ac31ee40417f3addb90599e
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu May 21 09:50:36 2026 +0000
unbound: Fix hash
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/unbound | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/unbound b/lfs/unbound
index 7fe47f5b6..5bbeee66b 100644
--- a/lfs/unbound
+++ b/lfs/unbound
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 925d964cfaa76211b5d71ab7d16318327417e7e85791ef3b7b442b0b417e1e29fb925b7a1f3427105cc9114b5b8c093ecc9a9aa5c3457620f622a24ed3674de3
+$(DL_FILE)_BLAKE2 = da9818a14a540bf2d674f504a38da711cfead20af2c6f987aab74094b441ef31586f28608432d2369b2223b3287290f450218466654c71626e33df74da557f18
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-21 9:51 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=4gLkF31M2Gz2xJB@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