Paul Gevers wrote:
>>
>> Config file fragment handling in unbound
>>
>> The DNS resolver unbound
>> has changed the way it handles configuration file fragments. If
>> you are relying on an include: directive to
>> merge several fragments into a valid
Hi,
On 22-03-2021 17:34, Justin B Rye wrote:
> Andrei POPESCU wrote:
>> The NEWS file is also available online:
>>
>> https://sources.debian.org/src/unbound/1.13.1-1/debian/NEWS/
>
> That's a better idea than the alternative I was considering, which was
> to point at this bug report. So we
On Lu, 22 mar 21, 16:34:00, Justin B Rye wrote:
> Andrei POPESCU wrote:
> > The NEWS file is also available online:
> >
> > https://sources.debian.org/src/unbound/1.13.1-1/debian/NEWS/
>
> That's a better idea than the alternative I was considering, which was
> to point at this bug report. So
Andrei POPESCU wrote:
> The NEWS file is also available online:
>
> https://sources.debian.org/src/unbound/1.13.1-1/debian/NEWS/
That's a better idea than the alternative I was considering, which was
to point at this bug report. So we could cut it all the way down to
something like:
On Lu, 22 mar 21, 14:33:25, Justin B Rye wrote:
> Andrei POPESCU wrote:
> >
> > How about squeezing even further and pointing to the NEWS file instead
> > (for those that have unbound installed, but not apt-listchanges).
>
> The problem is, that way the information they need to implement a fix
Andrei POPESCU wrote:
> On Du, 21 mar 21, 13:01:07, Justin B Rye wrote:
>> Robert Edmonds wrote:
>>> During the bullseye release cycle the default /etc/unbound/unbound.conf
>>> file was changed to use the newly introduced "include-toplevel:"
>>> directive rather than the "include:" directive. This
On Du, 21 mar 21, 13:01:07, Justin B Rye wrote:
> Robert Edmonds wrote:
> > During the bullseye release cycle the default /etc/unbound/unbound.conf
> > file was changed to use the newly introduced "include-toplevel:"
> > directive rather than the "include:" directive. This should probably be
> >
Robert Edmonds wrote:
> During the bullseye release cycle the default /etc/unbound/unbound.conf
> file was changed to use the newly introduced "include-toplevel:"
> directive rather than the "include:" directive. This should probably be
> mentioned in the bullseye release notes because it will
Package: release-notes
Severity: normal
Hi,
During the bullseye release cycle the default /etc/unbound/unbound.conf
file was changed to use the newly introduced "include-toplevel:"
directive rather than the "include:" directive. This should probably be
mentioned in the bullseye release notes
9 matches
Mail list logo
