public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f8a8123fee011c4772e1752becebe81f7ea8ee93
Date: Tue, 09 Jun 2026 15:34:00 +0000 (UTC)	[thread overview]
Message-ID: <4gZXy053Wvz2xjD@people01.haj.ipfire.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  f8a8123fee011c4772e1752becebe81f7ea8ee93 (commit)
      from  518a22e9fea84e768f1685a8fd92372e21627657 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit f8a8123fee011c4772e1752becebe81f7ea8ee93
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Tue Jun 9 16:34:00 2026 +0200

    update-rpzs: Also switch group to knot-resolver
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 src/scripts/update-rpzs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/src/scripts/update-rpzs b/src/scripts/update-rpzs
index 24d40c255..b3e457dc1 100644
--- a/src/scripts/update-rpzs
+++ b/src/scripts/update-rpzs
@@ -72,7 +72,7 @@ main() {
 		done
 
 		# Run the sync as unprivileged user
-		setpriv --reuid="knot-resolver" --init-groups \
+		setpriv --reuid="knot-resolver" --regid="knot-resolver" --init-groups \
 			zone-sync "${ZONE_SYNC_ARGS[@]}" --primary="${primary}"  "${zones[@]}" || failed=$?
 	done
 


hooks/post-receive
--
IPFire 2.x development tree


                 reply	other threads:[~2026-06-09 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4gZXy053Wvz2xjD@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.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