Hi,
On 15.07.2013 21:05, Steinar H. Gunderson wrote:
> I've uploaded 2.13-2, which goes through (I hope) all necessary motions to
> build against Apache 2.4. However, it also fixes a bunch of other things,
> and one of them is a package rename from libapreq2 to libapreq2-3, which
> means that the
On Mon, Jul 08, 2013 at 09:46:49PM +0200, gregor herrmann wrote:
> mod_perl with support for Apache 2.4 is in unstable since the end of
> May.
I've uploaded 2.13-2, which goes through (I hope) all necessary motions to
build against Apache 2.4. However, it also fixes a bunch of other things,
and on
On Mon, 08 Jul 2013 20:57:38 +0200, Steinar H. Gunderson wrote:
> On Sat, Jul 06, 2013 at 08:02:22PM +0200, Arno Töll wrote:
> > could you please tell us what the state being with libapreq2 is? It's
> > certainly one of these modules which might break in unexpected ways,
> > despite of still compi
On Sat, Jul 06, 2013 at 08:02:22PM +0200, Arno Töll wrote:
> Hi sesse,
>
> could you please tell us what the state being with libapreq2 is? It's
> certainly one of these modules which might break in unexpected ways,
> despite of still compiling against the Apache 2.4 API.
> On the other hand, if
On Sat, Jul 06, 2013 at 08:02:22PM +0200, Arno Töll wrote:
> could you please tell us what the state being with libapreq2 is? It's
> certainly one of these modules which might break in unexpected ways,
> despite of still compiling against the Apache 2.4 API.
The state is that I haven't even tried.
Hi sesse,
could you please tell us what the state being with libapreq2 is? It's
certainly one of these modules which might break in unexpected ways,
despite of still compiling against the Apache 2.4 API.
Looks like the latest upstream release was in 2010, but the module has
several reverse depend
6 matches
Mail list logo
