Differences between revisions 21 and 22
Revision 21 as of 2019-07-08 04:09:04
Size: 2329
Editor: PaulWise
Comment: buster updates, use codename macro
Revision 22 as of 2019-07-08 04:14:27
Size: 2328
Editor: PaulWise
Comment: missed another rreference
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
Pin: release o=Debian,n=stretch-updates Pin: release o=Debian,n=buster-updates

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



Some packages from proposed-updates may also be made available via the stable-updates mechanism. This path will be used for updates which many users may wish to install on their systems before the next point release is made, such as updates to virus scanners and timezone data. All packages from stable-updates will be included in point releases.

For Debian 10.9 Buster, in order to use packages from buster-updates (aka stable-updates), you can add an entry to your sources.list. For example:

deb     http://deb.debian.org/debian buster-updates main
deb-src http://deb.debian.org/debian buster-updates main

For Debian 8 "Jessie", jessie-updates no longer exists as this suite no longer receives updates since 2018-05-17.

The next time you run apt update, the system will become aware of the packages in the (old)stable-updates section and will consider them when looking for packages to upgrade.

Note that if APT::Default-Release is set in your apt configuration, then, in order for automatic upgrades to work, some apt pinning needs to be added (see apt_preferences(5) for more information):

Package: *
Pin: release o=Debian,n=buster-updates
Pin-Priority: 990

When a new package is made available via (old)stable-updates, this will be announced on the debian-stable-announce mailing list.

stable-updates were introduced in DebianSqueeze, to replace DebianLenny's Volatile (see announcement).

See also