Processed: Re: Bug#219897: hw-detect: destroys debconf/priority up if run after a failed module

2003-11-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 219897 + pending Bug#219897: hw-detect: destroys debconf/priority up if run after a failed module Tags were: d-i Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking

Bug#219897: hw-detect: destroys debconf/priority up if run after a failed module

2003-11-10 Thread Steinar H. Gunderson
On Sun, Nov 09, 2003 at 10:45:54PM -0500, Joey Hess wrote: >> If one first runs a module that fails (for instance, install LILO on a >> non-existant drive, or install base from network with cable unplugged) >> and then run hw-detect, weird stuff happens: > Can you provide an easier way to reproduce

Bug#219897: hw-detect: destroys debconf/priority up if run after a failed module

2003-11-09 Thread Joey Hess
Steinar H. Gunderson wrote: > If one first runs a module that fails (for instance, install LILO on a > non-existant drive, or install base from network with cable unplugged) > and then run hw-detect, weird stuff happens: Can you provide an easier way to reproduce this? hw-detect here does skip loa

Bug#219897: hw-detect: destroys debconf/priority up if run after a failed module

2003-11-09 Thread Steinar H. Gunderson
Package: hw-detect Severity: important Tags: d-i This has been discussed on IRC earlier, but deserves a bug report so we won't forget it before it's fixed :-) If one first runs a module that fails (for instance, install LILO on a non-existant drive, or install base from network with cable unplugg