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: drm headers 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 ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-libc-dev: drm headers conflict with libdrm-dev
- From: Julien Cristau <jcristau@debian.org>
- Date: Fri, 30 Jan 2009 18:23:49 +0100
- Message-id: <20090130172340.GA1802@radis.liafa.jussieu.fr>
Package: linux-libc-dev Version: 2.6.28-1~experimental.1~snapshot.12651 Severity: serious Justification: undeclared file conflict Hi, the kernel started installing drm headers which previously came with libdrm-dev. If we decide to do things this way for squeeze, linux-libc-dev will need to Replaces appropriate versions of libdrm-dev, and libdrm will stop shipping these headers. However, maybe it'd make sense to stop shipping these headers from linux-libc-dev for now, until this can be uploaded to sid after lenny? Another temporary solution is to have an unversioned Replaces... Cheers, Julien
--- End Message ---
--- Begin Message ---
- To: 513604-done@bugs.debian.org
- Subject: drm linux-libc-dev file conflicts
- From: maximilian attems <max@stro.at>
- Date: Mon, 20 Apr 2009 10:13:07 +0200
- Message-id: <20090420081307.GA5430@stro.at>
Version: 2.6.29-2 the versioned replaces got bumped to latest input from xorg team, thus closing.
--- End Message ---