El 05/07/23 a las 10:26, Moritz Muehlenhoff escribió: > On Tue, Jul 04, 2023 at 03:17:43PM -0400, Roberto C. Sánchez wrote: > > On Fri, Jun 16, 2023 at 10:12:22PM +0200, Moritz Muehlenhoff wrote: > > > On Fri, Jun 16, 2023 at 01:29:28PM -0400, Roberto C. Sánchez wrote: > > > > On Wed, May 17, 2023 at 10:50:34AM +0200, Moritz Muehlenhoff wrote: > > > > > > > > > > My take would be to mark it as unsupported after the trixie > > > > > development cycle > > > > > has started (this flags awareness, but has no impact on stable > > > > > releases) > > > > > and then revisit the support situation before the trixie freeze (Kea > > > > > might be > > > > > a full replacment by then or maybe it turns out the patch support is > > > > > ensured > > > > > despite upstream's EOL) > > > > > > > > > Hi Moritz, > > > > > > > > Now that bookworm is out and (AFAICT) that the trixie development cycle > > > > has started, are able to go ahead with marking isc-dhcp as unsupported? > > > > > > Ultimately it's the maintainer(s) call, but sounds good to me. > > > > > Are you referring to the maintainer of debian-security-support, or the > > maintainer of isc-dhcp? > > The isc-dhcp maintainers.
https://salsa.debian.org/debian/debian-security-support/-/merge_requests/16 I hope the above mentioned MR reflects the thread consensus. It is been a long time since I haven't made any change to debian-security-support, please review it, in case I am doing some stupidity. Cheers, -- S
signature.asc
Description: PGP signature
