Package: apache2.2-common
Version: 2.2.3-3.1
Severity: important
Hi,
After upgrading apache 2.2, several authz_ modules I had specifically
disabled were re-enabled. If I've asked for a module to go away, it should go
away, it should not come back with an upgrade.
Thanks,
> I think all that's neccessary is a control file update to make it
> build-depend on the new stuff. I'll give it a shot and let you know. I can't
> upload it though, I'm not an official maintainer yet...
Tollef & Thom,
I just tested this, and libapache2-mod-perl2 builds in a
pbuild
Tollef Fog Heen <[EMAIL PROTECTED]> wrote:
> This has been fixed already. Somebody needs to upload a 2.2-compatible
> mod_perl, though.
I think all that's neccessary is a control file update to make it
build-depend on the new stuff. I'll give it a shot and let you know. I can't
upload it
Luk Claes <[EMAIL PROTECTED]> wrote:
> Package: libbtutil0
> Severity: serious
> Version: 0.0.19-1
>
> Your package is not installable as it depends on libapr0 which is not
> available in unstable anymore. You might want to update the dependency to
> libapr1.
I know. :-( Unfortunately, the apache
Package: apr
Severity: wishlist
APR provides browsable documentation via doxygen. It would be nice if the
debian APR source package created a apr-doc package out of doxygen's output
so people don't need to have http://apr.apache.org/docs/apr open when
they're programming.
Thanks,
Tyler
WOOHOO! Thanks!!
Archive Administrator <[EMAIL PROTECTED]> wrote:
> apache2_2.2.3-1~exp.r170_i386.changes uploaded successfully to localhost
> along with the files:
> apache2_2.2.3-1~exp.r170.dsc
> apache2_2.2.3.orig.tar.gz
> apache2_2.2.3-1~exp.r170.diff.gz
> apache2-common_2.2.3-1~ex
Kurt Roeckx <[EMAIL PROTECTED]> wrote:
> Yes, name it libapr-dev. If something really can use either one
> of the 2, I don't see why you should make a transition so hard
> and go and name it libapr0-dev.
>
> So I suggest you rename libapr0-dev to libapr-dev and make it
> provide libapr0-dev for n
Steve Dighans <[EMAIL PROTECTED]> wrote:
> Is there an easy way to get apache 2.2.2 installed into debian. I tried
> compiling from source but it keeps having errors
Odd, I've had no problems at all. Just make sure apache 2.0 isn't already
installed. What sort of errors did you have?
- Ty
Julien Danjou <[EMAIL PROTECTED]> wrote:
> I would like to know what are the status of Apache packages currently.
> There is several RC bugs, no update for a while and Apache 2.2 was
> released some month ago.
>
> Do you need help?
There's a few issues with Apache 2.2;
- It uses
Omry Yadan <[EMAIL PROTECTED]> wrote:
> apache2 does not support large files by default, there is a compile
> option for it,
>
> CFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"
>
> according to fajita, the friendly #apache bot.
It seems to be enabled by default on my Apache 2.2 inst
Stentor <[EMAIL PROTECTED]> wrote:
> install into apache server), so I haven't mod_proxy module
> compiled into my apache.
>
> the question is:
> what I have to do to inculde (
> install, compile) mod_proxy into my apache
> (please tell me step by step - I'm a little newbie ;) )
>
> I've tried
> m
d by
httpd...
Thanks,
Tyler
- Forwarded message from Tyler MacDonald <[EMAIL PROTECTED]> -
My apache module is being compiled with an RPATH by APXS:
W: libapache2-mod-bt: binary-or-shlib-defines-rpath
./usr/lib/apache2/modules/mod_bt.so /usr/local/lib
Is
Hello,
I'm working on debianizing my apache2 module
(http://www.crackerjack.net/mod_bt/). My hope is to eventually become a
debian package maintainer and supply debian with this apache2 extension.
I've gotten the core shared libs and apache2 handler done, and now it's time
for me to do the
13 matches
Mail list logo
