Paul Gevers wrote:
> How about (dropping the package specific section, and just merge it into
> upgrade items):
> 5.1. Upgrade specific items for bullseye
> 5.2. Items not limited to the upgrade process
> * Limitations in security support
> * Gnome accessibility issue
> * password-less rescue mode
> 5.3. Obsolescence and deprecation
> * Noteworthy obsolete packages
> * Deprecated components for bullseye
That's just about what I was thinking, if I'd taken the trouble to
look up the section numbers.
> Now I'm going over it, the Python2 is probably also not in the right
> section. I think it warrants to be mentioned under "Noteworthy obsolete
> packages" (section of 5.1) as the Python2 deprecation has resulted in *a
> lot* of Python2 packages to have been removed.
If we move it then it probably also needs... maybe just an extra line:
Python 2 is already beyond its End Of Life, and will receive no
security updates. It is not supported for running applications,
+ and packages relying on it have either been switched to Python 3 or removed.
However, Debian bullseye does still include a version of Python 2.7,
> Paul
> PS: on the one hand it feels more natural to have deprecate before
> obsolete, but on the other hand I guess it's more important to learn
> about obsolete packages, so that goes first?
I like having "obsolete" first; maybe that's because I'm hoping to
get a py2less system this summer but I'm still treating the
deprecation of unmerged /usr as just a cloud on the horizon.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
