Differences between revisions 29 and 31 (spanning 2 versions)
Revision 29 as of 2020-05-18 12:18:05
Size: 1960
Comment: corrected info re: security for testing, updated answer from faq, made clear page not updated regularly
Revision 31 as of 2021-04-24 00:36:23
Size: 1927
Editor: PaulWise
Comment: drop section that requires maintainence, clarify existing paragraph to compensate for that, minor cleanups
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
See also the [[http://lists.debian.org/debian-testing|debian-testing mailing list archive]]. See also the [[https://lists.debian.org/debian-testing|debian-testing mailing list archive]].
Line 14: Line 14:
=== Problem-Description (date of occurance) === === Problem-Description (date of occurrence) ===
Line 21: Line 21:
From the [[http://www.debian.org/security/faq#testing|Debian Security FAQ]]: From the [[https://www.debian.org/security/faq#testing|Debian Security FAQ]]:
Line 27: Line 27:
There does exist a testing-security repository but it is empty. It is there so that people can have the line in their SourcesList to facilitate easily changing it to the next release name. To be clear, '''there are no security updates in this repository.''' There does exist a testing-security repository but it is empty. It is there so that people who intend to stay with <<DebianCodename(testing)>> after the release can have <<DebianCodename(testing)>>-security in their SourcesList so that they receive security updates after the release happens. To be clear, '''there are no security updates in this repository''' until '''after''' the release.
Line 29: Line 29:
   * deb h{{{}}}ttp://security.debian.org testing-security main contrib non-free
   * deb-src ht{{{}}}tp://security.debian.org testing-security main contrib non-free
Line 34: Line 31:
== Quick links ==
Line 35: Line 33:
== Quick links ==

Translation(s): English - español- Français - Italiano - Svenska


Current Issues Affecting Testing

Please note that this page is not updated regularly.

See also the debian-testing mailing list archive.

Workarounds for Current Problems

Problem-Description (date of occurrence)

(currently none)

Security

From the Debian Security FAQ:

Security for testing benefits from the security efforts of the entire project for unstable. However, there is a minimum two-day migration delay, and sometimes security fixes can be held up by transitions. The Security Team helps to move along those transitions holding back important security uploads, but this is not always possible and delays may occur. Especially in the months after a new stable release, when many new versions are uploaded to unstable, security fixes for testing may lag behind. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable.

There does exist a testing-security repository but it is empty. It is there so that people who intend to stay with bookworm after the release can have bookworm-security in their SourcesList so that they receive security updates after the release happens. To be clear, there are no security updates in this repository until after the release.

See the security page for information about keeping your Debian install secure.