From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Bruno Victal <mirai@makinata.eu>, 61570@debbugs.gnu.org
Subject: bug#61570: Backward incompatible changes in mpd-service-type
Date: Tue, 07 Mar 2023 06:31:43 +0100 [thread overview]
Message-ID: <e8c36c4f16827c00b2634723591f1a64c508efc3.camel@gmail.com> (raw)
In-Reply-To: <87bkl5z7lt.fsf@gmail.com>
Am Montag, dem 06.03.2023 um 20:13 -0500 schrieb Maxim Cournoyer:
> > Am Freitag, dem 17.02.2023 um 07:53 -0500 schrieb Maxim Cournoyer:
> > > Else an error rather than a warning when multiple same-name users
> > > are defined would be more appropriate, I think.
> > Guess what, it used to be a formatted message (i.e. an actual
> > error). However, that broke some configs as reported in [1], so I
> > demoted it to a warning.
>
> Interesting. I didn't know we were usefully (?) abusing duplicate
> users and group.
As far as I'm aware, we aren't. Even if such uses exist, they raise
said warning and probably cause more issues down the line, like with
your bug report.
> Perhaps we should try to isolate the most common offenders
> (services?), fix them up, and then re-introduce the check, perhaps
> gradually (e.g. "in 6 months time, duplicated users or groups will
> become a configuration error").
The only instance known to me (cups creating a duplicate lp group) was
fixed back in 2021.
Cheers
next prev parent reply other threads:[~2023-03-07 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 12:53 bug#61570: Backward incompatible changes in mpd-service-type Maxim Cournoyer
2023-02-17 15:33 ` Bruno Victal
2023-02-17 18:06 ` Liliana Marie Prikler
2023-03-07 1:13 ` Maxim Cournoyer
2023-03-07 5:31 ` Liliana Marie Prikler [this message]
2023-02-18 17:42 ` bug#61570: [PATCH] services: mpd: Use proper records Liliana Marie Prikler
2023-02-19 13:54 ` Bruno Victal
2023-02-25 20:13 ` Maxim Cournoyer
2023-04-02 14:42 ` bug#61570: control-msg Bruno Victal
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8c36c4f16827c00b2634723591f1a64c508efc3.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=61570@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=mirai@makinata.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).