Bug#1030041: release-notes: offer deb22 format for apt sources
Adam D. Barratt wrote:
> That's no longer necessary for trixie:
>
> apt (3.0.2) unstable; urgency=medium
> [...]
> * Downgrade "modernize-sources" notice to audit
Looks like we can get away with keeping just the legacy-style sources
with a low-priority heads-up for trixie -
*Either* a note in old-stuff.rst where we're already talking about
sources.list:
#--------------------------------------------------------------------#
--- old-stuff.rst.orig 2025-06-10 06:45:17.078990639 +0100
+++ old-stuff.rst 2025-06-10 07:16:54.782447017 +0100
@@ -19,6 +19,15 @@
If you upgrade your system using a Debian mirror, it will automatically
be upgraded to the latest |OLDRELEASENAME| point release.
+.. note ::
+
+ This guide assumes that you are still using files in the legacy
+ one-line-style format, even though this is now being deprecated in
+ favor of the deb822-style format (see
+ :url-man-stable:`sources.list(5)`). The suggested approach is to
+ wait until after the upgrade to switch over using trixie's new
+ `apt modernize-sources` command.
+
.. _old-sources:
Checking your APT source-list files
#--------------------------------------------------------------------#
*Or* as a suggested piece of post-upgrade general maintenance:
#--------------------------------------------------------------------#
--- upgrading.rst.orig 2025-06-10 06:45:17.078990639 +0100
+++ upgrading.rst 2025-06-10 07:15:43.724157949 +0100
@@ -1168,6 +1168,13 @@
remove their configuration files. See also `Purging removed
packages <#purge-removed-packages>`__.
+- Although most documentation, including this guide, still works in
+ terms of the one-line-style format for `apt` `sources.list` files,
+ this legacy format is now being deprecated in favor of the
+ deb822-style format (see :url-man-stable:`sources.list(5)`). The
+ suggested approach is to wait until after the upgrade to switch
+ over using trixie's new `apt modernize-sources` command.
+
.. _purge-removed-packages:
Purging removed packages
#--------------------------------------------------------------------#
Someday we're going to need to write a set of Release Notes that
explain everything twice, first in the obsolete format and then again
in the long-winded format. Either that or we're going to need to
persuade absolutely everybody to switch over so that we only need the
latter. But at least we get to put off worrying about that for now.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Reply to: