Date: Wed, 10 Sep 2014 20:41:05 +0200 From: olli hauer <ohauer@gmx.de> To: Adam Weinberger <adamw@adamw.org> Cc: Mathieu Arnold <mat@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org>, apache@freebsd.org Subject: Re: apache 2.2 ports Message-ID: <54109B41.70302@gmx.de> In-Reply-To: <77693D02-4172-42C6-B6CD-D68DF6EF547C@adamw.org> References: <8DF8037F-F9EC-488D-86C4-0923789C174C@adamw.org> <8c7c200293f6d84e756d6eec4a1edcc2@mail.feld.me> <1078D71E80C9283D7F23513F@ogg.in.absolight.net> <540F7CFB.4050304@gmx.de> <F83736752D4F0BB901E2A3DE@atuin.in.mat.cc> <540F829C.10301@gmx.de> <B5F3D52D-5119-4547-BA9C-7CCFC2BA4583@adamw.org> <0CF42C9D059713BFBD49709C@atuin.in.mat.cc> <77693D02-4172-42C6-B6CD-D68DF6EF547C@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-09-10 19:31, Adam Weinberger wrote: > On 10 Sep, 2014, at 4:31, Mathieu Arnold <mat@FreeBSD.org> wrote: > >> +--On 9 septembre 2014 19:36:35 -0400 Adam Weinberger <adamw@adamw.org> >> wrote: >> |> Here you go: https://reviews.freebsd.org/D750 >> | >> | Hi Olli, >> | >> | With the old patch in place, there were a few build runs that took place >> | that showed some interesting effects. One that I don’t think gets >> | resolved (and I’m not sure that it really can be) is that packages for >> | a lot of 2.2-dependent ports will be unavailable. >> >> Do you have a couple of examples ? > > http://gohan3.ysv.freebsd.org/data/10amd64-default-baseline/367609/logs/errors/mod_authnz_crowd-2.2.2_3.log > http://gohan3.ysv.freebsd.org/data/10amd64-default-baseline/367609/logs/errors/ap22-mod_amazon_proxy-20100913.log > > as examples. > > # Adam > Thats a general issue with in case changed API is not reflected and the port depends on another port that was fixed or does not require parts of the changed API. mod_authnz_crowd build against apache24 with this fix https://people.freebsd.org/~ohauer/diffs/apache/mod_authnz_crowd_apache22-24.diff mod_amazon_proxy build fine after changing s/22/22+/. Is portsmon working again or do we have a special report so such issues can be identified ? I open a PR for both ports so Vick and TOTA-san can test their port are working with the suggested patch. -- olli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54109B41.70302>