Bug#384882: apache 2.2 does not work with current php4/php5 modules

2006-08-30 Thread Tollef Fog Heen
* Laurent Bonnaud | I'm going to raise the severity of this bug because breaking another | package deserves a grave severity. I'd rather argue it's a wishlist priority and again PHP for that. They should build packages for experimental. | To solve this problem, why not rename the experimental

Bug#385004: apache-ssl: I get this too

2006-08-30 Thread Philip Craig
Package: apache-ssl Version: 1.3.34-4 Followup-For: Bug #385004 Mine crashes in the same (nasty) way -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash

Bug#385004: Info received (apache-ssl: I get this too)

2006-08-30 Thread Philip Craig
I have now built and installed apache-ssl and apache-common from source using the previous version in testing, 1.34-2. This still fails with the same error, so I guess it must actually be a bug in a dependency? As apache is fine, I guess it may be some ssl dependency. Any ideas what this could

Bug#385004: Info received (apache-ssl: I get this too)

2006-08-30 Thread Philip Craig
I have more info. I did a stack trace with apache-ssl.dbg built from source, and it was crashing in libssl. But this didn't help. What *did* help was totally purging the apache-ssl package, deleting the /etc/apache-ssl directory, and reinstalling. It now works fine. Another theory is that

mod_proxy question

2006-08-30 Thread David M. Zendzian
Hello there, I recently went to turn on a reverse proxy through one of my debian apache1.3 machines and found mod_proxy but no mod_proxy_http or mod_proxy_connect available for apache 1.3. Is it just not available (ie I have to upgrade my 200 virtual hosts to apache2) or is it somewhere