From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dhcp: Update to 4.4.3-P1
Date: Mon, 10 Oct 2022 10:39:43 +0100 [thread overview]
Message-ID: <DA1E75D9-4B00-4FAD-9BB3-0A792D8338F7@ipfire.org> (raw)
In-Reply-To: <20221007195921.3651616-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Hello Matthias,
This is very interesting that ISC DHCP is now practically EOL.
> NOTE: This software is now End-Of-Life. 4.4.3 is the final release planned.
> We will continue to keep the public issue tracker and user mailing list open.
I would say, that for IPFire 2 this does not matter too much and we won’t replace it. But of course any new implementations should no longer rely on this.
-Michael
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 7 Oct 2022, at 20:59, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> For details see:
> https://downloads.isc.org/isc/dhcp/4.4.3-P1/dhcp-4.4.3-P1-RELNOTES
>
> Changelog since 4.4.1 is rather long...
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/dhcp | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/dhcp b/lfs/dhcp
> index 93471954f..6849e7dff 100644
> --- a/lfs/dhcp
> +++ b/lfs/dhcp
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 4.4.1
> +VER = 4.4.3-P1
>
> THISAPP = dhcp-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -42,7 +42,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = fd3c65d8802c42cb936ff75ee19784e4f533c9b36aa08a61280aa8acae5cf581c67cd70222b46eb24b1f9a571e1c028cc853952feac4b6a12f9b7d7d3dbc2fc9
> +$(DL_FILE)_BLAKE2 = 6cc16f7472efb1e1f6b7a83cafd9a81a16f10af7361da079c48a5eff0d9e310f475dcc82e984c20936c64867183402d00d26e5366e75bf7463ec2aea4a6f68a4
>
> install : $(TARGET)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2022-10-10 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 19:59 Matthias Fischer
2022-10-10 9:39 ` 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=DA1E75D9-4B00-4FAD-9BB3-0A792D8338F7@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