Differences between revisions 29 and 30
Revision 29 as of 2019-09-02 09:42:50
Size: 3975
Comment: add example for apt-pinning to only get specific packages
Revision 30 as of 2021-08-14 22:43:48
Size: 3981
Editor: ?JonathanWiltshire
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
The same way {{{stable}}} is an alias for the current distribution ({{{buster}}}), {{{stable-proposed-updates}}} is a link to current stable distribution updates ({{{buster-proposed-updates}}}). Be consistent when you use them. The same way {{{stable}}} is an alias for the current distribution ({{{bullseye}}}), {{{stable-proposed-updates}}} is a link to current stable distribution updates ({{{bullseye-proposed-updates}}}). Be consistent when you use them.
Line 26: Line 26:
 * Add the repository (choose {{{stable}}} or {{{buster}}}. Only add the sections {{{contrib}}} and {{{non-free}}} if you have added them to stable already).  * Add the repository (choose {{{stable}}} or {{{bullseye}}}. Only add the sections {{{contrib}}} and {{{non-free}}} if you have added them to stable already).

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


Debian Releases > Stable Proposed Updates

Stable-proposed-updates is an apt repository that contains the files that are being prepared for the next Debian/Stable point release. (read more on https://www.debian.org/releases/proposed-updates)

Using stable-proposed-updates

Stability

Official statement : As mentioned above, packages in stable-proposed-updates aren't yet officially part of Debian Stable and one should not assume they have the same quality and stability (yet!). Those new versions of the packages needs to be reviewed (by the stable release manager) and tested (by some users) before entering stable.

Unofficial statement : However, the quality is usually very high (It should still be considered higher quality than Debian Testing, Backports... ) You are welcome to test those updates if you can recover minor problems (but don't test on production servers ;-).

Repository name

The same way stable is an alias for the current distribution (bullseye), stable-proposed-updates is a link to current stable distribution updates (bullseye-proposed-updates). Be consistent when you use them.

Using Synaptic

  • Open Synaptic
  • Go to the menu Settings > Repository

  • Click on "New"
  • Add the repository (choose stable or bullseye. Only add the sections contrib and non-free if you have added them to stable already).

    synaptics_stable-proposed-updates.png

Using sources.list

Alternatively you can :

  • Edit /etc/apt/sources.list as root.

  • Add this line:

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

As usually, run aptitude update and install the updates.

FAQ

stable + proposed-updates ?

*-proposed-updates isn't a standalone repository. You should have both stable and stable-proposed-updates repositories enabled. (*-proposed-updates only contains the subset of packages that are going to be updated).

Apt pinning for stable-proposed-updates

The apt pinning is by default the same level as stable. To only install certain packages from stable-proposed-updated, the apt-preferences first needs to decrease the default pin, then set a specific package pin:

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

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

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

What's planned for the next point release ?
You can have a look at :

See also