From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 61105fd16e5edc8c15641a4971da9a565052c427
Date: Mon, 24 Feb 2025 18:01:53 +0000 [thread overview]
Message-ID: <4Z1pTY30G8z2yDc@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2141 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 61105fd16e5edc8c15641a4971da9a565052c427 (commit)
from 30f8ec8f757e33fcdda8abe85abb7f87e715596e (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 61105fd16e5edc8c15641a4971da9a565052c427
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Mon Feb 24 19:00:22 2025 +0100
dhcpcd: Update to 10.20.1
For details see:
https://github.com/NetworkConfiguration/dhcpcd/releases/tag/v10.2.1
"What's Changed
Fix building with different options by @rsmarples in #461
Only drop IPv4 LL addresses if configured to handle them
by @ColinMcInnes in #464"
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/dhcpcd | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/dhcpcd b/lfs/dhcpcd
index 6b77a9db7..43d43f64a 100644
--- a/lfs/dhcpcd
+++ b/lfs/dhcpcd
@@ -24,7 +24,7 @@
include Config
-VER = 10.2.0
+VER = 10.2.1
THISAPP = dhcpcd-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 0b209f253e6462cc176ffef749228fc3b82474ee4baa2c468277b58abea9541282a2a96633e88641c46e3e9a612049f574009dd42f00f86334e655b10c234e81
+$(DL_FILE)_BLAKE2 = f550f69a3db07e9b388e5e24fe94820e25c91aa5332bc32120194d268d1697fd1db2f5619119f030fd9774336757709b40416333a3f0f5beb9fa25e64f451134
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-02-24 18:01 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=4Z1pTY30G8z2yDc@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