Package: release-notes
Severity: normal
Tags: patch
The footnote in section 4.4.2 ("Updating the package list") was useful
for buster, but already unnecessary even for bullseye. Where the
stretch release notes had just:
4.4.2. Updating the package list
First the list of available packages for the new release needs to
be fetched. This is done by executing:
# apt-get update
buster switched from "apt-get" to "apt" and added
Note
Users of apt-secure may find issues when using aptitude or
apt-get. For apt-get, you can use apt-get update
--allow-releaseinfo-change.
This advice was necessary to deal with a new error message that libapt
produced when suite attributes had changed; but it was so unpopular
with people running (e.g.) build chroots that apt was fixed not to
give that error message in version 2.1.10 - see changelog:
* Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
That was in 2020, and went not only into bullseye but even a buster
point release, at which point we should have dropped this note.
(The note was strangely cobwebby from the start, since cryptographic
signature checking on downloaded packages has been standard since...
what, 2005? People following the documented dist-upgrade procedure
are necessarily users of apt-secure, but probably won't know that.)
Trivial patch attached. I'd hoped to do it as a merge request, but
git has defeated me yet again.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/source/upgrading.rst b/source/upgrading.rst
index c3204562..47fbd1d6 100644
--- a/source/upgrading.rst
+++ b/source/upgrading.rst
@@ -728,13 +728,6 @@ fetched. This is done by executing:
# apt update
-
-.. note::
-
- Users of apt-secure may find issues when using ``aptitude`` or
- ``apt-get``. For apt-get, you can use
- ``apt-get update --allow-releaseinfo-change``.
-
.. _sufficient-space:
Make sure you have sufficient space for the upgrade
