Translation(s): English - Español - Français - Italiano - Русский

Contents

  1. Introduction
  2. Using stable-proposed-updates
  3. APT pinning
  4. FAQ
  5. See also

Introduction

The stable-proposed-updates suite contains the packages proposed for inclusion in the next point release of Debian Stable. See https://www.debian.org/releases/proposed-updates for more information about how packages are added to this suite.

Stability

The official position is that packages in stable-proposed-updates are not yet officially part of Debian Stable and may not have the required quality and stability (yet!): you use them at your own risk. They may not yet have been reviewed by the stable release managers or tested, and there is no guarantee that are will become part of the official stable release.

The unofficial position is that in practice the quality is usually very high, typically better than Debian Testing or Backports. You are welcome to test those packages, but be prepared to fix minor issues: it is not recommended to use stable-proposed-updates on production servers.

Repository name

There is a stable-proposed-updates suite for each Debian codename. The term stable-proposed-updates is an alias for the version corresponding to stable. For example, when Debian Bookworm was stable, stable-proposed-updates was a link to bookworm-proposed-updates.

As always, it is recommended to use the name including the codename, rather than stable-proposed-updates or stable: these will point to a completely new place once a new stable is released and could lead to you installing incompatible packages.

Using stable-proposed-updates

Using APT

To add the trixie-proposed-updates suite to your debian.sources, simply add the suite to the existing list: 

Types: deb
URIs: http://deb.debian.org/debian
Suites: trixie trixie-security trixie-proposed-updates
Components: main
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

As usual, run apt update to make the packages available to APT.

Using sources.list

With the old /etc/apt/sources.list format add the line: 

   deb http://deb.debian.org/debian/ trixie-proposed-updates main

APT pinning

By default, apt will consider packages in stable-proposed-updates as having the same priority as stable. To only install certain packages from stable-proposed-updates, the apt_preferences(5) file should first decrease the default pin, then set a higher priority pin for each package you want: 

Package: *
Pin: release a=proposed-updates
Pin-Priority: 100

Package: fdroidserver
Pin: release a=proposed-updates
Pin-Priority: 500

Using Synaptic

FAQ

Do i use keep using stable repository after enabling stable-proposed-updates?

Yes, *-proposed-updates isn't a standalone repository, and only contains versions of packages that are going to be updated. You must have both the stable and stable-proposed-updates repositories enabled for a functioning system.

How do developers upload to stable-proposed-updates?

See developers-reference's Special case: uploads to the stable and oldstable distributions (particularly the part about filing a bug against release.debian.org to discuss your changes before uploading)

What packages will be in the next point release ?
You can have a look at :

See also