From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dhcpcd: Update to version 10.0.8
Date: Wed, 29 May 2024 10:11:39 +0100 [thread overview]
Message-ID: <D5CE6542-5CB8-4CFE-8B5C-736E793A386B@ipfire.org> (raw)
In-Reply-To: <20240528154144.3777068-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 28 May 2024, at 16:41, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from version 10.0.6 to 10.0.8
> - Update of rootfile not required
> - Changelog
> 10.0.8
> Fixed compile without ARP
> Fixed closefrom test for glibc
> Fixed spelling of ADVERTISEMENT
> 10.0.7
> DHCP: use request_time, fallback_time and ipv4ll_time rather than reboot
> timeout
> DHCP6: Wait for IRT to elapse before requesting advertisments
> DHCPv6: Don't re-INFORM if the RA changes
> privsep: Reduce fd use
> dhcpcd: Add support for arp persist defence by @pradeep-brightsign in #273
> Move dhcp(v4) packet size check earlier by @pemensik in #295
> Define the Azure Endpoint and other site-specific options by @lparkes in #299
> add RFC4191 support by @goertzenator in #297
> dhcpcd: Respect IPV6_PREFERRED_ONLY flag regardless of state by @taoyl-g
> in #307
> Fix time_offset to be int to match RFC-2132 by @ColinMcInnes in #319
> hooks/30-hostname: Exit with 0 if setting hostname is not needed by @bdrung
> in #320
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/dhcpcd | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/dhcpcd b/lfs/dhcpcd
> index 4a2368562..3bac681d8 100644
> --- a/lfs/dhcpcd
> +++ b/lfs/dhcpcd
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 10.0.6
> +VER = 10.0.8
>
> THISAPP = dhcpcd-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 4afd08cf7377b2262d33bf3f7ac503e081572a7c1ffd53b285842a92d99d88fae44e7e6384134bbe1eb839001f822fa7fb43718c42f9e8e6d11a05ec66fa2fc6
> +$(DL_FILE)_BLAKE2 = 1bf27387c13f192c6216e2f1ecad06bfa82267d5d6e08ddaa123789699fe9154222c33b1aa1f603e65ae8dce510cb24d48e72701494e0793c766e81f024f8bc5
>
> install : $(TARGET)
>
> --
> 2.44.0
>
prev parent reply other threads:[~2024-05-29 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 15:41 Adolf Belka
2024-05-28 15:41 ` [PATCH] sqlite: Update to version 3.46.0 Adolf Belka
2024-05-29 9:11 ` Michael Tremer
2024-05-29 9:11 ` Michael Tremer [this message]
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=D5CE6542-5CB8-4CFE-8B5C-736E793A386B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@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