Github messages for voidlinux
 help / color / mirror / Atom feed
From: NeelChotai <NeelChotai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Solaar: update to 1.0.7, install udev rules
Date: Tue, 12 Oct 2021 11:38:20 +0200	[thread overview]
Message-ID: <20211012093820.iX6myBOGthZcLDysPfiQa9Td6z6o3NCUhZS5sEmpGTM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33425@inbox.vuxu.org>

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

There is an updated pull request by NeelChotai against master on the void-packages repository

https://github.com/NeelChotai/void-packages Solaar-update
https://github.com/void-linux/void-packages/pull/33425

Solaar: update to 1.0.7, install udev rules
Fixes #33422.

Solaar currently runs with the error message:
```
ERROR: Solaar depends on a udev file that is not present.
For more information see the Solaar installation directions
at https://pwr-solaar.github.io/Solaar/installation
```

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/33425.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-Solaar-update-33425.patch --]
[-- Type: text/x-diff, Size: 1631 bytes --]

From f715081a154d5a8c47be53559484e63dd9c22572 Mon Sep 17 00:00:00 2001
From: Neel Chotai <neel.chotai@hyperexponential.com>
Date: Fri, 8 Oct 2021 17:21:04 +0100
Subject: [PATCH] Solaar: update to 1.0.7

---
 srcpkgs/Solaar/INSTALL.msg | 6 ++++++
 srcpkgs/Solaar/template    | 4 ++--
 2 files changed, 8 insertions(+), 2 deletions(-)
 create mode 100644 srcpkgs/Solaar/INSTALL.msg

diff --git a/srcpkgs/Solaar/INSTALL.msg b/srcpkgs/Solaar/INSTALL.msg
new file mode 100644
index 000000000000..a09ce30882e5
--- /dev/null
+++ b/srcpkgs/Solaar/INSTALL.msg
@@ -0,0 +1,6 @@
+Solaar depends on a udev file available at
+/usr/share/solaar/udev-rules.d/42-logitech-unify-permissions.rules. You may
+want to install this file to /usr/lib/udev/rules.d/ and reload udev rules.
+
+This behaviour may not be desirable on multi-user systems as it grants write 
+permissions to any seated user.
diff --git a/srcpkgs/Solaar/template b/srcpkgs/Solaar/template
index 393cede0f0ae..9377d7a11fa6 100644
--- a/srcpkgs/Solaar/template
+++ b/srcpkgs/Solaar/template
@@ -1,6 +1,6 @@
 # Template file for 'Solaar'
 pkgname=Solaar
-version=1.0.6
+version=1.0.7
 revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -10,6 +10,6 @@ maintainer="Young Jin Park <youngjinpark20@gmail.com>"
 license="GPL-3.0-or-later"
 homepage="https://pwr-solaar.github.io/Solaar/"
 distfiles="https://github.com/pwr-Solaar/Solaar/archive/${version}.tar.gz"
-checksum=fb879136911978f8f0183262a86f2b47a50b1816516599ae9a6681ad1d9a4e49
+checksum=39c025b4186b6cb4620bc52d1d20e2d841082982c8be0fed155398faee7a9cd1
 # Package provides no tests
 make_check=no

  parent reply	other threads:[~2021-10-12  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 16:32 [PR PATCH] " NeelChotai
2021-10-09  0:52 ` ahesford
2021-10-09 15:46 ` NeelChotai
2021-10-12  9:38 ` NeelChotai [this message]
2021-10-12  9:39 ` Solaar: update to 1.0.7 NeelChotai
2021-10-12 10:53 ` [PR REVIEW] " ahesford
2021-10-12 11:04 ` [PR PATCH] [Updated] " NeelChotai
2021-10-12 11:04 ` [PR REVIEW] " NeelChotai
2021-10-12 11:12 ` ahesford
2021-10-12 13:04 ` [PR PATCH] [Updated] " NeelChotai
2021-10-12 13:05 ` NeelChotai
2021-10-12 13:22 ` [PR PATCH] [Merged]: " ahesford

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=20211012093820.iX6myBOGthZcLDysPfiQa9Td6z6o3NCUhZS5sEmpGTM@z \
    --to=neelchotai@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).