Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]:  libfido2: switch udev rules to the `plugdev` group
Date: Sun, 26 Feb 2023 03:06:35 +0100	[thread overview]
Message-ID: <20230226020635.XgdBL3t4NlIbGmX1dVUJsGRrM1K8YtZlLV1S4UUaBGs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39688@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

There's a closed pull request on the void-packages repository

 libfido2: switch udev rules to the `plugdev` group
https://github.com/void-linux/void-packages/pull/39688

Description:
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (x86-64_glibc)

@leahneukirchen

Embarrassingly, I spent a lot of time wondering why my U2F was not showing and then I noticed this switch in the template. 

Most other rules shipped by void, use `plugdev`, and the current docs imply that it should be `plugdev`.
 
```
plugdev | Access to pluggable devices.
users | Ordinary users.
```
from https://docs.voidlinux.org/config/users-and-groups.html




      parent reply	other threads:[~2023-02-26  2:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  0:48 [PR PATCH] libfido2: switch udev rules back to 'plugdev', revbump dmarto
2022-10-04  0:55 ` classabbyamp
2022-10-04  1:11 ` dmarto
2022-10-04  1:12 ` dmarto
2022-10-04  2:07 ` 0x5c
2022-10-04 12:35 ` dmarto
2022-10-04 12:52 ` leahneukirchen
2022-10-04 13:12 ` dmarto
2022-10-04 15:16 ` classabbyamp
2022-10-04 15:56 ` dmarto
2022-10-04 16:14 ` dmarto
2022-10-05 14:47 ` CameronNemo
2022-10-08 22:54 ` dmarto
2022-10-08 22:57 ` dmarto
2022-10-08 23:16 ` [PR PATCH] [Updated] " dmarto
2022-10-08 23:19 ` dmarto
2022-10-09  6:08 ` libfido2: add INSTALL.msg, revbump 0x5c
2022-10-09  6:09 ` classabbyamp
2022-10-09 11:30 ` leahneukirchen
2022-11-13  0:30 ` dmarto
2022-11-13  3:46 ` libfido2: switch udev rules to the `plugdev` group 0x5c
2022-11-13 15:38 ` CameronNemo
2023-02-12  2:01 ` github-actions
2023-02-26  2:06 ` github-actions [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=20230226020635.XgdBL3t4NlIbGmX1dVUJsGRrM1K8YtZlLV1S4UUaBGs@z \
    --to=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).