[resending to submitter]
On Thu, May 30, 2013 at 12:23:04AM +0100, Dominic Hargreaves wrote:
> On Tue, May 28, 2013 at 04:53:01PM +0300, Niko Tyni wrote:
> > On Sat, May 25, 2013 at 08:03:35PM +0200, gregor herrmann wrote:
> > > On Sat, 25 May 2013 11:47:01 +0300, Niko Tyni wrote:
> >
> > > > I j
On Tue, May 28, 2013 at 04:53:01PM +0300, Niko Tyni wrote:
> On Sat, May 25, 2013 at 08:03:35PM +0200, gregor herrmann wrote:
> > On Sat, 25 May 2013 11:47:01 +0300, Niko Tyni wrote:
>
> > > I just pushed a ntyni/httpd24 branch to the git repo. I think it should
> > > be rebased onto whichever sol
On Tue, May 28, 2013 at 04:53:01PM +0300, Niko Tyni wrote:
> On Sat, May 25, 2013 at 08:03:35PM +0200, gregor herrmann wrote:
> > On Sat, 25 May 2013 11:47:01 +0300, Niko Tyni wrote:
>
> > > I just pushed a ntyni/httpd24 branch to the git repo. I think it should
> > > be rebased onto whichever sol
On Sat, May 25, 2013 at 08:03:35PM +0200, gregor herrmann wrote:
> On Sat, 25 May 2013 11:47:01 +0300, Niko Tyni wrote:
> > I just pushed a ntyni/httpd24 branch to the git repo. I think it should
> > be rebased onto whichever solution we choose for the upstream merge.
>
> Same for my gregoa/httpd
On Sat, 25 May 2013 11:47:01 +0300, Niko Tyni wrote:
> > ... I just merged the 2_0_8 tag into the httpd24 branch and tarred it up.
> > svn merge didn't complain, so that sould be ok, I guess.
>
> Nice it was that easy. For some reason I thought 'svn merge' wouldn't
> work at all without write acc
On Fri, 24 May 2013 22:09:33 +0200, gregor herrmann wrote:
> > If somebody could look at merging the upstream SVN httpd24 branch with
> > the 2.0.8 release, that would be great. We're going to need at least
> > the Perl 5.18 fixes next.
> ... I just merged the 2_0_8 tag into the httpd24 branch and
On Fri, May 24, 2013 at 10:09:33PM +0200, gregor herrmann wrote:
> On Fri, 24 May 2013 22:28:34 +0300, Niko Tyni wrote:
> > If somebody could look at merging the upstream SVN httpd24 branch with
> > the 2.0.8 release, that would be great. We're going to need at least
> > the Perl 5.18 fixes next.
-=| Niko Tyni, 24.05.2013 22:28:34 +0300 |=-
> On Fri, May 24, 2013 at 11:03:13AM +0300, Niko Tyni wrote:
>
> > Overall it looks to me like the code for 2.4 support is fine, but
> > the Apache-Test side has some quirks left as it has to parse Apache
> > configuration files to generate the test con
On Fri, 24 May 2013 22:28:34 +0300, Niko Tyni wrote:
> Status update: things are looking better. I have a basically working 2.4
> package now, with dh_apache2 and all. I think we'll have to ignore the
> test suite failures for the apache2 transition and look at them later.
Cool!
> I'm currently
On Fri, May 24, 2013 at 11:03:13AM +0300, Niko Tyni wrote:
> Overall it looks to me like the code for 2.4 support is fine, but
> the Apache-Test side has some quirks left as it has to parse Apache
> configuration files to generate the test configurations.
>
> I have not looked at the packaging si
Hi,
On 24.05.2013 10:03, Niko Tyni wrote:
> + run '. /etc/apache2/envvars' to get the parts ripped from /etc/apache2
> to t/conf/httpd.conf working (we should probably provide our own
> Apache2
> config under debian/ and make Apache-Test use that as a base)
> + manually add t
On Thu, May 23, 2013 at 03:22:36PM +0100, Dominic Hargreaves wrote:
> [Ccing debian-perl to get a slightly greater awareness of the issue.]
>
> On Thu, May 23, 2013 at 01:13:53PM +0200, Arno Töll wrote:
> > we are ready to upload Apache2 2.4 to Debian Sid now. This means the
> > transition is effe
[Ccing debian-perl to get a slightly greater awareness of the issue.]
On Thu, May 23, 2013 at 01:13:53PM +0200, Arno Töll wrote:
> we are ready to upload Apache2 2.4 to Debian Sid now. This means the
> transition is effectively starting now, and going to break your modules.
>
>
> We have schedul
13 matches
Mail list logo
