5107
Comment: move wwer to DebianEtch
|
4248
fixed xdm transitioned to etch
|
Deletions are marked like this. | Additions are marked like this. |
Line 26: | Line 26: |
=== 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 |
Status of Debian testing
The [wiki:DebianTesting Testing] release of ["Debian"] currently codenamed [wiki:DebianEtch Etch]. You can read more about available versions of Debian at DebianReleases.
When Will Etch Release?
See DebianEtch for information about the etch release timeframe.
Security
Recently the Testing security team [http://lists.debian.org/debian-devel-announce/2006/05/msg00006.html announced] that the testing archive has been integrated with http://security.debian.org. you should update your SourcesList to include:
deb http://security.debian.org etch/updates main contrib non-free
deb-src http://security.debian.org etch/updates main contrib non-free
Instead of the older urls that included http://security-testing-master.debian.net.
Refer to the [wiki:Status/Stable Status of Stable] page for a list of current ["?DebianSecurityAdvisories"], or see the [wiki:Security security page] for information about keeping your Debian install secure.
Current Issues Affecting Testing
x.org 7.0
["Xorg"] 7.0 has migrated to Testing. Refer to Xorg69To7 for common issues regarding this transition.
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
Quick links
- [wiki:Status The Status page]
- [wiki:Status/Stable Status of Stable]
- [wiki:Status/Unstable Status of Unstable]