Re: Bug#255180: module-init-tools: removal of modprobe.conf breaks mkinitrd

[Jens Schmalzing <j.s@lmu.de>]

reassign module-init-tools 255180
merge 255180 254950
thanks

Hi,

Marco d'Itri writes:

> reassign initrd-tools 255180
> thanks
> 
> On Jun 19, Henning Glawe <glaweh@physik.fu-berlin.de> wrote:
> 
> > after installing module-init-tools 3.1-pre2-1 mkinitrd, which is needed
> > for the debian-prepackaged kernels, ceases to work. this is cause by the
> > removal of modprobe.conf generation in module-init-tools/update-modules
> > for now I downgraded to 3.0-pre10-4, so building initrds works again.
> Then mkinitrd needs to be fixed.

I ran into the very same bug this morning, and it's obviously a
special case of #254950.  Downgrading module-init-tools to 3.0-pre10-4
and putting it on hold works around the problem, but it should really
be fixed by allowing to load modules from read-only filesystems.

Regards, Jens.

-- 
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!