Your message dated Tue, 29 Apr 2008 23:37:39 +0100
with message-id <[EMAIL PROTECTED]>
and subject line libapache-mod-lisp has been removed from Debian, closing
#152742
has caused the Debian Bug report #152742,
regarding libapache-mod-lisp 2.2-2 lockups using clisp 2.28 and apache 1.3.26
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
152742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=152742
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libapache-mod-lisp
Version: 2.2-2
Hi Matthew and Marc,
I have libapache-mod-lisp 2.2-2, apache 1.3.26-0woody1 and clisp 2.28-1
installed in Debian Woody with Rachel's contributed test file
http://www.fractalconcept.com/fcweb/download/modlisp-clisp.lisp.gz
After I run (modlisp:modlisp-server) to start the server it works fine
for a while before I get a lockup. Trying to wget "fixed" (the key
values page) almost always locks up the server.
clisp doesn't crash nor give any output. I just have to break, exit and
restart clisp.
Two other people have found the same problem with clisp on Mac OS X and
FreeBSD:
http://groups.google.co.nz/groups?selm=6b4aa54a.0206060137.3739b9a4%40posting.google.com
With a wget induced lockup the transfer ends with 0 bytes only after I
break (ctrl-c) clisp.
The Debian libapache-mod-lisp binary probably wasn't produced from the
current Apache source. Compiling a current binary is probably the first
thing to try.
Regards,
Adam Warner
--- End Message ---
--- Begin Message ---
Version: 2.43-2+rm
The libapache-mod-lisp package has been removed from Debian testing, unstable
and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/431034 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
