From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libsigrok: fix missing plugdev group
Date: Sun, 20 Mar 2022 06:06:36 +0100 [thread overview]
Message-ID: <20220320050636.ilGm96CYkJ3Mi-omFHsev3xDU7kEv70KSHekd6H-FcM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36144@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
There is an updated pull request by 0x5c against master on the void-packages repository
https://github.com/0x5c/void-packages sigrok-plugdev
https://github.com/void-linux/void-packages/pull/36144
libsigrok: fix missing plugdev group
Fixes #23580
Closes #23581 (obsoletes the PR)
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/36144.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-sigrok-plugdev-36144.patch --]
[-- Type: text/x-diff, Size: 1040 bytes --]
From b8fe0ad34a8fcca48148ad4a91b45bb17c2320d4 Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Sun, 20 Mar 2022 00:41:04 -0400
Subject: [PATCH] libsigrok: fix on systems without logind
Fixes #23580
Closes #23581 (obsoletes the PR)
---
srcpkgs/libsigrok/template | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/libsigrok/template b/srcpkgs/libsigrok/template
index 87939ce82fa8..0243925a7312 100644
--- a/srcpkgs/libsigrok/template
+++ b/srcpkgs/libsigrok/template
@@ -1,7 +1,7 @@
# Template file for 'libsigrok'
pkgname=libsigrok
version=0.5.2
-revision=1
+revision=2
build_style=gnu-configure
hostmakedepends="pkg-config doxygen python3"
makedepends="glib-devel libzip-devel glibmm-devel libserialport-devel
@@ -20,6 +20,7 @@ esac
post_install() {
vinstall contrib/60-libsigrok.rules 0644 /usr/lib/udev/rules.d
vinstall contrib/61-libsigrok-uaccess.rules 0644 /usr/lib/udev/rules.d
+ vinstall contrib/61-libsigrok-plugdev.rules 0644 /usr/lib/udev/rules.d
}
libsigrok-devel_package() {
next prev parent reply other threads:[~2022-03-20 5:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 23:28 [PR PATCH] " 0x5c
2022-03-15 3:23 ` Duncaen
2022-03-15 19:55 ` q66
2022-03-15 19:56 ` q66
2022-03-15 20:44 ` 0x5c
2022-03-20 5:06 ` 0x5c [this message]
2022-03-20 5:13 ` 0x5c
2022-03-20 5:14 ` 0x5c
2022-03-29 10:10 ` [PR PATCH] [Updated] libsigrok: fix missing udev rules 0x5c
2022-04-06 22:47 ` 0x5c
2022-04-07 1:58 ` [PR PATCH] [Merged]: " abenson
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=20220320050636.ilGm96CYkJ3Mi-omFHsev3xDU7kEv70KSHekd6H-FcM@z \
--to=0x5c@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).