Bug#1000662: Bug#995189: RFH: isc-dhcp
On Tue, Feb 22, 2022 at 10:58 AM Santiago R.R. wrote: > > El 22/02/22 a las 10:09, Martin-Éric Racine escribió: > > On Tue, Feb 22, 2022 at 5:31 AM Martin-Éric Racine > > wrote: > ... > > > > > > Please note that there are now 2 upstream repos, if you wanna cherry > > > pick CVE fixes: > > > > > > https://github.com/isc-projects/dhcp > > > https://gitlab.isc.org/isc-projects/dhcp > > > > > > GitHub seems to be abandoned, while GitLab regularly sees commits and > > > is where I found the 4.4.3 beta. > > > > > > Tarballs are still here: > > > > > > https://downloads.isc.org/isc/dhcp/ > > > > To top it all, upstream has decided to retire this codebase by the end > > of this year: > > > > https://www.isc.org/blogs/dhcp-client-relay-eom/ > > > > This will have 2 impacts for Debian: > > > > 1) Whatever outstanding bugs Debian has will have to be solved and > > applicable patches pushed upstream ASAP or closed as won't fix. > > > > 2) Debian will have to either agree with other distros on a common > > fork to maintain or find a new DHCP client to replace the ISC client. > > > > Indeed. And a minor degree, the DHCP relay. > > Thanks for pointing this out! This impact especially concerns ifupdown, > for which an alternative Recommended dhcp client has to be found. See also: Bug#1006263: ifupdown: outdated DHCP client support Bug#1006264:RFH: dhcpcd5 -- DHCPv4, IPv6RA and DHCPv6 client with IPv4LL support Martin-Éric
Bug#995189: RFH: isc-dhcp
El 22/02/22 a las 10:09, Martin-Éric Racine escribió: > On Tue, Feb 22, 2022 at 5:31 AM Martin-Éric Racine > wrote: ... > > > > Please note that there are now 2 upstream repos, if you wanna cherry > > pick CVE fixes: > > > > https://github.com/isc-projects/dhcp > > https://gitlab.isc.org/isc-projects/dhcp > > > > GitHub seems to be abandoned, while GitLab regularly sees commits and > > is where I found the 4.4.3 beta. > > > > Tarballs are still here: > > > > https://downloads.isc.org/isc/dhcp/ > > To top it all, upstream has decided to retire this codebase by the end > of this year: > > https://www.isc.org/blogs/dhcp-client-relay-eom/ > > This will have 2 impacts for Debian: > > 1) Whatever outstanding bugs Debian has will have to be solved and > applicable patches pushed upstream ASAP or closed as won't fix. > > 2) Debian will have to either agree with other distros on a common > fork to maintain or find a new DHCP client to replace the ISC client. > Indeed. And a minor degree, the DHCP relay. Thanks for pointing this out! This impact especially concerns ifupdown, for which an alternative Recommended dhcp client has to be found. Cheers, -- Santiago P.S. BTW, co-maintainers are welcome ;-) signature.asc Description: PGP signature
Bug#1000662: Bug#995189: RFH: isc-dhcp
On Tue, Feb 22, 2022 at 5:31 AM Martin-Éric Racine wrote: > > On Mon, Feb 21, 2022 at 11:44 PM Santiago R.R. wrote: > > > > El 21/02/22 a las 15:19, Martin-Éric Racine escribió: > > > On Mon, Feb 21, 2022 at 2:18 PM Martin-Éric Racine > > > wrote: > > > > > > > > On Thu, Jan 6, 2022 at 8:40 PM Santiago R.R. > > > > wrote: > > > > > On January 6, 2022 4:49:49 AM GMT-05:00, "Martin-Éric Racine" > > > > > wrote: > > > > > >Hello again, > > > > > > > > > > > >ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón > > > > > >(santiag...@riseup.net) kirjoitti: > > > > > >> El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > > > > > >> > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > > > > > >> > (santiag...@riseup.net) kirjoitti: > > > > > >> > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > > > > >> > > > Package: wnpp > > > > > >> > > > Severity: normal > > > > > >> > > > X-Debbugs-Cc: debian-de...@lists.debian.org > > > > > >> > > > Control: affects -1 src:isc-dhcp > > > > > >> > > > > > > > > >> > > > -BEGIN PGP SIGNED MESSAGE- > > > > > >> > > > Hash: SHA256 > > > > > >> > > > > > > > > >> > > > The ISC DHCP suite has a lenghty list of bug reports that > > > > > >> > > > have been left unattended. Some bugs date back to DHCP 3 or > > > > > >> > > > even earlier. > > > > > >> > > > > > > > > >> > > > Additionally, recent upstream releases are still unpackaged. > > > > > >> > > > One release came out well ahead of the Bullseye freeze, a > > > > > >> > > > bug report requesting its packaging was filed, but it > > > > > >> > > > remains unanswered. > > > > > >> > > > > > > > > >> > > > Leaving a package with a priority Important in such utter > > > > > >> > > > state of neglect is unacceptable. > > > > > >> > > > > > > > > >> > > > At this point, it has become clear that, at the very least, > > > > > >> > > > its maintainers need help, hence why I filed this WNPP bug. > > > > > >> > > > > > > > >> > > Indeed. I am willing to spend some cycles to help maintaining > > > > > >> > > it. I > > > > > >> > > requested access to the ISC DHCP packaging team in salsa ~a > > > > > >> > > couple of > > > > > >> > > weeks ago, but I hasn't been answered yet (mgilbert is its > > > > > >> > > only member). > > > > > >> > > It was on my ToDo list to ping the maintainers (in CC). > > > > > >> > > > > > > >> > Has any progress taken place on this? > > > > > >> > > > > > >> I've started doing some work at > > > > > >> https://salsa.debian.org/santiago/isc-dhcp/ > > > > > >> > > > > > >> I still didn't get any answer from current maintainers (keeping > > > > > >> them in > > > > > >> CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > > > > > >> later than next Friday. > > > > > > > > > > > >Has the ITA taken place? > > > > > > > > > > > > > > > > Not an ITA, but an ITS (CCed). I was unable close according to the > > > > > ITS schedule, and I will have to resume the work after then end of my > > > > > VAC (mid-January) > > > > > > > > This was nearly 2 months ago. At this point, I think that apollock > > > > and mgilbert might as well be considered MIA. > > > > > > Sure enough, upstream already is up to version 4.4.3b1, 26 January > > > 2022, and recent commits include CVE fixes. > > > > OK. I am resuming the work on this, and I'll upload it ASAP. > > > > I have just requested to move the isc-dhcp packaging repo to the debian/ > > namespace. > > Please note that there are now 2 upstream repos, if you wanna cherry > pick CVE fixes: > > https://github.com/isc-projects/dhcp > https://gitlab.isc.org/isc-projects/dhcp > > GitHub seems to be abandoned, while GitLab regularly sees commits and > is where I found the 4.4.3 beta. > > Tarballs are still here: > > https://downloads.isc.org/isc/dhcp/ To top it all, upstream has decided to retire this codebase by the end of this year: https://www.isc.org/blogs/dhcp-client-relay-eom/ This will have 2 impacts for Debian: 1) Whatever outstanding bugs Debian has will have to be solved and applicable patches pushed upstream ASAP or closed as won't fix. 2) Debian will have to either agree with other distros on a common fork to maintain or find a new DHCP client to replace the ISC client. Martin-Éric
Bug#995189: RFH: isc-dhcp
On Mon, Feb 21, 2022 at 11:44 PM Santiago R.R. wrote: > > El 21/02/22 a las 15:19, Martin-Éric Racine escribió: > > On Mon, Feb 21, 2022 at 2:18 PM Martin-Éric Racine > > wrote: > > > > > > On Thu, Jan 6, 2022 at 8:40 PM Santiago R.R. > > > wrote: > > > > On January 6, 2022 4:49:49 AM GMT-05:00, "Martin-Éric Racine" > > > > wrote: > > > > >Hello again, > > > > > > > > > >ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón > > > > >(santiag...@riseup.net) kirjoitti: > > > > >> El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > > > > >> > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > > > > >> > (santiag...@riseup.net) kirjoitti: > > > > >> > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > > > >> > > > Package: wnpp > > > > >> > > > Severity: normal > > > > >> > > > X-Debbugs-Cc: debian-de...@lists.debian.org > > > > >> > > > Control: affects -1 src:isc-dhcp > > > > >> > > > > > > > >> > > > -BEGIN PGP SIGNED MESSAGE- > > > > >> > > > Hash: SHA256 > > > > >> > > > > > > > >> > > > The ISC DHCP suite has a lenghty list of bug reports that have > > > > >> > > > been left unattended. Some bugs date back to DHCP 3 or even > > > > >> > > > earlier. > > > > >> > > > > > > > >> > > > Additionally, recent upstream releases are still unpackaged. > > > > >> > > > One release came out well ahead of the Bullseye freeze, a bug > > > > >> > > > report requesting its packaging was filed, but it remains > > > > >> > > > unanswered. > > > > >> > > > > > > > >> > > > Leaving a package with a priority Important in such utter > > > > >> > > > state of neglect is unacceptable. > > > > >> > > > > > > > >> > > > At this point, it has become clear that, at the very least, > > > > >> > > > its maintainers need help, hence why I filed this WNPP bug. > > > > >> > > > > > > >> > > Indeed. I am willing to spend some cycles to help maintaining > > > > >> > > it. I > > > > >> > > requested access to the ISC DHCP packaging team in salsa ~a > > > > >> > > couple of > > > > >> > > weeks ago, but I hasn't been answered yet (mgilbert is its only > > > > >> > > member). > > > > >> > > It was on my ToDo list to ping the maintainers (in CC). > > > > >> > > > > > >> > Has any progress taken place on this? > > > > >> > > > > >> I've started doing some work at > > > > >> https://salsa.debian.org/santiago/isc-dhcp/ > > > > >> > > > > >> I still didn't get any answer from current maintainers (keeping them > > > > >> in > > > > >> CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > > > > >> later than next Friday. > > > > > > > > > >Has the ITA taken place? > > > > > > > > > > > > > Not an ITA, but an ITS (CCed). I was unable close according to the ITS > > > > schedule, and I will have to resume the work after then end of my VAC > > > > (mid-January) > > > > > > This was nearly 2 months ago. At this point, I think that apollock > > > and mgilbert might as well be considered MIA. > > > > Sure enough, upstream already is up to version 4.4.3b1, 26 January > > 2022, and recent commits include CVE fixes. > > OK. I am resuming the work on this, and I'll upload it ASAP. > > I have just requested to move the isc-dhcp packaging repo to the debian/ > namespace. Please note that there are now 2 upstream repos, if you wanna cherry pick CVE fixes: https://github.com/isc-projects/dhcp https://gitlab.isc.org/isc-projects/dhcp GitHub seems to be abandoned, while GitLab regularly sees commits and is where I found the 4.4.3 beta. Tarballs are still here: https://downloads.isc.org/isc/dhcp/ Martin-Éric
Bug#1000662: Bug#995189: RFH: isc-dhcp
El 21/02/22 a las 15:19, Martin-Éric Racine escribió: > On Mon, Feb 21, 2022 at 2:18 PM Martin-Éric Racine > wrote: > > > > On Thu, Jan 6, 2022 at 8:40 PM Santiago R.R. wrote: > > > On January 6, 2022 4:49:49 AM GMT-05:00, "Martin-Éric Racine" > > > wrote: > > > >Hello again, > > > > > > > >ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón > > > >(santiag...@riseup.net) kirjoitti: > > > >> El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > > > >> > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > > > >> > (santiag...@riseup.net) kirjoitti: > > > >> > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > > >> > > > Package: wnpp > > > >> > > > Severity: normal > > > >> > > > X-Debbugs-Cc: debian-de...@lists.debian.org > > > >> > > > Control: affects -1 src:isc-dhcp > > > >> > > > > > > >> > > > -BEGIN PGP SIGNED MESSAGE- > > > >> > > > Hash: SHA256 > > > >> > > > > > > >> > > > The ISC DHCP suite has a lenghty list of bug reports that have > > > >> > > > been left unattended. Some bugs date back to DHCP 3 or even > > > >> > > > earlier. > > > >> > > > > > > >> > > > Additionally, recent upstream releases are still unpackaged. One > > > >> > > > release came out well ahead of the Bullseye freeze, a bug report > > > >> > > > requesting its packaging was filed, but it remains unanswered. > > > >> > > > > > > >> > > > Leaving a package with a priority Important in such utter state > > > >> > > > of neglect is unacceptable. > > > >> > > > > > > >> > > > At this point, it has become clear that, at the very least, its > > > >> > > > maintainers need help, hence why I filed this WNPP bug. > > > >> > > > > > >> > > Indeed. I am willing to spend some cycles to help maintaining it. I > > > >> > > requested access to the ISC DHCP packaging team in salsa ~a couple > > > >> > > of > > > >> > > weeks ago, but I hasn't been answered yet (mgilbert is its only > > > >> > > member). > > > >> > > It was on my ToDo list to ping the maintainers (in CC). > > > >> > > > > >> > Has any progress taken place on this? > > > >> > > > >> I've started doing some work at > > > >> https://salsa.debian.org/santiago/isc-dhcp/ > > > >> > > > >> I still didn't get any answer from current maintainers (keeping them in > > > >> CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > > > >> later than next Friday. > > > > > > > >Has the ITA taken place? > > > > > > > > > > Not an ITA, but an ITS (CCed). I was unable close according to the ITS > > > schedule, and I will have to resume the work after then end of my VAC > > > (mid-January) > > > > This was nearly 2 months ago. At this point, I think that apollock > > and mgilbert might as well be considered MIA. > > Sure enough, upstream already is up to version 4.4.3b1, 26 January > 2022, and recent commits include CVE fixes. OK. I am resuming the work on this, and I'll upload it ASAP. I have just requested to move the isc-dhcp packaging repo to the debian/ namespace. Cheers, -- Santiago signature.asc Description: PGP signature
Bug#995189: RFH: isc-dhcp
On Mon, Feb 21, 2022 at 2:18 PM Martin-Éric Racine wrote: > > On Thu, Jan 6, 2022 at 8:40 PM Santiago R.R. wrote: > > On January 6, 2022 4:49:49 AM GMT-05:00, "Martin-Éric Racine" > > wrote: > > >Hello again, > > > > > >ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón > > >(santiag...@riseup.net) kirjoitti: > > >> El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > > >> > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > > >> > (santiag...@riseup.net) kirjoitti: > > >> > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > >> > > > Package: wnpp > > >> > > > Severity: normal > > >> > > > X-Debbugs-Cc: debian-de...@lists.debian.org > > >> > > > Control: affects -1 src:isc-dhcp > > >> > > > > > >> > > > -BEGIN PGP SIGNED MESSAGE- > > >> > > > Hash: SHA256 > > >> > > > > > >> > > > The ISC DHCP suite has a lenghty list of bug reports that have > > >> > > > been left unattended. Some bugs date back to DHCP 3 or even > > >> > > > earlier. > > >> > > > > > >> > > > Additionally, recent upstream releases are still unpackaged. One > > >> > > > release came out well ahead of the Bullseye freeze, a bug report > > >> > > > requesting its packaging was filed, but it remains unanswered. > > >> > > > > > >> > > > Leaving a package with a priority Important in such utter state of > > >> > > > neglect is unacceptable. > > >> > > > > > >> > > > At this point, it has become clear that, at the very least, its > > >> > > > maintainers need help, hence why I filed this WNPP bug. > > >> > > > > >> > > Indeed. I am willing to spend some cycles to help maintaining it. I > > >> > > requested access to the ISC DHCP packaging team in salsa ~a couple of > > >> > > weeks ago, but I hasn't been answered yet (mgilbert is its only > > >> > > member). > > >> > > It was on my ToDo list to ping the maintainers (in CC). > > >> > > > >> > Has any progress taken place on this? > > >> > > >> I've started doing some work at > > >> https://salsa.debian.org/santiago/isc-dhcp/ > > >> > > >> I still didn't get any answer from current maintainers (keeping them in > > >> CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > > >> later than next Friday. > > > > > >Has the ITA taken place? > > > > > > > Not an ITA, but an ITS (CCed). I was unable close according to the ITS > > schedule, and I will have to resume the work after then end of my VAC > > (mid-January) > > This was nearly 2 months ago. At this point, I think that apollock > and mgilbert might as well be considered MIA. Sure enough, upstream already is up to version 4.4.3b1, 26 January 2022, and recent commits include CVE fixes. Martin-Éric
Bug#1000662: Bug#995189: RFH: isc-dhcp
On Thu, Jan 6, 2022 at 8:40 PM Santiago R.R. wrote: > On January 6, 2022 4:49:49 AM GMT-05:00, "Martin-Éric Racine" > wrote: > >Hello again, > > > >ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón > >(santiag...@riseup.net) kirjoitti: > >> El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > >> > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > >> > (santiag...@riseup.net) kirjoitti: > >> > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > >> > > > Package: wnpp > >> > > > Severity: normal > >> > > > X-Debbugs-Cc: debian-de...@lists.debian.org > >> > > > Control: affects -1 src:isc-dhcp > >> > > > > >> > > > -BEGIN PGP SIGNED MESSAGE- > >> > > > Hash: SHA256 > >> > > > > >> > > > The ISC DHCP suite has a lenghty list of bug reports that have been > >> > > > left unattended. Some bugs date back to DHCP 3 or even earlier. > >> > > > > >> > > > Additionally, recent upstream releases are still unpackaged. One > >> > > > release came out well ahead of the Bullseye freeze, a bug report > >> > > > requesting its packaging was filed, but it remains unanswered. > >> > > > > >> > > > Leaving a package with a priority Important in such utter state of > >> > > > neglect is unacceptable. > >> > > > > >> > > > At this point, it has become clear that, at the very least, its > >> > > > maintainers need help, hence why I filed this WNPP bug. > >> > > > >> > > Indeed. I am willing to spend some cycles to help maintaining it. I > >> > > requested access to the ISC DHCP packaging team in salsa ~a couple of > >> > > weeks ago, but I hasn't been answered yet (mgilbert is its only > >> > > member). > >> > > It was on my ToDo list to ping the maintainers (in CC). > >> > > >> > Has any progress taken place on this? > >> > >> I've started doing some work at https://salsa.debian.org/santiago/isc-dhcp/ > >> > >> I still didn't get any answer from current maintainers (keeping them in > >> CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > >> later than next Friday. > > > >Has the ITA taken place? > > > > Not an ITA, but an ITS (CCed). I was unable close according to the ITS > schedule, and I will have to resume the work after then end of my VAC > (mid-January) This was nearly 2 months ago. At this point, I think that apollock and mgilbert might as well be considered MIA. Martin-Éric
Bug#1000662: Bug#995189: RFH: isc-dhcp
On January 6, 2022 4:49:49 AM GMT-05:00, "Martin-Éric Racine" wrote: >Hello again, > >ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón >(santiag...@riseup.net) kirjoitti: >> El 07/11/21 a las 13:54, Martin-Éric Racine escribió: >> > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón >> > (santiag...@riseup.net) kirjoitti: >> > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: >> > > > Package: wnpp >> > > > Severity: normal >> > > > X-Debbugs-Cc: debian-de...@lists.debian.org >> > > > Control: affects -1 src:isc-dhcp >> > > > >> > > > -BEGIN PGP SIGNED MESSAGE- >> > > > Hash: SHA256 >> > > > >> > > > The ISC DHCP suite has a lenghty list of bug reports that have been >> > > > left unattended. Some bugs date back to DHCP 3 or even earlier. >> > > > >> > > > Additionally, recent upstream releases are still unpackaged. One >> > > > release came out well ahead of the Bullseye freeze, a bug report >> > > > requesting its packaging was filed, but it remains unanswered. >> > > > >> > > > Leaving a package with a priority Important in such utter state of >> > > > neglect is unacceptable. >> > > > >> > > > At this point, it has become clear that, at the very least, its >> > > > maintainers need help, hence why I filed this WNPP bug. >> > > >> > > Indeed. I am willing to spend some cycles to help maintaining it. I >> > > requested access to the ISC DHCP packaging team in salsa ~a couple of >> > > weeks ago, but I hasn't been answered yet (mgilbert is its only member). >> > > It was on my ToDo list to ping the maintainers (in CC). >> > >> > Has any progress taken place on this? >> >> I've started doing some work at https://salsa.debian.org/santiago/isc-dhcp/ >> >> I still didn't get any answer from current maintainers (keeping them in >> CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no >> later than next Friday. > >Has the ITA taken place? > Not an ITA, but an ITS (CCed). I was unable close according to the ITS schedule, and I will have to resume the work after then end of my VAC (mid-January) Cheers, -- S -- Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.
Bug#995189: RFH: isc-dhcp
Hello again, ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón (santiag...@riseup.net) kirjoitti: > El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > > (santiag...@riseup.net) kirjoitti: > > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > > > Package: wnpp > > > > Severity: normal > > > > X-Debbugs-Cc: debian-de...@lists.debian.org > > > > Control: affects -1 src:isc-dhcp > > > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA256 > > > > > > > > The ISC DHCP suite has a lenghty list of bug reports that have been > > > > left unattended. Some bugs date back to DHCP 3 or even earlier. > > > > > > > > Additionally, recent upstream releases are still unpackaged. One > > > > release came out well ahead of the Bullseye freeze, a bug report > > > > requesting its packaging was filed, but it remains unanswered. > > > > > > > > Leaving a package with a priority Important in such utter state of > > > > neglect is unacceptable. > > > > > > > > At this point, it has become clear that, at the very least, its > > > > maintainers need help, hence why I filed this WNPP bug. > > > > > > Indeed. I am willing to spend some cycles to help maintaining it. I > > > requested access to the ISC DHCP packaging team in salsa ~a couple of > > > weeks ago, but I hasn't been answered yet (mgilbert is its only member). > > > It was on my ToDo list to ping the maintainers (in CC). > > > > Has any progress taken place on this? > > I've started doing some work at https://salsa.debian.org/santiago/isc-dhcp/ > > I still didn't get any answer from current maintainers (keeping them in > CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > later than next Friday. Has the ITA taken place? Cheers! Martin-Éric
Bug#995189: RFH: isc-dhcp
ke 24. marrask. 2021 klo 16.20 Santiago Ruano Rincón (santiag...@riseup.net) kirjoitti: > I've started doing some work at https://salsa.debian.org/santiago/isc-dhcp/ > > I still didn't get any answer from current maintainers (keeping them in > CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no > later than next Friday. Btw, you might wanna look at the changes that Ubuntu made as well, in case they have already fixed some pending issues. https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/isc-dhcp/4.4.1-2.3ubuntu1/isc-dhcp_4.4.1-2.3ubuntu1.dsc This one is obviously against what's currently in unstable. Martin-Éric
Bug#995189: RFH: isc-dhcp
El 07/11/21 a las 13:54, Martin-Éric Racine escribió: > Howdy! Hi! > > ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón > (santiag...@riseup.net) kirjoitti: > > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > > Package: wnpp > > > Severity: normal > > > X-Debbugs-Cc: debian-de...@lists.debian.org > > > Control: affects -1 src:isc-dhcp > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > The ISC DHCP suite has a lenghty list of bug reports that have been left > > > unattended. Some bugs date back to DHCP 3 or even earlier. > > > > > > Additionally, recent upstream releases are still unpackaged. One release > > > came out well ahead of the Bullseye freeze, a bug report requesting its > > > packaging was filed, but it remains unanswered. > > > > > > Leaving a package with a priority Important in such utter state of > > > neglect is unacceptable. > > > > > > At this point, it has become clear that, at the very least, its > > > maintainers need help, hence why I filed this WNPP bug. > > > > Indeed. I am willing to spend some cycles to help maintaining it. I > > requested access to the ISC DHCP packaging team in salsa ~a couple of > > weeks ago, but I hasn't been answered yet (mgilbert is its only member). > > It was on my ToDo list to ping the maintainers (in CC). > > Has any progress taken place on this? > > Martin-Éric I've started doing some work at https://salsa.debian.org/santiago/isc-dhcp/ I still didn't get any answer from current maintainers (keeping them in CC), so I plan to retitle this bug as an ITS bug soon. Hopefully no later than next Friday. Cheers, -- Santiago signature.asc Description: PGP signature
Bug#995189: RFH: isc-dhcp
Howdy! ma 27. syysk. 2021 klo 21.44 Santiago Ruano Rincón (santiag...@riseup.net) kirjoitti: > El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > > Package: wnpp > > Severity: normal > > X-Debbugs-Cc: debian-de...@lists.debian.org > > Control: affects -1 src:isc-dhcp > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > The ISC DHCP suite has a lenghty list of bug reports that have been left > > unattended. Some bugs date back to DHCP 3 or even earlier. > > > > Additionally, recent upstream releases are still unpackaged. One release > > came out well ahead of the Bullseye freeze, a bug report requesting its > > packaging was filed, but it remains unanswered. > > > > Leaving a package with a priority Important in such utter state of neglect > > is unacceptable. > > > > At this point, it has become clear that, at the very least, its maintainers > > need help, hence why I filed this WNPP bug. > > Indeed. I am willing to spend some cycles to help maintaining it. I > requested access to the ISC DHCP packaging team in salsa ~a couple of > weeks ago, but I hasn't been answered yet (mgilbert is its only member). > It was on my ToDo list to ping the maintainers (in CC). Has any progress taken place on this? Martin-Éric
Bug#995189: RFH: isc-dhcp
El 27/09/21 a las 20:25, Martin-Éric Racine escribió: > Package: wnpp > Severity: normal > X-Debbugs-Cc: debian-de...@lists.debian.org > Control: affects -1 src:isc-dhcp > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The ISC DHCP suite has a lenghty list of bug reports that have been left > unattended. Some bugs date back to DHCP 3 or even earlier. > > Additionally, recent upstream releases are still unpackaged. One release came > out well ahead of the Bullseye freeze, a bug report requesting its packaging > was filed, but it remains unanswered. > > Leaving a package with a priority Important in such utter state of neglect is > unacceptable. > > At this point, it has become clear that, at the very least, its maintainers > need help, hence why I filed this WNPP bug. Indeed. I am willing to spend some cycles to help maintaining it. I requested access to the ISC DHCP packaging team in salsa ~a couple of weeks ago, but I hasn't been answered yet (mgilbert is its only member). It was on my ToDo list to ping the maintainers (in CC). Cheers, -- Santiago signature.asc Description: PGP signature
Bug#995189: RFH: isc-dhcp
Package: wnpp Severity: normal X-Debbugs-Cc: debian-de...@lists.debian.org Control: affects -1 src:isc-dhcp -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The ISC DHCP suite has a lenghty list of bug reports that have been left unattended. Some bugs date back to DHCP 3 or even earlier. Additionally, recent upstream releases are still unpackaged. One release came out well ahead of the Bullseye freeze, a bug report requesting its packaging was filed, but it remains unanswered. Leaving a package with a priority Important in such utter state of neglect is unacceptable. At this point, it has become clear that, at the very least, its maintainers need help, hence why I filed this WNPP bug. - -- Martin-Éric -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmFR/noACgkQrh+Cd8S0 17apRA/9EnsfZnMsWBz07360Z8fqdoZWteKo3Weqfa7lhfVXqHaaWKR1k83uY3gO DEP+NGdDqMs5LVhQ4eDvEeMze2utCx52C2GFHebksI1QyaGruj9PSEu0j5CIBlKu v/fXdk9BXk3oQ4bJoKM8HBifNVx/ICb1X/4wdr78dy4ZYQLB+XLkbQ5DGn/UJ4mr VQctq/uxjFFY1zD+C5Mu7jG/X8eEbSXcshtMkxcoO3GW0c/Bmmy7Rm2exs1zHOkX fAiULeThKPJkpYgbiw6+iPZiJqWeeoDtXo8gInuw8riP3sua9PxhEwKnZBEcACJ3 BAT5ethXxAhC5Ecd+pzuqzlTrP9FYDqPyie3If0A9XK1sDPsnnn5yERWeuAn8L2E 7tZ5BAuBCEskQ+Z9Q1MqgK8/yeabzZRzmd2VCy+FXMfENjhDeGm1YefPSD80mebG UGVbN1MC9274pv6oomPkM6fQidIcbUIZDlBj2qJOxFWgXuv3jcnzWs4+XV9VssiD s/B5+YC9XvItCpZKjAUBaXDUX/hzPqFoseRygRPChxgrzyvP7ChWSz1JY9G73EYg ITe7KHQ9wqAMPJYmUp0ZmcACn9tCWH/xSt99KLrnYURPxNHcYpG8+Pwr5r9swJ50 fjkEyEZWCNUu6u8uUvSx5sPrc29aIpuk+QXeBJIsAB24roy8ONo= =5hUD -END PGP SIGNATURE-
