Bug#365948: x11-common: broken depends on compat package xfree86-common
Package: x11-common Version: 1:7.0.16 Severity: grave Justification: renders package unusable Version 7.0.16 of x11-common depends on xfree86-common, which is a "useless" compatibility package. Making things worse is that xfree86-common conflicts with x11-common. This prevents x11-common from being installed at all. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.0 Debian configuration management sy ii debianutils 2.16 Miscellaneous utilities specific t ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: * x11-common/xwrapper/nice_value: 0 * x11-common/xwrapper/allowed_users: Anybody x11-common/experimental_packages: x11-common/xwrapper/actual_allowed_users: anybody x11-common/xwrapper/nice_value/error: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365948: x11-common: broken depends on compat package xfree86-common
I screwed this up. It installs fine if I do it right. smime.p7s Description: S/MIME Cryptographic Signature
Bug#365948: x11-common: broken depends on compat package xfree86-common
The installation is not clean. You can find the following script in the xfree86-common.postinst. # Just move the Xsession file if it's still around if [ -f /etc/X11/Xsession ]; then mv /etc/X11/Xsession /etc/X11/Xsession.xfree86 fi This action makes a big broken in my system. I can't use startx to start Xwindow -- Best Regards Haifeng Chen
Bug#365948: x11-common: broken depends on compat package xfree86-common
On Wed, May 03, 2006 at 06:35:56PM -0400, Ray Kohler wrote: > Package: x11-common > Version: 1:7.0.16 > Severity: grave > Justification: renders package unusable > Version 7.0.16 of x11-common depends on xfree86-common, which is a > "useless" compatibility package. Making things worse is that > xfree86-common conflicts with x11-common. This prevents x11-common from > being installed at all. > I screwed this up. It installs fine if I do it right. So your assessment is that there's no bug here? What way did you do it first that was "wrong", btw? On Thu, May 04, 2006 at 10:15:29AM +0800, Haifeng Chen wrote: > The installation is not clean. > You can find the following script in the xfree86-common.postinst. > # Just move the Xsession file if it's still around > if [ -f /etc/X11/Xsession ]; then > mv /etc/X11/Xsession /etc/X11/Xsession.xfree86 > fi Right... this is a problem because plenty of users already *have* an x11-common on their system (in unstable) that contains /etc/X11/Xsession, so this code deletes the x11-common version of the config file for those users -- not the xfree86-common version! The workaround is, after upgrade, to run apt-get install --reinstall -o DPkg::Options::=--force-confmiss x11-common to restore the missing /etc/X11/Xsession file. This bug will only affect upgrades within unstable; it will not affect users who are still running testing, so technically this is not release-critical (it doesn't need to be fixed before xorg is updated in testing), but it's still rather nasty... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#365948: x11-common: broken depends on compat package xfree86-common
Steve Langasek wrote: On Wed, May 03, 2006 at 06:35:56PM -0400, Ray Kohler wrote: Package: x11-common Version: 1:7.0.16 Severity: grave Justification: renders package unusable Version 7.0.16 of x11-common depends on xfree86-common, which is a "useless" compatibility package. Making things worse is that xfree86-common conflicts with x11-common. This prevents x11-common from being installed at all. I screwed this up. It installs fine if I do it right. So your assessment is that there's no bug here? What way did you do it first that was "wrong", btw? Right, I don't think there's really a bug here. What I did wrong, was to try to install them "by hand" with dpkg, and not to notice that I was dealing with a Pre-Depends rather than an ordinary Depends. In any case, I can't reproduce it at all installing it with apt-get. smime.p7s Description: S/MIME Cryptographic Signature
