[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#517329: marked as done (linux-libc-dev: file conflict with libdrm-dev)



Your message dated Mon, 20 Apr 2009 10:13:07 +0200
with message-id <20090420081307.GA5430@stro.at>
and subject line drm linux-libc-dev file conflicts
has caused the Debian Bug report #513604,
regarding linux-libc-dev: file conflict with libdrm-dev
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
513604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513604
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-libc-dev
Version: 2.6.28-1
Severity: serious
Justification: fails to install/upgrade

Hi,

I'm running xorg from experimental, my libdrm-dev version is
2.4.4+git+20090205+8b88036-1

Upgrade of linux-libc-dev fails with

Unpacking replacement linux-libc-dev ...
dpkg: error processing
/var/cache/apt/archives/linux-libc-dev_2.6.28-1_i386.deb (--unpack):
 trying to overwrite `/usr/include/drm/drm_sarea.h', which is also in
 package libdrm-dev
 Errors were encountered while processing:
 /var/cache/apt/archives/linux-libc-dev_2.6.28-1_i386.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)


Cheers,
Michael

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.28.6
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.6.29-2

the versioned replaces got bumped to latest input from xorg team,
thus closing.



--- End Message ---

Reply to: