Differences between revisions 1 and 31 (spanning 30 versions)
Revision 1 as of 2006-05-11 07:34:30
Size: 4557
Editor: MikeOConnor
Comment:
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 1: Line 1:
= Status of Debian testing = #language en
~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[es/Status/Testing|español]]- [[fr/Status/Testing|Français]] - [[it/Status/Testing|Italiano]] - [[sv/Status/Testing|Svenska]] -~
----
Line 3: Line 5:
The [wiki:DebianTesting Testing] release of ["Debian"] currently codenamed [wiki:DebianEtch Etch].
You can read more about available versions of Debian at DebianReleases.
Line 6: Line 6:
== When Will Etch Release? == == Current Issues Affecting Testing ==
Line 8: Line 8:
Currently there is not a planned date of release for [wiki:DebianEtch Etch]. '''Please note that this page is not updated regularly.'''
Line 10: Line 10:
The lastest status report from the ReleaseTeam can be found here:
 * http://lists.debian.org/debian-devel-announce/2006/05/msg00000.html
See also the [[https://lists.debian.org/debian-testing|debian-testing mailing list archive]].

== Workarounds for Current Problems ==

=== Problem-Description (date of occurrence) ===

(currently none)
Line 15: Line 21:
Refer to the [wiki:Status/Stable Status of Stable] page for a list of current ["DebianSecurityAdvisories"] From the [[https://www.debian.org/security/faq#testing|Debian Security FAQ]]:
Line 17: Line 23:
== Current Issues Affecting Testing == {{{#!wiki debian
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.
}}}
Line 19: Line 27:

=== Broken xdm ===

The xdm package snuck into testing ahead of the rest of the xorg 6.9->7.0 trasition, and it is missing a pre-depends on x11-common 7.0. As a result it is looking for /usr/bin/X (the xorg R7 location) instead of /usr/X11R6/bin/X (the xorg R6 location).

If you are experiencing this bug, it is recommended that you either downgrade xdm to an older version, switch to a different DisplayManager, or just use startx. If you are lucky, and older version of xdm might be in /var/cache/apt/archives, if not, one can be found on http://snapshot.debian.net

This bug is being tracked here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365134

See also:
 * The package page for xdm: http://packages.debian.org/xdm
 * The QA page for xdm: http://qa.debian.org/xdm
 * The bug tracking page from xdm: http://bugs.debian.org/xdm

=== gnome-session dies immediately ===

This has been reported by several users who have recently updated libxklavier10 who are running xserver-xorg 6.9

please refer to bugs [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365079 #365079], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364838 #364838] and [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364830 #364830].

The workaround is to downgrade libxklavier10 to 2.2-1

=== locales fails to postinst/configure ===

This was encountered upon upgrading/dist-upgrading {{{testing}}}. See [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363644 #363644]. One user solved it by upgrading {{{debconf}}} to {{{1.5.0}}}, purging {{{locales}}}, removing {{{/etc/environment}}} and {{{/etc/default/locales}}} (of course, you should rename them, rather than actually delete them), and finally reinstalling {{{locales}}}. Whether the bug is actually in {{{locales}}} or {{{debconf}}} is as yet unknown.

=== apt key problems ===

'''I believe you can now resolve this for official Debian repositories by simply installing the debian-archive-keyring package.'''

Here is something that is going on:
an apt update now gives: W: GPG error: http://http.us.debian.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F

I had a pubkey installed for testing yesterday. Now what? --JoshuaRodman

This email from JoeyHess might be relevant: http://lists.debian.org/debian-user/2006/01/msg00291.html

If you encounter following kind of warning (when running apt-get update) :

W: GPG error: ftp://ftp.belnet.be testing Release: The following signatures couldn't be veri
ailable: NO_PUBKEY 010908312D230C5F

Follow the procedure below :

# open console terminal, type su and root password
# gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 2D230C5F
# gpg --armor --export 2D230C5F | apt-key add -
# apt-get update

If you encounter following kind of warning (when running apt-get update) :

W: GPG error: http://secure-testing.debian.net etch/security-updates Release: The following signatures couldn't
be verified because the public key is not available: NO_PUBKEY 946AA6E18722E71E
W: You may want to run apt-get update to correct these problems

Follow the procedure below :

# Open console terminal, type su and root password
# wget http://secure-testing.debian.net/ziyi-2005-7.asc -O - | apt-key add -
# apt-get update

If you have other sources in sources.list file, you can get the key for them in a similar manner, just look for the key number in the error message. --JanJansen

  Okay, although I don't like the release key being in root's keyring. But what I can't find anywhere is information on how I (as user, not a knoweledgable Debian Developer), can validate or trust the release key. --JoshuaRodman
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.
  
See the [[SecurityManagement|security page]] for information about keeping your Debian install secure.
Line 86: Line 32:
Line 87: Line 34:
 * [wiki:Status The Status page]
 * [wiki:Status/Stable Status of Stable]
 * [wiki:Status/Unstable Status of Unstable]
 * [[Status|The Status page]]
 * [[Status/Stable|Status of Stable]]
 * [[Status/Unstable|Status of Unstable]]

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.