all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 45836@debbugs.gnu.org
Subject: bug#45836: cups-service-type duplicates lp group
Date: Wed, 13 Jan 2021 12:28:34 +0100	[thread overview]
Message-ID: <874kjlcbz1.fsf@gnu.org> (raw)
In-Reply-To: <a8a72caf989dc39752a4025c6035d82f346fe116.camel@student.tugraz.at> (Leo Prikler's message of "Wed, 13 Jan 2021 02:09:23 +0100")

Hi Leo,

Leo Prikler <leo.prikler@student.tugraz.at> skribis:

> it has come to my attention due to the recent reporting of #45830 and
> some conversation in IRC, that cups-service-type adds an lp group,
> which is already defined in %base-groups.  Since both share the same
> definition, this is not too big an issue, but it prohibits us from
> using a hard error for #45770.
>
> I can currently think of two solutions: Either remove the lp group from
> cups-service-type or remove it from base-groups.  Neither sounds
> particularly awesome.  Perhaps we could also delete identical
> duplicates before asserting that there are none for #45770, but that
> sounds like a little much effort.  Any ideas how else to solve this?

I’d be pragmatic here:

  1. Ignore duplicates that are identical (don’t report them).

  2. Remove “lp” from %base-groups since it has no use without CUPS
     (right?).

Thanks,
Ludo’.




  reply	other threads:[~2021-01-13 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  1:09 bug#45836: cups-service-type duplicates lp group Leo Prikler
2021-01-13 11:28 ` Ludovic Courtès [this message]
2021-01-13 12:06   ` Leo Prikler
2021-01-14 11:38     ` Ludovic Courtès
2021-01-14 13:06 ` bug#45836: [PATCH] services: Let cups-service-type reuse base " Leo Prikler
2021-01-16 18:37   ` Ludovic Courtès
2021-01-16 19:49     ` Leo Prikler
2021-01-18 14:47       ` Ludovic Courtès
2021-01-20  8:16         ` Leo Prikler

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=874kjlcbz1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=45836@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.