-=| 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 configurations. > > > > I have not looked at the packaging side at all yet. > > > > I doubt I have the time to pull this together by May 30th myself. More > > hands are definitely welcome. > > 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.
Nice!
> My time is up for tonight, but I hope to push something tomorrow, either
> to the 'master' branch or a separate one.
>
> I'm currently versioning this as 2.0.9~httpd24-r1449661-1, which is
> something of a lie as the httpd24 branch predates the 2.0.8 release.
> OTOH 2.0.8+httpd24-r1449661-1 isn't much closer to the truth either. I
> guess we shouldn't care at this point.
>
> 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 started in the other direction -- from the current 2.0.8 package,
picking commits from upstream's httpd24 branch, until the build
succeeded. The result is a series of patches, with which the
compilation seems to succeed. I couldn't make the tests really start
to run.
The picked changes are from the following upstream revisions:
1448037
1448098
1448100
1448194
1448197
1448199
1448202
1448242
Perhaps a less naive approach would be to really merge the http24
upstream branch, for example by importing every revision as a quilt
patch (28 in total, if my git-svn copy is right).
There is an incompatibility with the wheezy version that we need to
address somehow. "remote_ip" and "remote_port" request methods are
renamed to "client_ip" and "client_port". Perhaps small wrappers
providing the old methods for jessie? Another approach would be to
just document the change in NEWS.Debian.
Cheers,
dam
signature.asc
Description: Digital signature
