از آنجایی که زمان نسبتا زیادی بین دو نسخه پایدار دبیان فاصله می‌افتد، قبل از بروزرسانی کلی باید یادداشت انتشار آن را مطالعه کنید.

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.

با تمام تلاش‌های صورت گرفته، یک بروزرسانی کلی ممکن است همیشه خوب پیش نرود. نسخه‌های جدید نرم‌افزار ممکن است با نسخه‌های پیشین ناسازگار باشند (برای نمونه، رفتار پیش‌فرض آن‌ها یا قالب داده‌یشان ممکن است تغییر کند). برخی باگ‌ها ممکن است از دید فرآیند تست که همیشه قبل از انتشار دبیان صورت می‌گیرد، مخفی مانده باشند.

برای پیش‌بینی این مشکلات، می‌توانید بسته apt-listchanges را نصب کنید که احتمال بروز مشکلات در ابتدای فرآیند بروزرسانی کلی را بررسی می‌کند. این اطلاعات توسط نگهدارنده‌های بسته کامپایل شده و در فایل /usr/share/doc/package/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:

Depending on the severity of the bug, a new version of the package may be prepared specifically for a new revision of the stable release. When this happens, the fixed package is made available in the proposed-updates section of the Debian mirrors (see قسمت 6.1.2.3, “بروزرسانی‌های پیشنهادی” ). The corresponding entry can then be temporarily added to the sources.list file, and updated packages can be installed with apt or aptitude.

Sometimes the fixed package isn't available in this section yet because it is pending a validation by the Stable Release Managers. You can verify if that is the case on their web page. Packages listed there aren't available yet, but at least you know that the publication process is ongoing.

APT usually ensures a clean upgrade, pulling in new and updated dependencies, or removing conflicting packages. But even being such a great tool, it cannot cover all tasks users and administrators will face after an upgrade, because they require a human decision.

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

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