Package: win32-loader Version: 0.6.8 Severity: serious Builds of win32-loader using latest grub-pc from lenny abort with "no module name found".
The problem depends only on the version of grub-pc used to build it, and has been introduced at an undetermined time after win32-loader 0.6.6, which I believe used grub-pc 1.96+20080429-1 to build. It went undetected because 0.6.7 and 0.6.8 were only tested on win98 (which is unaffected as it doesn't use grub). I'll be doing a regression test to trace this down. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-6-amd64 (SMP w/2 CPU cores) Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages win32-loader depends on: ii base-files 4.0.5 Debian base system miscellaneous f win32-loader recommends no packages. Versions of packages win32-loader suggests: pn wine <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
