Your message dated Mon, 18 Jun 2007 23:20:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429572: /sbin/update-modules.modutils: infinite loop
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: module-init-tools
Version: 3.3-pre11-3
Severity: serious
Justification: breaks unrelated packages (such as kernel modules)
Hello,
On my system, after several recent upgrade tentatives, I end up with
tanyaivinco /home/vincent $ cat /sbin/update-modules
#!/bin/sh -e
if [ -x /sbin/update-modules.modutils ]; then
exec /sbin/update-modules.modutils "$*"
fi
exit 0
and
tanyaivinco /home/vincent $ cat /sbin/update-modules.modutils
#!/bin/sh -e
if [ -x /sbin/update-modules.modutils ]; then
exec /sbin/update-modules.modutils "$*"
fi
exit 0
So that running update-modules launches a nasty infinite loop -- and
some kernel module upgrade scripts do... dpkg -S says:
21:52 [EMAIL PROTECTED] ~ dpkg -S /sbin/update-modules
diversion by module-init-tools from: /sbin/update-modules
diversion by module-init-tools to: /sbin/update-modules.modutils
module-init-tools: /sbin/update-modules
I'm not really sure from which version this diversion is coming,
as if I purge module-init-tools, the output of dpkg -S is still the
same (without the last line, of course).
Maybe a cleanup of diversions in the next maintainer script
should be of order ? Or is that a file coming from modutils ? (which was
installed recently on my system, but is currently purged).
I set the severity to serious as it leaves my system in a not-so-good
state (enable to install kernel modules)... I do hope, however, that
this is just a corner case.
Regards,
Vincent Fourmond
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.21 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to
en_GB)
Shell: /bin/sh linked to /bin/dash
Versions of packages module-init-tools depends on:
ii libc6 2.5-11 GNU C Library: Shared libraries
ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip
module-init-tools recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Jun 18, Vincent Fourmond <[EMAIL PROTECTED]> wrote:
> On my system, after several recent upgrade tentatives, I end up with
> tanyaivinco /home/vincent $ cat /sbin/update-modules
So you probably broke it by yourself.
Let me know if you cant find a better explanation.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
