Package: libapache-mod-speedycgi
Version: 2.22-1
Severity: grave
Justification: causes non-serious data loss

Hi,

removing libapache-mod-speedycgi leaves /etc/apache/httpd.conf
zero-sized. This happens because the postrm script tries to comment
out references to the module like this:

cat /etc/apache$1/httpd.conf |\
     sed 's/^(LoadModule.*mod_speedycgi\.so)/#\1/' > $tmpfile || true
mv -f $tmpfile /etc/apache$1/httpd.conf

but the correct sed grouping markers are '\(' and '\)' instead of '(' and ')'.
Then sed bails out:

sed: -e expression #1, char 39: invalid reference \1 on `s' command's RHS

and $tmpfile ends up empty.

(Furthermore, at least on my system the LoadModule line is in
/etc/apache/modules.conf, not httpd.conf, so the commenting out
wouldn't apparently work anyway.)

Transcript follows:

# ls -l /etc/apache/httpd.conf 
-rw-r--r--  1 root root 35462 2005-08-30 22:17 /etc/apache/httpd.conf
# dpkg -r libapache-mod-speedycgi
(Reading database ... 165864 files and directories currently installed.)
Removing libapache-mod-speedycgi ...
sed: -e expression #1, char 39: invalid reference \1 on `s' command's RHS
An Apache module has been modified.  Restart apache [Y/n]? 
/usr/sbin/apachectl graceful: httpd gracefully restarted
# ls -l /etc/apache/httpd.conf 
-rw-r--r--  1 root root 0 2005-08-30 22:18 /etc/apache/httpd.conf


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_US, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages libapache-mod-speedycgi depends on:
ii  apache-common               1.3.33-6     support files for all Apache webse
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libdb4.1                    4.1.25-18    Berkeley v4.1 Database Libraries [
ii  libexpat1                   1.95.8-3     XML parsing C library - runtime li
ii  speedy-cgi-perl             2.22-1       speed up perl scripts by making th

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to