Processing commands for [EMAIL PROTECTED]:
tags 235976 + pending
Bug#235976: apache: Apache overwrites local configuration
There were no tags set.
Tags added: pending
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
nach einem Wechsel von Suse auf Debian steht folgendes Problem an:
Im Website-Verzeichnis ist eine .htaccess abgelegt, die eine php-URL in
eine HTML-URl umwandeln soll. Bei SuSe ging das reibungslos. Unter Debian
kommt
die Meldung:
---
Forbidden
You don't have permission to access /... on this
Processing commands for [EMAIL PROTECTED]:
tags 234650 + pending
Bug#234650: apache-ssl 1.3.29.0.1-3 not reading config files
There were no tags set.
Tags added: pending
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
apache_1.3.29.0.2-1_i386.changes uploaded successfully to localhost
along with the files:
apache_1.3.29.0.2-1.dsc
apache_1.3.29.0.2.orig.tar.gz
apache_1.3.29.0.2-1.diff.gz
apache-doc_1.3.29.0.2-1_all.deb
apache_1.3.29.0.2-1_i386.deb
apache-ssl_1.3.29.0.2-1_i386.deb
Accepted:
apache-common_1.3.29.0.2-1_i386.deb
to pool/main/a/apache/apache-common_1.3.29.0.2-1_i386.deb
apache-dbg_1.3.29.0.2-1_i386.deb
to pool/main/a/apache/apache-dbg_1.3.29.0.2-1_i386.deb
apache-dev_1.3.29.0.2-1_i386.deb
to pool/main/a/apache/apache-dev_1.3.29.0.2-1_i386.deb
Your message dated Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#45268: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#234091: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#233694: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#229653: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#229653: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#226833: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#226833: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#219378: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#226131: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#228355: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#229000: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#230718: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#231387: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#233097: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#232668: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#234650: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#234731: fixed in apache 1.3.29.0.2-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 Sun, 07 Mar 2004 08:32:06 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#235976: fixed in apache 1.3.29.0.2-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
This patch fixes problems seen by apache modules attempting to run regex
stuff, and getting apache's internal pcre implementation. It contains
two parts; the first (the autoconf stuff) checks if libpcre is installed
on the host system. If it is, that pcre is used to build apache2. If
it's not,
There is a bug in the build process for apache2 where by the static
debian/config_vars.mk is used in all mpm packages. This is incorrect as
the config_vars.mk is used by apxs2 and must contain changes for the
specific mpm build target. For example, in apache2-prefork-dev, the
installed
Package: apache
Version: 1.3.29.0.2-1
Severity: grave
Hi,
In /usr/share/apache/postinst.common:do_ucf(), there are two calls to
ucf --debconf-ok. However it appears the version of ucf available in
sid does not support that flag. Making apache unable to install correctly.
Wolfgang
-- System
Hi Wolfgang,
according to ucf documentation --debconf-ok is supported from
version 0.28 and there is a specific dependency on it in apache-common.
Can you kindly show us the error you get?
Thanks
Fabio
On Sun, 7 Mar 2004, Wolfgang Sourdeau wrote:
Package: apache
Version: 1.3.29.0.2-1
27 matches
Mail list logo
