Your message dated Fri, 24 Oct 2008 00:53:48 -0400
with message-id <[EMAIL PROTECTED]>
and subject line close
has caused the Debian Bug report #431810,
regarding nvidia-kernel-legacy-96xx-2.6.18-4-686: 96xx should conflict with 
71xx and vice versa
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 [EMAIL PROTECTED]
immediately.)


-- 
431810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431810
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: nvidia-kernel-legacy-96xx-2.6.18-4-686
Version: 1.0.9639+1
Severity: important

the 96xx and 71xx kernel module packages should conflict.  both attempt
to write to the same nvidia.ko file, which leads to various problems
including a broken apt database.

mike

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nvidia-kernel-legacy-96xx-2.6.18-4-686 depends on:
ii  linux-image-2.6.18 2.6.18.dfsg.1-12etch2 Linux 2.6.18 image on PPro/Celeron
ii  nvidia-kernel-comm 20051028+1            NVIDIA binary kernel module common

nvidia-kernel-legacy-96xx-2.6.18-4-686 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
this is no longer an issue for lenny since 71xx binary packages are
not being provided.  and even so, "m-a a-i nvidia-kernel-legacy-71xx"
doesn't build correctly.  hence, it will require perseverence from the
user to get 71xx installed, and hence a very low probability of this
conflict with the 96xx driver.


--- End Message ---

Reply via email to