On Thu, 14 Sep 2006 14:52:35 +0200, Robert Millan <[EMAIL PROTECTED]> said:
> On Wed, Sep 13, 2006 at 05:49:16PM -0600, dann frazier wrote:
>> Package: oss-compat Version: 0.0.3 Severity: normal
>>
>> Errors were encountered while processing: oss-compat E: Sub-process
>> /usr/bin/dpkg returned an error code (1) A package failed to
>> install. Trying to recover: Setting up oss-compat (0.0.3) ...
>> FATAL: Could not load /lib/modules/2.6.17-1-mckinley/modules.dep:
>> No such file or directory dpkg: error processing oss-compat
>> (--configure): subprocess post-installation script returned error
>> exit status 1 Errors were encountered while processing: oss-compat
>>
>>
>> This is likely because I no longer have 2.6.17-1-mckinley installed
>> - I have upgraded to 2.6.17-2-mckinley, but have not rebooted yet.
> If you uninstall the modules for your running version of Linux, your
> system is broken untill you reboot. oss-compat's postinst is set -e
> in purpose to exhibit the problem (rather than silently ignoring
> it).
> IMHO, prerm generated by kernel-package should prevent this from
> happening by aborting with error when attempting to remove modules
> for a running kernel.
> Doesn't this already happen?
The prerm asks. You can always tell the kernel image to go
ahead anyway.
manoj
--
You are false data.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
