Your message dated Fri, 09 Apr 2010 01:57:17 -0700
with message-id <[email protected]>
and subject line Re: nvidia-kernel-2.6-amd64: "-amd64" packages should be built
for i386 architecture
has caused the Debian Bug report #428487,
regarding nvidia-kernel-2.6-amd64: "-amd64" packages should be built for i386
architecture
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.)
--
428487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428487
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-kernel-2.6-amd64
Severity: normal
Currently the linux-image-2.6-amd64 packages (such as
linux-image-2.6.18-4-amd64, linux-image-2.6.21-1-amd64 and so on) are being
built for both amd64 and i386 architectures. But nvidia kernel modules
(nvidia-kernel-2.6-amd64:
nvidia-kernel-2.6.18-4-amd64/nvidia-kernel-legacy-2.6-amd64 and like this) are
being built for amd64 only. There seems to be many people interested in running
32bit-kernels on their Core-2-s and Athlon-64-s, wishing to have these kernels
fully optimized for their CPUs nevertheless; giving them opportunity to support
Nvidia drivers in such configuration with usual Debian's ease would be useful.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (480,
'stable'), (450, 'unstable'), (400, 'experimental'), (1, 'experimental')
Architecture: i386 (i586)
Kernel: Linux 2.6.18-4-486
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 173.14.09+1
This was done (in nvidia-kernel-modules-i386) in 173.14.09+1, but the bug
was never closed. Closing it now with the correct version.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
--- End Message ---
