Bug#339658: should not call update-modules for module-init-tools

2005-12-08 Thread Marco d'Itri
On Dec 05, Joey Hess [EMAIL PROTECTED] wrote: Anyway, if you add a depmod call to update-modules then debhelper could just run it and not worry about needing to run depmod. If OTOH you do want to eventually remove update-modules from module-init-tools then we will have to live with debhelper

Bug#339658: should not call update-modules for module-init-tools

2005-12-05 Thread Joey Hess
Marco d'Itri wrote: update-modules needs to be called only when /etc/modutils/ is modified, so dh_installmodules should not add code to call it in other situations (specifically when /etc/modprobe.d/ is modified or when new modules are installed). dh_installmodules generates code to run

Bug#339658: should not call update-modules for module-init-tools

2005-12-05 Thread Marco d'Itri
On Dec 05, Joey Hess [EMAIL PROTECTED] wrote: dh_installmodules generates code to run update-modules in the postinst and postrm, which are run when modules are installed or removed. Amoung other things, the depmod call in update-modules.modutils makes the newly installed modules in the

Bug#339658: should not call update-modules for module-init-tools

2005-12-05 Thread Joey Hess
Marco d'Itri wrote: Right, I did not remember that update-modules also runs depmod. This is interesting, because if modutils is not installed then depmod will not be run by the update-modules script of module-init-tools. Nobody ever reported this, so I wonder if the packages which install 2.6

Bug#339658: should not call update-modules for module-init-tools

2005-11-17 Thread Marco d'Itri
Package: debhelper Version: 5.0.7 Severity: normal update-modules needs to be called only when /etc/modutils/ is modified, so dh_installmodules should not add code to call it in other situations (specifically when /etc/modprobe.d/ is modified or when new modules are installed). -- ciao, Marco