Bug#396631: Same problem with latest version of apache2/libapr1
On Tue, Dec 19, 2006 at 12:46:52AM +0100, Andreas Barth wrote:
> * H. S. Teoh (hsteoh@quickfur.ath.cx) [061218 19:39]:
> > On Fri, Dec 15, 2006 at 05:53:38PM -0600, Peter Samuelson wrote:
> > >
> > > [H. S. Teoh]
> > > > Hi, the old patch (currently in unstable) already works---my test was
> > > > invalid because I upgraded apache2 but forgot to upgrade libapr1. Do
> > > > you still want me to test the new patch?
> > >
> > > Ahh - great to hear! Yes, If it's convenient for you, please do test
> > > my new patch. It's a little bit cleaner than the old one, and it does
> > > fix one bug, unless I'm completely misreading it.
> > [...
> >
> > Hi, I just tried to build libapr1 with the new patch, but I'm unable to
> > test it because I'm getting unrelated errors (apache2 doesn't load its
> > configuration correctly and doesn't start... I don't think this is
> > related to the patch, probably a build environment problem).
>
> Which architecture do you use?
[...]
i686. But it runs on a modified kernel that my colo provider uses for
running virtual servers. I'm not sure if this makes a difference in the
build. All I did was `apt-get source libapr1`, copy the new patch into
debian/patches, and run `dpkg-buildpackage -r fakeroot`.
T
--
IBM = I Blame Microsoft
Reply to: