Hi Athos. Thanks for the information. I didn't realise ISC Kea had LTS versions vs short term stable versions. Of course it makes sense for youto stick with their LTS versions.
I hunted around to try and work out how I'd start a backporting discussion, but l got lost on their website and on GitLab where their code seems to be hosted. On GitHub I'd just raise a request in their Issues section, but I have no idea where or how to initiate such a request on GitLab... Perhaps I need your help on this, since I suspect you've dealt with them before? -- Jim Barber On Mon, 7 Sept 2026 at 23:14, Athos Ribeiro <[email protected]> wrote: > > On Sun, Sep 06, 2026 at 08:25:44PM +0800, Jim Barber wrote: > >Source: isc-kea > >Version: 2.6.3-1+deb13u1 > >Severity: wishlist > >X-Debbugs-Cc: [email protected] > > > >Dear Maintainer, > > > >ISC started their next round of stable releases of kea in June with > >version 3.2.0. > > > >Please consider upgrading from the 3.0.x series that you currently use > >in forky, sid, and trixie-backports to the new 3.2.x series. > > > >3.2.x contains a number of fixes; and for me personally, it fixes the > >VLAN issue that was reported in Debian bug 1061769 > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061769 > >Without this being fixed I'm stuck with using the deprecated > >isc-dhcp-server package. > > Hi Jim, > > As Paride suggested in #1061769, would you mind filing a bug upstream so > this can be fixed in 3.0.x? > > As we can see in https://www.isc.org/kea/, kea 3.0 is an LTS release, > supported until June 2028, while 3.2 is only supported until July 2027. > > If by the time we have a forky soft freeze date announced we also have a > new release (e.g. 3.3) with the same support length as 3.0 (i.e., June > 2028 or later), we can re-assess the idea of bumping the version of kea > in Debian. Until then, I'd personaly rather stick to the longer upstream > support version of the package. > > Would you like to start the backporting discussion with upstream or > should I go ahead and file that bug? > > -- > Athos Ribeiro
