Debian 各稳定版之间存在相当的差异，升级前应仔细阅读发布说明。

In this section, we will focus on upgrading a Bullseye system to Bookworm. This is a major operation on a system; as such, it is never 100% risk-free, and should not be attempted before all important data has been backed up.

Another good habit which makes the upgrade easier (and shorter) is to tidy your installed packages and keep only the ones that are really needed. Helpful tools to do that include aptitude, deborphan, debfoster, and apt-show-versions (see 第 6.2.7 节 “自动追踪已安装的软件包”). For example, you can use the following command, and then use aptitude's interactive mode to double check and fine-tune the scheduled removals:

# deborphan | xargs aptitude --schedule-only remove

Now for the upgrading itself. First, you need to change the /etc/apt/sources.list file to tell APT to get its packages from Bookworm instead of Bullseye. If the file only contains references to Stable rather than explicit codenames, the change isn't even required, since Stable always refers to the latest released version of Debian. In both cases, the database of available packages must be refreshed with the apt update command or the refresh button in synaptic (第 6.2.1 节 “初始化”).

Once these new package sources are registered, you should first do a minimal upgrade with apt upgrade et al. as described in 第 6.2.3 节 “系统升级”. By doing the upgrade in two steps, we ease the job of the package management tools and often ensure that we have the latest versions of those, which might have accumulated bugfixes and improvements required to complete the full distribution upgrade.

Once this first upgrade is done, it is time to handle the upgrade itself, either with apt full-upgrade, aptitude, or synaptic (第 6.7 节 “升级至下个稳定发行版”). You should carefully check the suggested actions before applying them: you might want to add suggested packages or deselect packages which are only recommended and known not to be useful. In any case, the frontend should come up with a scenario ending in a coherent and up-to-date Bookworm system. Then, all you need is to do is wait while the required packages are downloaded, answer the debconf questions and possibly those about locally modified configuration files, and sit back while APT does its magic.

尽管 Debian 管理者已经尽力做好份内的工作，主系统的升级仍可能不如想像中顺利。软件的新版本可能无法与旧版本兼容 (例如，可能改变缺省行为或数据格式)。同时，尽管在 Debian 发布前做了详尽的测试，还是有若干漏网的错误。

要解决这些问题，可以先安装 apt-listchanges 软件包，在软件包升级前先显示可能问题。由软件包维护者编辑的这些信息且置于 /usr/share/doc/软件包名/NEWS.Debian 文件名内，供用户参考。阅读这些文件 (可能经由 apt-listchanges) 应有助于规避意外。

You might sometimes find that the new version of a software doesn't work at all. This generally happens if the application isn't particularly popular and hasn't been tested enough; a last-minute update can also introduce regressions which are only found after the stable release. In both cases, the first thing to do is to have a look at the bug tracking system at https://bugs.debian.org/package, and check whether the problem has already been reported. If this is case, it will be also listed before the upgrade begins if you have apt-listbugs installed. If it hasn't, you should report it yourself with reportbug. If it is already known, the bug report and the associated messages are usually an excellent source of information related to the bug:

很严重的错误，将有特别的软件包供稳定版使用。在这种情况下，修订后的软件包位于 Debian 镜像站的 proposed-updates 区域 (见 第 6.1.2.3 节 “计划更新”)。对应的条目暂时加在 sources.list 文件内，可用 apt 或 aptitude 命令安装升级软件包。

修订软件包尚未被稳定版管理者认可时，就不会出现在此区块。用户必须自己动手认可它。虽然列在此的软件包尚未可得，但至少已知在审查中。

APT通常保证干净升级，下载新的和更新的依赖项，或移除冲突软件包。但是，即使是如此出色的工具，也不能涵盖用户和管理员在升级后将面对的所有任务，需要人工决策。

$ apt-show-versions | grep "No available version"

$ dpkg -l | grep ^ii | grep -i -E "(transition|dummy)"