From: Michael Tremer <michael.tremer@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: [PATCH] unbound: Update to 1.25.1
Date: Thu, 21 May 2026 19:34:05 +0100 [thread overview]
Message-ID: <738EAC86-7C00-4756-AE11-492AA51C71AF@ipfire.org> (raw)
In-Reply-To: <65b7e7bb-b537-4719-b5a5-54213a9db089@ipfire.org>
Hello,
Not a problem at all. I merged it too quickly too. I just wanted to have this in the release as everything in that release looked so scary...
> On 21 May 2026, at 14:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>
> On 21.05.2026 15:29, Matthias Fischer wrote:
>> For details see:
>> https://nlnetlabs.nl/projects/unbound/download/#unbound-1-25-1
>> ...
>
> Sorry for the noise - I tested the new unbound-version with Core 201 and
> forgot to update the new ownerships!
>
> I'm going to sit in my deepest corner and feel ashamed...
>
>> - chown -Rv unbound:unbound /var/lib/unbound
>> + chown -Rv nobody.nobody /var/lib/unbound
>>
>> # Ship ICANN's certificates to validate DNS trust anchors
>> install -v -m 644 $(DIR_SRC)/config/unbound/icannbundle.pem \
>> @@ -117,7 +117,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>>
>> # Install the cache directory
>> -mkdir -pv /var/cache/unbound
>> - chown unbound:unbound /var/cache/unbound
>> + chown nobody:nobody /var/cache/unbound
>> ...
>
prev parent reply other threads:[~2026-05-21 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:29 Matthias Fischer
2026-05-21 13:58 ` Matthias Fischer
2026-05-21 18:34 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=738EAC86-7C00-4756-AE11-492AA51C71AF@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=matthias.fischer@ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox