Currently, check-security-support informs the user about the security
support status of the debian release currently running in the host.
However, it may be helpful to also notify the user when there would be
changes in the security support after upgrading to the next release.

This is the case now for isc-dhcp, that has been marked as non-supported
since trixie.  From a user PoV, it would make sense to get an early
warning about the end of security support.  And to raise awareness that
it is needed to look for alternative packages.

I like the idea and am wondering how to best implement this: right after a
release (eg think in 3 months when trixie hopefully will be release) it
doesnt make sense to display the status for forky. But when does it make sense?
Or should this require running check-support-status manually with some
option?

El 22/06/25 a las 08:55, Holger Levsen escribió:

From my POV, the earlier the better. But yeah, probably just after
release is too much. I'd say that if there are packages that we know
won't be supported, users should be warned no later than one year before
the expected release date of release+1.

And for oldstable -> stable upgrade, that should be ASAP.

If this requires manual action, my gut feeling tells me that the chances
that people use it are very low.

What do you think?

while I share the gut feeling mentioned above I also don't think we
should spam everybody with potential issues in a future release :/

So, atm I think I/we need to think further about this.

:)