Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.22
reassign 281421 apache2-common
Bug#281421: apache2-common: /var/cache/apache2/proxy/ should be writable by
www-data
Bug reassigned from package `apache2.2-common' to `apache2-common'.
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.22
reassign 286138 apache2.2-common
Bug#286138: better module dependency handling needed
Bug reassigned from package `apache2' to `apache2.2-common'.
forcemerge 273929 286138
Your message dated Sun, 22 Oct 2006 10:52:40 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#286683: Please proxy_* adding LoadModule proxy_module
/usr/lib/apache2/modules/mod_proxy.so
has caused the attached Bug report to be marked as done.
This means that you claim that the
reassign 273929 apache2.2-common
forcemerge 273929 286138
stop
On Sun, Oct 22, 2006, Debian Bug Tracking System wrote:
forcemerge 273929 286138
Bug#273929: a2{en,dis}mod system needs a way to track dependencies
Bug#286138: better module dependency handling needed
Mismatch - only Bugs in the
Your message dated Sun, 22 Oct 2006 11:16:55 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#340770: IndexOptions not being incremental
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
Processing commands for [EMAIL PROTECTED]:
reassign 273929 apache2.2-common
Bug#273929: a2{en,dis}mod system needs a way to track dependencies
Bug reassigned from package `apache2-common' to `apache2.2-common'.
forcemerge 273929 286138
Bug#273929: a2{en,dis}mod system needs a way to track
Package: apache2
Version: 2.2.3-2
Severity: serious
apache2 2.0.55-4.1 depended on:
apache2-mpm-worker (= 2.0.55-4.1) |
apache2-mpm-prefork (= 2.0.55-4.1) |
apache2-mpm-perchild (= 2.0.55-4.1)
I think apache2 2.2.3-2 should depend on:
apache2-mpm-worker (= 2.2.3-2) |
apache2-mpm-prefork (=
Your message dated Sun, 22 Oct 2006 16:29:10 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#394658: doesn't depend on correct versions
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
found 340770 2.2.3-2
thank you
This has NOT been fixed in 2.2 I am still seeing this problem after upgrading
to apache2 2.2.3-2.
Here is the setup I tried:
/etc/apache2/apache2.conf:
Options Indexes MultiViews
IndexOptions FancyIndexing VersionSort HTMLTable NameWidth=*
reopen 394658
thank you
I think there is a need for an exact dependency. I upgraded from apache2
2.0.55-4.1 to apache2 2.2.3-2 and it didn't do anything. Nothing REAL got
upgraded. My copy of apache2-mpm-prefork stayed at version 2.0.55-4.1.
--Jayen
- Original Message
From: Tollef
Processing commands for [EMAIL PROTECTED]:
severity 394658 wishlist
Bug#394658: doesn't depend on correct versions
Severity set to `wishlist' from `serious'
tags 394658 + wontfix
Bug#394658: doesn't depend on correct versions
There were no tags set.
Tags added: wontfix
kthxbye
Stopping
what's the point of having an apache2 package then? the package doesn't really
depend on anything then, just that you have any implementation of apache2?
also, if another package depends on apache2 (=2.2) then the apache2 package
should depend on an implementation representative of the apache2
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.22
forcemerge 384128 294416
Bug#384128: apache2-common: If no apache2-mpm is installed, initscript gives no
advice on why it is not starting
Bug#294416:
Forcibly Merged 294416 384128.
severity 394658 wishlist
tags 394658 + wontfix
kthxbye
* Jayen Ashar
| I think there is a need for an exact dependency. I upgraded from
| apache2 2.0.55-4.1 to apache2 2.2.3-2 and it didn't do anything.
| Nothing REAL got upgraded. My copy of apache2-mpm-prefork stayed at
| version
Your message dated Sun, 22 Oct 2006 17:22:49 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#340770: closed by Tollef Fog Heen [EMAIL PROTECTED] (Re:
Bug#340770: IndexOptions not being incremental)
has caused the attached Bug report to be marked as done.
This means that you claim
Package: apache2
Version: 2.2.3-2
Severity: normal
As per Tollef's directions in bug 340770, I am opening this as a separate bug.
Here is the setup I tried:
/etc/apache2/apache2.conf:
IndexOptions FancyIndexing VersionSort HTMLTable NameWidth=*
/etc/apache2/sites-enabled/000-default:
Package: apache2
Version: 2.2.3-2
Severity: normal
This got closed with 340770, but I guess it's my fault for putting two bugs in
one bug report.
I tried:
/etc/apache2/apache2.conf:
IndexOptions FancyIndexing VersionSort HTMLTable NameWidth=*
/etc/apache2/sites-enabled/000-default:
I've now upgraded to the packages in unstable:
libapache2-mod-perl2 2.0.2-2.2
apache2-mpm-worker 2.2.3-2
The /etc/init.d/apache2 initscript still fails to start apache2.
What I now experience, however, is that apache2-mpm-prefork (from
Apache 2.2) also seems to
Besides, apache2ctl graceful does not restart the main apache process.
Only the worker processes are killed and forked off again. This means
the old executable keeps running, and apache or library updates won't
get active. On update, you need to do stop+start.
Cheers,
Stefan
--
To
Package: apache2-mpm-prefork
Version: 2.2.3-2
Severity: grave
Justification: renders package unusable
I just upgraded apache2 from version 2.0 to 2.2 and now apache2 no
longer starts. The file /var/log/apache2/error.log just shows this:
[Sun Oct 22 17:36:45 2006] [notice] Apache/2.2.3 (Debian)
* Jayen Ashar
| what's the point of having an apache2 package then? the package
| doesn't really depend on anything then, just that you have any
| implementation of apache2?
Yes, what else would it depend on?
| also, if another package depends on apache2 (=2.2) then the apache2
| package
| | what's the point of having an apache2 package then? the package
| | doesn't really depend on anything then, just that you have any
| | implementation of apache2?
|
| Yes, what else would it depend on?
a specific version of apache2, much as the previous versions of the apache2
package had
* David Muriel
| I just upgraded apache2 from version 2.0 to 2.2 and now apache2 no
| longer starts. The file /var/log/apache2/error.log just shows this:
This is probably a bug in some module. What modules do you have
enabled? Can you get a sensible backtrace from gdb --args apache2 -X ?
--
23 matches
Mail list logo
