Github messages for voidlinux
 help / color / mirror / Atom feed
From: Gigahawk <Gigahawk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libsigrok: update to 0.5.2.
Date: Wed, 15 Jul 2020 05:24:28 +0200	[thread overview]
Message-ID: <20200715032428.H2zwnEn2FcOks6JLTE7xqIl5X5GhkorqCPCPCEP3tes@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23581@inbox.vuxu.org>

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

New comment by Gigahawk on void-packages repository

https://github.com/void-linux/void-packages/pull/23581#issuecomment-658523313

Comment:
Original udev rule uses `TAG+=uaccess` which doesn't seem to be supported due to not using systemd-logind. 

The repo provides a similar rules file that allows access for users in the `plugdev` group which is usually only present on Debian based distros, so I've made a copy of it for the `dialout` group instead.

Not sure if it's preferred to patch an existing file or to use some group other than `dialout`.

  reply	other threads:[~2020-07-15  3:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  3:20 [PR PATCH] " Gigahawk
2020-07-15  3:24 ` Gigahawk [this message]
2020-07-17  0:49 ` sgn
2020-07-28  1:43 ` [PR PATCH] [Updated] " Gigahawk
2020-07-28  1:45 ` Gigahawk
2021-01-18 22:09 ` [PR REVIEW] " ericonr
2021-09-20 15:49 ` paper42
2022-03-14 20:18 ` 0x5c
2022-03-14 20:20 ` 0x5c
2022-03-14 23:33 ` 0x5c
2022-03-14 23:37 ` Gigahawk
2022-03-14 23:51 ` 0x5c
2022-04-07  1:58 ` [PR PATCH] [Closed]: " abenson
2022-04-07  5:01 ` 0x5c
2022-04-07  5:02 ` Gigahawk

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=20200715032428.H2zwnEn2FcOks6JLTE7xqIl5X5GhkorqCPCPCEP3tes@z \
    --to=gigahawk@users.noreply.github.com \
    --cc=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).