Re: local-unbound stopped working after upgrade to 13.2

In message <c394f074-3474-4bb6-8534-ed2400029010@aetern.org>, Yuri writes:
> Chris wrote:
> > On 2023-09-18 08:26, Yuri wrote:
> >> Chris wrote:
> >>> On 2023-09-17 11:15, Alain Zscheile wrote:
> >>>> Hi,
> >>>>
> >>>> After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound
> >>>> doesn't
> >>>> appear to work anymore
> >>>> (doesn't return DNS responses for anything, although I don't have
> >>>> network traces).
> >>>>
> >>>> For now, I just disabled it on all my systems, but I believe this is a
> >>>> bug that
> >>>> should be fixed...
> >>>
> >>> This is more likely a ports issue and would be better served on the
> >>> ports@ list.
> >>
> >> local-unbound is in bsae.
> > You mean base, right? ;-)
> > Sure. But it's derived from the source in ports. Maybe CC ports@ ?
>
> No, the source is in contrib/unbound, has its own set of build rules and
> the changes between 13.1 and 13.2 can be easily seen using git, don't
> see how ports are related.
>

This is correct. emaste@ refers to it as FreeBSD's bespoke build system. 
The word describes it succinctly.

This reminds me that 15-CURRENT will get an update to 1.18.0 once make 
universe finishes building, probably by tomorrow. It built successfully on 
amd64 already. It will be MFCed to stable/* in a couple of weeks or so 
after that.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
NTP:           <cy@nwtime.org>    Web:  https://nwtime.org

			e^(i*pi)+1=0