Bug#372938: x11-common and xfree86-common confiicts artificially prevents other apps from installing
Package: x11-common
Version: 7.0.20
* The exact and complete text of any error messages printed or
logged. This is very important!
The problem is prerequisites for packages which have not yet been
updated to use x11-common instead of or in addition to xfree86-common.
* Exactly what you typed or did to demonstrate the problem.
apt-get update
apt-get dist-upgrade
<x11-common installed, xfree86-common uninstalled, packages
depending soly on xfree86-common removed>
I fixed up the paths, etc as reported elsewhere
compatability packages, such as libxft1 and bugreport can no longer be
installed.
* A description of the incorrect behaviour: exactly what behaviour
you were expecting, and what you observed. A transcript of an example
session is a good way of showing this.
I expected to be able to continue to use legacy packages with a
dependancy on xfree86-common. Since in effect, xorg and x11 common
provide a new version of the same packages, this seems a reasonable
expectation.
Additionally, forcing the installation of a dependancy-broken app
permits the app to run correctly.
* A suggested fix, or even a patch, if you have one.
This seems to be a packaging issue, and I am not familiar with deb
packaging from a development point of view. However, it seems that if
it were possible to have xfree86-common and x11-common installed
simultaneously, much would be resolved. Perhaps even a dummy
xfree86-common package to permit old apps to still have their
dependancies satisfied.
* Details of the configuration of the program with the problem.
Include the complete text of its configuration files.
I am running deb testing with a large number of packages
* The versions of any packages on which the buggy package depends.
The versions do not matter, just the confilcts.
* What kernel version you're using (type uname -a), your shared C
library (type ls -l /lib/libc.so.6 or dpkg -s libc6 | grep ^Version),
and any other details about your Debian system, if it seems
appropriate. For example, if you had a problem with a Perl script, you
would want to provide the version of the `perl' binary (type perl -v
or dpkg -s perl | grep ^Version:).
These do not seem especially relevant.
* Appropriate details of the hardware in your system. If you're
reporting a problem with a device driver please list all the hardware
in your system, as problems are often caused by IRQ and I/O address
conflicts.
This does not seem relevant.
Thank you. If there is any additional information I can provide,
please let me know.
--Harley
Reply to: