.. _ch-information: Issues to be aware of for |RELEASENAME| |DRAFT| ========================================================================== Sometimes, changes introduced in a new release have side-effects we cannot reasonably avoid, or they expose bugs somewhere else. This section documents issues we are aware of. Please also read the errata, the relevant packages' documentation, bug reports, and other information mentioned in :ref:`morereading`. .. _upgrade-specific-issues: Things to be aware of while upgrading to |RELEASENAME| ---------------------------------------------------------------------------- This section covers items related to the upgrade from |OLDRELEASENAME| to |RELEASENAME|. .. _issue-1: .. only:: fixme Something ~~~~~~~~~~~~~~~~~~ Text .. _issue-2: .. only:: fixme Something else ~~~~~~~~~~~~~~~~~~ Text .. _before-first-reboot: Things to do before rebooting ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When ``apt full-upgrade`` has finished, the "formal" upgrade is complete. For the upgrade to |RELEASENAME|, there are no special actions needed before performing a reboot. .. only:: fixme When ``apt full-upgrade`` has finished, the "formal" upgrade is complete, but there are some other things that should be taken care of *before* the next reboot. :: add list of items here .. _not-upgrade-only: Items not limited to the upgrade process -------------------------------------------------------------------------------- .. _limited-security-support: Limitations in security support ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There are some packages where Debian cannot promise to provide minimal backports for security issues. These are covered in the following subsections. .. note:: The package **debian-security-support** helps to track the security support status of installed packages. .. _browser-security: Security status of web browsers and their rendering engines ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Debian |RELEASE| includes several browser engines which are affected by a steady stream of security vulnerabilities. The high rate of vulnerabilities and partial lack of upstream support in the form of long term branches make it very difficult to support these browsers and engines with backported security fixes. Additionally, library interdependencies make it extremely difficult to update to newer upstream releases. Applications using the **webkit2gtk** source package (e.g. **epiphany**) are covered by security support, but applications using qtwebengine (source packages **qtwebengine-opensource-src** and **qt6-webengine**) are not. For general web browser use we recommend Firefox or Chromium. They will be kept up-to-date by rebuilding the current ESR releases for stable. The same strategy will be applied for Thunderbird. Once a release becomes ``oldstable``, officially supported browsers may not continue to receive updates for the standard period of coverage. For example, Chromium will only receive 6 months of security support in ``oldstable`` rather than the typical 12 months. .. _golang-static-linking: Go- and Rust-based packages ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The Debian infrastructure currently has problems with rebuilding packages of types that systematically use static linking. With the growth of the Go and Rust ecosystems it means that these packages will be covered by limited security support until the infrastructure is improved to deal with them maintainably. In most cases if updates are warranted for Go or Rust development libraries, they will only be released via regular point releases. .. _issue-3: .. only:: fixme Something ~~~~~~~~~~~~~~~~~~ Text .. _issue-4: .. only:: fixme Something else ~~~~~~~~~~~~~~~~~~ Text .. _obsolescense-and-deprecation: Obsolescence and deprecation -------------------------------------------------------- .. _noteworthy-obsolete-packages: Noteworthy obsolete packages ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following is a list of known and noteworthy obsolete packages (see :ref:`obsolete` for a description). The list of obsolete packages includes: .. only:: fixme - The **foo** package has been removed from |RELEASENAME|. The upstream developer suggests using **bar** instead. .. _deprecated-components: Deprecated components for |RELEASENAME| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ With the next release of Debian |NEXTRELEASE| (codenamed |NEXTRELEASENAME|) some features will be deprecated. Users will need to migrate to other alternatives to prevent trouble when updating to Debian |NEXTRELEASE|. This includes the following features: .. only:: fixme - The **foo** package will be removed from |NEXTRELEASENAME|. The upstream developer suggests migrating to **bar** instead. .. only:: fixme No-longer-supported hardware ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For a number of \`arch`-based devices that were supported in |OLDRELEASENAME|, it is no longer viable for Debian to build the required ``Linux`` kernel, due to hardware limitations. The unsupported devices are: - foo Users of these platforms who wish to upgrade to |RELEASENAME| nevertheless should keep the |OLDRELEASENAME| APT sources enabled. Before upgrading they should add an APT preferences file containing: .. parsed-literal:: Package: linux-image-marvell Pin: release n= |OLDRELEASENAME| Pin-Priority: 900 The security support for this configuration will only last until |OLDRELEASENAME|'s End Of Life. .. _rc-bugs: Known severe bugs --------------------------------------------------- Although Debian releases when it's ready, that unfortunately doesn't mean there are no known bugs. As part of the release process all the bugs of severity serious or higher are actively tracked by the Release Team, so an `overview of those bugs `__ that were tagged to be ignored in the last part of releasing |RELEASENAME| can be found in the `Debian Bug Tracking System `__. The following bugs were affecting |RELEASENAME| at the time of the release and worth mentioning in this document: .. csv-table:: :header: "Bug number", "Package (source or binary)", "Description" :widths: 13, 22, 60 "`1032240`_", "**akonadi-backend-mysql**", "akonadi server not robust against mysql upgrades" .. _1032240: https://bugs.debian.org/1032240