Same problem here:
Stopping apache 2.0 web server...apache2: Syntax error on line 116 of
/etc/apache2/apache2.conf: Syntax error on line 1 of
/etc/apache2/mods-enabled/auth_ldap.load: API module structure
`ldap_module' in file /usr/lib/apache2/modules/mod_ldap.so is garbled -
perhaps this is not
Package: apache2.2-common
Version: 2.2.3-1
Severity: important
Hi,
Some apache modules that used to be present in apache2-common,
and that are referenced in /etc/apache2/mods-available and in
apache2.2 documentation are not available anymore.
mod_ext_filter is the one I was using, but there
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.21
reassign 391271 apache2
Bug#391271: apache2.2-common: Fails to install because of mod_actions.so
Bug reassigned from package `apache2.2-common' to `apache2'.
reassign 391265 apache2
* Steve Langasek
| On Thu, Oct 05, 2006 at 09:11:04AM -0600, Steve Langasek wrote:
| So it's my recommendation to downgrade and wontfix this bug, since there's
| no way to fix apache2-common's postrm script after the fact without
| introducing a dummy package that re-breaks our dependency
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.10
package apache2 apache2.2-common apache2-doc apache2-mpm-event
apache2-mpm-perchild apache2-mpm-prefork apache2-mpm-worker
apache2-prefork-dev apache2-threaded-dev apache2-utils
Processing commands for [EMAIL PROTECTED]:
reassign 391089 libaprutil1-dev
Bug#391089: apache2-prefork-dev: require libdb4.3-dev wich conflicts with
apache-dev (require libdb4.4-dev)
Bug reassigned from package `apache2-prefork-dev' to `libaprutil1-dev'.
thanks
Stopping processing here.
Your message dated Fri, 06 Oct 2006 18:44:50 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in NMU
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 responsibility to
Your message dated Fri, 06 Oct 2006 18:25:38 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#391089: apache2-prefork-dev: require libdb4.3-dev wich
conflicts with apache-dev (require libdb4.4-dev)
has caused the attached Bug report to be marked as done.
This means that you claim
Your message dated Fri, 06 Oct 2006 18:44:50 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in NMU
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 responsibility to
Your message dated Fri, 06 Oct 2006 18:44:50 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in NMU
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 responsibility to
Processing commands for [EMAIL PROTECTED]:
tag 299855 - fixed
Bug#299855: apache2: bash completion for administration tools
Tags were: fixed patch
Tags removed: fixed
tag 349416 - fixed
Bug#349416: FTBFS: apr_sendfile for the Hurd
Tags were: fixed upstream patch
Tags removed: fixed
tag
Your message dated Fri, 06 Oct 2006 18:44:50 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in NMU
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 responsibility to
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.10
reassign 301417 apr
Bug#301417: libapr is built with -D_REENTRANT
Bug reassigned from package `apache2' to `apr'.
End of message, stopping processing here.
Please contact me if you
Package: apache2
Version: 2.2.3-1
Severity: serious
When upgrading, I get the following log:
LANG=C apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Correcting dependencies... Done
The following extra packages will be installed:
apache2.2-common
The following
apache2_2.2.3-2_amd64.changes uploaded successfully to localhost
along with the files:
apache2_2.2.3-2.dsc
apache2_2.2.3-2.diff.gz
apache2.2-common_2.2.3-2_amd64.deb
apache2-mpm-worker_2.2.3-2_amd64.deb
apache2-mpm-prefork_2.2.3-2_amd64.deb
apache2-mpm-event_2.2.3-2_amd64.deb
Processing commands for [EMAIL PROTECTED]:
reassign 390819 apache2
Bug#390819: Apache2.2 upgrade makes apache2-common --remove fail
Bug reassigned from package `apache2-common' to `apache2'.
tag 390819 + pending
Bug#390819: Apache2.2 upgrade makes apache2-common --remove fail
There were no
apache2_2.2.3-2_amd64.changes uploaded successfully to localhost
along with the files:
apache2_2.2.3-2.dsc
apache2_2.2.3-2.diff.gz
apache2.2-common_2.2.3-2_amd64.deb
apache2-mpm-worker_2.2.3-2_amd64.deb
apache2-mpm-prefork_2.2.3-2_amd64.deb
apache2-mpm-event_2.2.3-2_amd64.deb
Rejected: Unknown distribution `UNRELEASED'.
===
If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted:
apache2-doc_2.2.3-2_all.deb
to pool/main/a/apache2/apache2-doc_2.2.3-2_all.deb
apache2-mpm-event_2.2.3-2_amd64.deb
to pool/main/a/apache2/apache2-mpm-event_2.2.3-2_amd64.deb
apache2-mpm-perchild_2.2.3-2_all.deb
to pool/main/a/apache2/apache2-mpm-perchild_2.2.3-2_all.deb
There are disparities between your recently accepted upload and the
override file for the following file(s):
apache2-mpm-perchild_2.2.3-2_all.deb: package says section is web, override
says net.
apache2-mpm-prefork_2.2.3-2_amd64.deb: package says section is web, override
says net.
Your message dated Fri, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390893: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390794: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390774: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390893: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390785: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#391393: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390893: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#391018: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390823: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390774: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390893: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390785: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390786: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390893: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#376680: fixed in apache2 2.2.3-2
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, 06 Oct 2006 15:32:36 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#390786: fixed in apache2 2.2.3-2
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
36 matches
Mail list logo
