Package Details: solaar-git 1.1.7rc2.r0.gf539ac06-1

Git Clone URL: (read-only, click to copy)
Package Base: solaar-git
Description: Device manager for Logitech's Unifying receiver peripherals
Upstream URL:
Licenses: GPL2
Conflicts: solaar
Provides: solaar
Submitter: Max-P
Maintainer: Max-P
Last Packager: Max-P
Votes: 42
Popularity: 0.77
First Submitted: 2015-10-02 22:37 (UTC)
Last Updated: 2022-10-31 02:08 (UTC)

Latest Comments

1 2 3 4 Next › Last »

class101 commented on 2022-11-07 18:52 (UTC) (edited on 2022-11-07 18:57 (UTC) by class101)


In case you haven't seen my report

python-hid-parser-git needs to be fixed to get ride of the endless update 0.0.3 > 0.0.4=0.0.3 > 0.0.4=0.0.3 etc...

the pkgver() method produces a different version 0.0.3 than what you set in PKGBUILD 0.0.4

Nor there is a missing Git tag 0.0.4 at, nor you have to go back to 0.0.3 in the PKGBUILD

Max-P commented on 2022-10-31 02:10 (UTC)

@lgm This makes more sense as a separate package, so I've created python-hid-parser-git and added it as a dependency.

It seems to be optional for now, but I imagine this might not be the case forever if this is a recent introduction so I made it a required dependency to ensure full support for features that may depend on it.

lgm commented on 2022-10-17 18:49 (UTC) (edited on 2022-10-17 18:50 (UTC) by lgm)

solaar now contains a submodule As per, I think a patch should look as follows:

diff --git a/PKGBUILD b/PKGBUILD
index e53e57f..1718d22 100644
@@ -3,7 +3,7 @@
 # Contributor: Victor Häggqvist <aur a snilius d com>

 pkgdesc="Device manager for Logitech's Unifying receiver peripherals"
@@ -24,14 +24,25 @@ depends=(
 optdepends=('libappindicator-gtk3: tray icon support')
+        "git+"
+      )
+            'SKIP'
+            )

 pkgver() {
   cd "${pkgname}"
   git describe --long | sed 's/\([^-]*-g\)/r\1/;s/-/./g'

+prepare() {
+  cd ${pkgname}
+  git submodule init
+  git config submodule.externals/vendor/python-hid-parser.url "$srcdir/mysubmodule"
+  git submodule update
 build() {
   cd "${pkgname}"
   python build

EDIT: I tested this patch and it works for me

crypt0ninja commented on 2022-04-22 10:42 (UTC) (edited on 2022-04-22 18:38 (UTC) by crypt0ninja)

Getting the following error during build as of yesterday:

install: cannot stat 'ChangeLog': No such file or directory '' -> '/var/tmp/pamac-build-crypt0ninja/solaar-git/pkg/solaar-git/usr/share/doc/solaar-git/' ==> ERROR: A failure occurred in package(). Aborting...

UPDATE: changing ChangeLog to in PKGBUILD resolves the issue.

HC6505 commented on 2022-03-27 10:53 (UTC)

Latest version needs python-evdev

solaar: error: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/solaar/", line 158, in main import solaar.ui as ui File "/usr/lib/python3.10/site-packages/solaar/ui/", line 101, in <module> from . import diversion_rules, notify, tray, window # isort:skip # noqa: E402 File "/usr/lib/python3.10/site-packages/solaar/ui/", line 30, in <module> from logitech_receiver import diversion as _DIV File "/usr/lib/python3.10/site-packages/logitech_receiver/", line 28, in <module> import evdev ModuleNotFoundError: No module named 'evdev'

lgm commented on 2021-12-20 17:39 (UTC)

The name of the changelog file changed from ChangeLog to, causing the package build to fail.

jose1711 commented on 2021-08-23 20:44 (UTC)

please ship with language files ( thanks

lgm commented on 2020-12-02 16:46 (UTC)

solaar has the following new dependencies: python-yaml, python-xlib python-psutil. Please update the PKGBUILD accordingly.

mar04 commented on 2020-05-14 19:44 (UTC)

This package installs the same udev rule in two places, remove the one in /etc.

Max-P commented on 2020-05-13 23:14 (UTC)

@yochananmarqos Added the optional dependency, which also bumps the version of the package.

That seems to be an issue with how upstream labeled this release candidate and the previous one: 1.0.2.rc1 vs 1.0.2rc2. One has it as a second dot number, while the other has 2rc2 as a whole. That probably messes with the way pacman parses the version number.

I'm not sure how to handle this without getting rid of the version number and reverting back to the commit number. Since the version number comes from the tag, and the version number is first in the version string, I can't fix this without prepending something to override that version number from upstream.

Hopefully upstream remains consistent and the version number change I just pushed fixes it for a while. I suspect that might break again on the 1.0.2 release, because 1.0.2 will be > 1.0.2.rc2.

I'll add an epoch if this keeps breaking, or update the package version again as new versions gets released upstream.