Bug#271499: Reproduced

2006-03-15 Thread Filipus Klutiero
Just a note that I reproduced this installing Etch d-i beta2, while installing x-window-system-core. Here is an approximate log of the context in which this happened. I meant to join dpkg's log, but I unfortunately reinstalled over that install and lost that log, so this may be not as helpful a

Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-03-15 Thread Daniel Stone
On Wed, Mar 15, 2006 at 10:41:39PM +0100, Denis Barbier wrote: > On Wed, Mar 15, 2006 at 11:07:33PM +0200, Daniel Stone wrote: > > On Wed, Mar 15, 2006 at 09:27:00PM +0100, Denis Barbier wrote: > > > Where can we find documentation about moving conffiles between packages? > > > > 'Don't.' > > > >

Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-03-15 Thread Denis Barbier
On Wed, Mar 15, 2006 at 11:07:33PM +0200, Daniel Stone wrote: > On Wed, Mar 15, 2006 at 09:27:00PM +0100, Denis Barbier wrote: > > On Wed, Mar 15, 2006 at 12:17:49PM +0100, Frank Küster wrote: > > > > dpkg: error processing > > > > /var/cache/apt/archives/x11-common_6.9.0.dfsg.1-4_all.deb (--unpac

Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-03-15 Thread Daniel Stone
On Wed, Mar 15, 2006 at 09:27:00PM +0100, Denis Barbier wrote: > On Wed, Mar 15, 2006 at 12:17:49PM +0100, Frank Küster wrote: > > > dpkg: error processing > > > /var/cache/apt/archives/x11-common_6.9.0.dfsg.1-4_all.deb (--unpack): > > > trying to overwrite `/etc/X11/Xsession', which is also in p

Bug#356180: marked as done (Font paths wrong in dexconf from x11-common 1:7.0.2)

2006-03-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Mar 2006 21:31:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#356180: Close this bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your respons

Bug#354146: workaround

2006-03-15 Thread Bas Bloemsaat
doing the following will workaround the problem: dpkg --force-depends --remove xfree86-common apt-get update apt-get install x11-common Regards, Bas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-03-15 Thread Denis Barbier
On Wed, Mar 15, 2006 at 12:17:49PM +0100, Frank Küster wrote: > > dpkg: error processing > > /var/cache/apt/archives/x11-common_6.9.0.dfsg.1-4_all.deb (--unpack): > > trying to overwrite `/etc/X11/Xsession', which is also in package > > xfree86-common > > dpkg-deb: subprocess paste killed by sig

Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-03-15 Thread Frank Küster
Hi! Does really nobody care about this serious bug - it hinders very much testing of upgrades from sarge to etch. Frank Küster <[EMAIL PROTECTED]> wrote: > Package: x11-common > Version: 1:7.0.0 > Severity: grave > > After login in a sarge chroot, I installed tetex-bin (probably that can > be mu

Bug#354130: xbase-clients: "(WW) Couldn't load XKB keymap, falling back to pre-XKB keymap" with xorg 7.0

2006-03-15 Thread Luca Capello
Hello! On Tue, 14 Mar 2006 22:10:27 +0100, Denis Barbier wrote: > On Tue, Mar 14, 2006 at 02:40:22PM +0100, Luca Capello wrote: >> Well, it seems that the bug is still present in my Xorg.0.log >> (attached). My xorg.conf is attached as well. > > Which version of xkb-data is installed? For the re

Bug#357007: Enabling direct rendering for kernels-2.5.15 and below

2006-03-15 Thread Svante Signell
Package: xserver-xorg-video-mga Version: 1:1.2.1.3.dfsg.1-1 Severity: normal For kernels 2.6.15 and below the following option is needed to /etc/X11/xorg.conf in order to enable direct rendering for AGP cards: Option "OldDmaInit" "True" For kernels 2.6.16 and later this is not needed. It it po

Bug#356180: Close this bug

2006-03-15 Thread Svante Signell
This bug is related to bug 356181, which is already solved. You can close this bug too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]