Bug#408243: gom: postinst fails: line 21: update-modules: command not found
severity 408243 minor retitle 408243 Either update or remove mixer initialisation on module load reopen 408243 quit On Mon, 2007-02-05 at 02:41 -0800, Steve Langasek wrote: (...) The only reason for calling this is the - optional (see auto_init in /etc/default/gom) - feature to recover mixer settings via gom automatically when the module is loaded. Um, what module? gom doesn't ship any modules and it doesn't ship any snd or snd-mixer-oss, resp. (gom does not ship these, of course). conffiles under /etc/modprobe.d, so what exactly is calling update-modules supposed to do for gom? They are under /etc/modutils; if there is no compatibility provided (afaik not), this would only work for 2.4 kernels. I guess for the future, this feature may be removed entirely for simplicity And for correctness, AFAICS. As update-modules is obsolete anyway, I agree; just wanted to keep the changeset as small as possible right now. MfG, Stephan -- Stephan A Suerken [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408243: gom: postinst fails: line 21: update-modules: command not found
On Fri, Feb 02, 2007 at 08:35:32AM +0100, Stephan Suerken wrote: On Thu, 2007-02-01 at 20:48 -0800, Steve Langasek wrote: * postrm|inst: Check for update-modules before calling. Fixes: gom: postinst fails: line 21: update-modules: command not found, thanks to Lucas Nussbaum (Closes: #408243). Why is this the right fix? More specifically -- if gom depends on update-modules being called for proper operation, why doesn't gom have a dependency on module-init-tools, and if it doesn't need update-modules for proper operation, why does it call it at all? I can't see anything in the contents of the gom package that explains why update-modules should be called. The only reason for calling this is the - optional (see auto_init in /etc/default/gom) - feature to recover mixer settings via gom automatically when the module is loaded. Um, what module? gom doesn't ship any modules and it doesn't ship any conffiles under /etc/modprobe.d, so what exactly is calling update-modules supposed to do for gom? I guess for the future, this feature may be removed entirely for simplicity And for correctness, AFAICS. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408243: gom: postinst fails: line 21: update-modules: command not found
Hello, * postrm|inst: Check for update-modules before calling. Fixes: gom: postinst fails: line 21: update-modules: command not found, thanks to Lucas Nussbaum (Closes: #408243). Why is this the right fix? More specifically -- if gom depends on update-modules being called for proper operation, why doesn't gom have a dependency on module-init-tools, and if it doesn't need update-modules for proper operation, why does it call it at all? I can't see anything in the contents of the gom package that explains why update-modules should be called. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408243: gom: postinst fails: line 21: update-modules: command not found
Hi, On Thu, 2007-02-01 at 20:48 -0800, Steve Langasek wrote: * postrm|inst: Check for update-modules before calling. Fixes: gom: postinst fails: line 21: update-modules: command not found, thanks to Lucas Nussbaum (Closes: #408243). Why is this the right fix? More specifically -- if gom depends on update-modules being called for proper operation, why doesn't gom have a dependency on module-init-tools, and if it doesn't need update-modules for proper operation, why does it call it at all? I can't see anything in the contents of the gom package that explains why update-modules should be called. The only reason for calling this is the - optional (see auto_init in /etc/default/gom) - feature to recover mixer settings via gom automatically when the module is loaded. So, gom does not depend on calling update-modules for proper operation. This least invasive fix will leave people actually using this feature w/ the same behaviour. I guess for the future, this feature may be removed entirely for simplicity (forcing a module-init-tool depends is not an option, imho). MfG, Stephan -- Stephan A Suerken [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408243: gom: postinst fails: line 21: update-modules: command not found
Package: gom Version: 0.30.1-1 Severity: serious Usertags: grid5000 piuparts rcness-questionable Hi, During a piuparts run over all the packages in etch, I ran into a problem with your package: Setting up gom (0.30.1-1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 75.) debconf: falling back to frontend: Readline /var/lib/dpkg/info/gom.postinst: line 21: update-modules: command not found dpkg: error processing gom (--configure): subprocess post-installation script returned error exit status 127 Errors were encountered while processing: gom E: Sub-process /usr/bin/dpkg returned an error code (1) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
