Package: apache2.2-common
Version: 2.2.3-3
Severity: important
*** Please type your report below this line ***
In apache2.2-common somebody choose to set up default charset:
apache2.2-common.postinst:45:
if [ ! -f /etc/apache2/conf.d/charset ]; then
echo AddDefaultCharset UTF-8
* Sven Mueller ([EMAIL PROTECTED]) [060625 09:23]:
Package: apache2-mpm-prefork
Version: 2.0.54-5
Severity: important
After a system crash, apache2 left an empty file behind
(/var/run/apache2/__db.ssl_scache to be exact). On reboot,
the file wasn't removed and when apache2 started, it
retitle 397481 apache2-mpm-prefork: segfault on startup on 2.4 kernels
forcemerge 394714 397481
thanks
* Mark Sheppard ([EMAIL PROTECTED]) [061109 10:07]:
I installed linux-image-2.6.17-2-686 (version 2.6.17-9) on the server in
question and rebooted with that and apache2 now works. That
Processing commands for [EMAIL PROTECTED]:
# default modules went missing since apache2 - fix typo in postinst
forcemerge 392349 392352 392701 393913 396678
Bug#392349: apache 2.2 upgrade breaks, missing Order (authz_host module)
Bug#392352: apache2.2-common: install does not enable replacement
retitle 395714 apache2 doesn't run on 2.4 kernels
block 395714 by 392049
thanks
* Peter Samuelson ([EMAIL PROTECTED]) [061023 15:17]:
Yeah, see #392049 and its duplicates. Tollef has a patch for libapr,
which I guess will go in soon.
Marking this bug appropriate.
Cheers,
Andi
--
severity 397886 serious
thanks
Hi,
* Michel Briand ([EMAIL PROTECTED]) [061110 01:34]:
This will modify apache configuration during an upgrade. Eventually will
cause all sites served locally to be IMPACTED by wrong charsets [mozilla
selects utf8 if apache told him that its the default - even
Processing commands for [EMAIL PROTECTED]:
severity 395853 serious
Bug#395853: apache2-common: removes symlinks on upgrade
Severity set to `serious' from `normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
apache2_2.2.3-3.1_i386.changes uploaded successfully to localhost
along with the files:
apache2_2.2.3-3.1.dsc
apache2_2.2.3-3.1.diff.gz
apache2.2-common_2.2.3-3.1_i386.deb
apache2-mpm-worker_2.2.3-3.1_i386.deb
apache2-mpm-prefork_2.2.3-3.1_i386.deb
apache2-mpm-event_2.2.3-3.1_i386.deb
Processing commands for [EMAIL PROTECTED]:
tags 397239 + upstream
Bug#397239: apache2: Since ugrading to 2.2.3-3, webdav doesn't work: Invalid
command 'AuthDigestFile'
There were no tags set.
Tags added: upstream
thanks
Stopping processing here.
Please contact me if you need assistance.
Hi,
* Greg Wooledge ([EMAIL PROTECTED]) [061106 11:12]:
Sorry about the root@ thing. I don't normally login to that server
as myself. This is my normal (work) e-mail address should you need to
contact me.
Thank you for your bug report.
According to
Processing commands for [EMAIL PROTECTED]:
severity 396265 grave
Bug#396265: apache2: mod_proxy_ajp connection reuse bug
Severity set to `grave' from `normal'
tags 396265 + patch
Bug#396265: apache2: mod_proxy_ajp connection reuse bug
There were no tags set.
Tags added: patch
--
Stopping
On Fri, Nov 10, 2006 at 05:52:32PM +0100, Steinar H. Gunderson wrote:
Anyhow, looking at the changelog, this option is supposed only to be enabled
for new installations, and the logic in the postinst seems correct. Are you
really upgrading, or is this a new installation?
It's a new install of
There are disparities between your recently accepted upload and the
override file for the following file(s):
apache2-mpm-event_2.2.3-3.1_i386.deb: package says section is web, override
says net.
apache2-mpm-perchild_2.2.3-3.1_all.deb: package says section is web, override
says net.
Your message dated Fri, 10 Nov 2006 18:03:06 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#397310: fixed in apache2 2.2.3-3.1
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 message dated Fri, 10 Nov 2006 18:03:06 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#391393: fixed in apache2 2.2.3-3.1
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 message dated Fri, 10 Nov 2006 18:03:06 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#392352: fixed in apache2 2.2.3-3.1
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 message dated Fri, 10 Nov 2006 18:03:06 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#392701: fixed in apache2 2.2.3-3.1
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 message dated Fri, 10 Nov 2006 18:03:06 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#392349: fixed in apache2 2.2.3-3.1
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 message dated Sat, 11 Nov 2006 08:45:35 +0100
with message-id [EMAIL PROTECTED]
and subject line This isn't sparc64 specific
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
severity 396782 important
thanks
* Don Geddis ([EMAIL PROTECTED]) [061102 13:05]:
I had a working apache2 configuration, with many virtual hosts.
After this recent upgrade, parts of my web sites stopped working.
I eventually discovered that the upgrade had added a new
000-default
20 matches
Mail list logo
