Control: tags -1 + patch
Manny <debbug.www.debian....@sideload.33mail.com> wrote: > The Bookworm release notes instruct users to “upgrade” to the latest point > release of Bullseye prior to upgrading to Bookworm: > > > https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#upgrade-to-latest-point-release > > When following that link, the article says to do an “apt update” then > neglects to tell users to perform the upgrade. Moreover, we have "This should only be necessary in specific situations." in this chapter appendix A [1], while we recommend to upgrade to the latest point release of stable in 4.2.2 [2]. We should remove that phrase completely. A patch for above two issues is attached (against the bookworm branch; any such changing needs to be ported to master/trixie as well). Holger [1] https://www.debian.org/releases/stable/amd64/release-notes/ap-old-stuff.en.html#old-upgrade [2] https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#upgrade-to-latest-point-release -- Holger Wansing <hwans...@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
diff --git a/en/old-stuff.dbk b/en/old-stuff.dbk index b1c734e7..287c80c1 100644 --- a/en/old-stuff.dbk +++ b/en/old-stuff.dbk @@ -2,22 +2,21 @@ <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "https://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % languagedata SYSTEM "language.ent" > %languagedata; <!ENTITY % shareddata SYSTEM "../release-notes.ent" > %shareddata; ]> <appendix id="ap-old-stuff" lang="en"> <title>Managing your &oldreleasename; system before the upgrade</title> <para> This appendix contains information on how to make sure you can install or -upgrade &oldreleasename; packages before you upgrade to &releasename;. This should only be -necessary in specific situations. +upgrade &oldreleasename; packages before you upgrade to &releasename;. </para> <section id="old-upgrade"> <title>Upgrading your &oldreleasename; system</title> <para> Basically this is no different from any other upgrade of &oldreleasename; you've been doing. The only difference is that you first need to make sure your package list still contains references to &oldreleasename; as explained in <xref linkend="old-sources"/>. </para> <para> @@ -73,20 +72,31 @@ not. It is possible to downgrade packages, but that is not covered here. If you've made any changes, save the file and execute </para> <screen> # apt update </screen> <para> to refresh the package list. </para> </section> +<section id="upgrading-to-latest-oldstable"> +<title>Performing the upgrade to latest &oldreleasename; release</title> +<para> +To upgrade all packages to the state of the latest point release for +&oldreleasename;, do +</para> +<screen> +# apt full-upgrade +</screen> +</section> + <section id="old-config"> <title>Removing obsolete configuration files</title> <para> Before upgrading your system to &releasename;, it is recommended to remove old configuration files (such as <filename>*.dpkg-{new,old}</filename> files under <filename>/etc</filename>) from the system. </para> </section> </appendix>