On Fri, Mar 04, 2011 at 02:16:57PM +0100, Petr Salinger wrote:
>> Please could you try to rebuild php5 with "PHP5_COMPAT=yes" in debian/rules ?
> It does help.
>
> On both kfreebsd-i386 and kfreebsd-amd64:
>
> The fix should be in apr, it really should advertise their
> ino_t as unsigned 32-bit ty
Package: apache-dev
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
php has a bug requesting to bump the build-deps to libdb4.5-dev, which i'd
like to do but apache-dev build-depends on libdb4.4-dev which prevents
us from doing so. this may also apply to apache2 as well.
i just got hit by this too, and have wasted a few hours before finally
finding this bug report. the solution for me was as suggested simply
adding "AuthBasicProvider ldap" and "AuthzLDAPAuthoritative off".
the first one of the two above i found on my own and i'm not certain
there's an easy way to
tags 391918 patch
thanks
hi,
fyi this is still a problem in unstable. it looks like you've renamed
the suexec wrapper from suexec2, but dh_fixperms in debian/rules still
references suexec2 as the exception, thus the bit is stripped:
--- debian/rules.old2006-10-28 12:49:02.0 +0200
++
hi sylvain,
On Tue, 2006-10-24 at 09:51 +0200, sferriol wrote:
> i still have segfault with libapache-mod-php,php5-common (5.1.6-1).
but the latest version is 5.1.6-4... can you try that?
> there were some issues with libdb-linking that may have caused
> > segfaulting like what you describe.
hi,
i just my request never made it back to the OP for more information, so
i'm re-requesting additional information on this bug.
could you verify that this is still a problem with the latest version of
php? there were some issues with libdb-linking that may have caused
segfaulting like what you
On Thu, 2006-10-12 at 11:48 -0700, Debian Bug Tracking System wrote:
> > reassign 385004 openssl,apache-ssl,libapache-mod-php5
> Bug#385004: apache-ssl: segfault when upgrading to 1.3.34-4
> Bug reassigned from package `openssl,apache-ssl' to
> `openssl,apache-ssl,libapache-mod-php5'.
what versio
reopen 316321
thanks
sorry, i disagree. "reload" should not start a service that is not
running. i suppose current policy is a little ambiguous on the issue,
but i brought it up on devel some time before raising the severity and
the general consensus was in agreement with me. i also supplied a p
hey christian,
On Mon, Jul 10, 2006 at 04:23:17PM +0200, Christian Hammers wrote:
> So as you plan to go to 20 we will have the following?
> 19 startmysql
> 20 startapache/apache2
> 80 stop apache/apache2
> 81 stop mysql
don't forget that t
severity 316321 serious
tags 316321 patch
thanks
hi,
revisiting this issue, and after having spoken with folks
on -devel and -policy, the consensus is that this is in
fact a policy violation, so i am changing the severity
appropriately.
but, because doing so merely to do so wouldn't be so
constr
Package: apache2-common
Version: 2.0.54-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
in previous versions of apache, 'reload' would not automatically restart
the server if it was not running. but now in apache2:
Reloading web server config...httpd not running, trying to sta
Package: apache2-common
Version: 2.0.54-4
Followup-For: Bug #303228
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i'd like to second the motion to not have a2enmod reload the server.
or, at the least, not do so by default but include a cmdline flag
to do so. changing a configuration and reloadin
Package: apache
Version: 1.3.33-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello again :)
copelandia[~]09:24:53$ /usr/sbin/apache-modconf apache query mod_access
cp: cannot create regular file `/etc/apache/httpd.conf.dpkg-inst.queue':
Permission denied
is there any reason
Package: apache
Version: 1.3.33-2
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
it would be nice if apache-modconf used a conf.d style directory
instead of an autogenerated "do not edit this file, even though it's
in /etc" type file. this would make things less fragile ov
Package: apache
Version: 1.3.29.0.1-3
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i know that managing the list of loadable modules and package-related
apache configuration settings is a rather difficult thing to do, and i
think that it's caused headaches for package maintain
hey fabio,
On Fri, Dec 19, 2003 at 08:30:59AM +0100, Fabio Massimo Di Nitto wrote:
> That would explain the error you get from the postinst.. but is somewhere
> a directory??
it's a symlink to another symlink actually... and now i see that this
other symlink was broken. so... i guess we can go a
having another problem too, think it's related:
mini-me[/var]18:01:24# /etc/init.d/apache start
Configuration syntax error detected. Not reloading.
Syntax error on line 281 of /etc/apache/httpd.conf:
DocumentRoot must be a directory
mini-me[/var]18:04:02# ls -ld /var/www
lrwxrwxrwx1 root
Package: apache
Version: 1.3.29.0.1-3
Severity: normal
Tags: sid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Setting up apache (1.3.29.0.1-3) ...
mkdir: cannot create directory `/var/www': File exists
dpkg: error processing apache (--configure):
subprocess post-installation script returned err
18 matches
Mail list logo
