From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: muradm <mail@muradm.net>
Cc: 56971@debbugs.gnu.org
Subject: bug#56971: greeter user permissions are not enough to talk with seatd
Date: Fri, 05 Aug 2022 10:04:52 +0200 [thread overview]
Message-ID: <128b8b30d46a357318bad98c3f11bceb8adbb8ca.camel@ist.tugraz.at> (raw)
In-Reply-To: <87r11v18mk.fsf@muradm.net>
Am Freitag, dem 05.08.2022 um 09:48 +0300 schrieb muradm:
>
> Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
>
> > Am Donnerstag, dem 04.08.2022 um 15:52 +0300 schrieb muradm:
> > >
> > > Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
> > >
> > > > [...] [L]ooking at the two patches, it appears they are to
> > > > be used in combination?
> > > >
> > > No, technically they are not strongly dependent on each other,
> > > could be applied one after another in no particular order.
> > > After both are applied, in cooperation they address this issue.
> > This is what I'm saying, albeit in different words. As far as I
> > understand, neither of these patches really accomplishes
> > anything if
> > not put together. Thus, you more or less opened three issues to
> > address one.
> Really I don't know what to comment here else. My analysis showed
> two independent issues, one is that seatd should have a declared
> group so that users of it could join it. This issues is not
> specific to greetd/greeter in any way. Any other greeting mechanism
> could fall short on this.
But it is greetd that does, no? If there are other greeting mechanisms
currently packaged in Guix falling short of this, please do tell.
> And second, greeter today required conditional group to interact with
> seatd, or it could be any other group like input, usb, modem or else
> depending on user setup.
> Solutions are offered accordingly. Third issue, this bug I was
> asked to open. I don't understand, is it a sin to have multiple
> issues, or what is the problem here?
It is not really a problem, but an observation. I personally think a
single series that has both patches would have been more visible than
this thing split across three topics for two patches. There is a small
overhead if you have to consider merges and blocks, even if debbugs
supports them.
Cheers
next prev parent reply other threads:[~2022-08-05 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 9:45 bug#56971: greeter user permissions are not enough to talk with seatd muradm
2022-08-04 11:08 ` Liliana Marie Prikler
2022-08-04 12:52 ` muradm
2022-08-05 6:11 ` Liliana Marie Prikler
2022-08-05 6:48 ` muradm
2022-08-05 8:04 ` Liliana Marie Prikler [this message]
2022-08-07 20:48 ` muradm
2022-08-08 5:54 ` Liliana Marie 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
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=128b8b30d46a357318bad98c3f11bceb8adbb8ca.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56971@debbugs.gnu.org \
--cc=mail@muradm.net \
/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).