Search Criteria
Package Details: rivalcfg 4.16.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/rivalcfg.git (read-only, click to copy) |
|---|---|
| Package Base: | rivalcfg |
| Description: | CLI tool and Python library to configure SteelSeries gaming mice |
| Upstream URL: | https://github.com/flozz/rivalcfg |
| Licenses: | custom:WTFPL |
| Submitter: | FFY00 |
| Maintainer: | FLOZz (tugyan) |
| Last Packager: | tugyan |
| Votes: | 17 |
| Popularity: | 0.63 |
| First Submitted: | 2018-05-26 15:21 (UTC) |
| Last Updated: | 2026-03-11 14:08 (UTC) |
Dependencies (6)
- hidapi (hidapi-gitAUR)
- python
- python-hidapi (python-hidapi-gitAUR)
- python-build (make)
- python-pip (make)
- python-setuptools (make)
Latest Comments
1 2 Next › Last »
FLOZz commented on 2026-03-11 19:23 (UTC)
Hello,
python-setuptoolsis not more a requirements of Rivalcfg:setup.pywas replaced bypyproject.tomland now the package relies on Flit instead of setuptools (but pip should handle that). :)ipaqmaster commented on 2023-07-09 11:18 (UTC)
Same issue here on my build server. Solved by force-rebuilding with the -f flag to makepkg.
I'm familiar with
importlib.metadata.PackageNotFoundError: No package metadata was found for rivalcfgappearing when a package is out of date compared with some other python environment which has been updated and this was another case of that.This package needs some way to check for that. Trying to rebuild rivalcfg with makepkg claims it doesn't need to because the package has already been built. In my case, that package was built 3 months earlier and while the version was the same, many python-relevant packages had moved on.
5ysk3y commented on 2023-05-06 09:21 (UTC) (edited on 2023-05-06 10:32 (UTC) by 5ysk3y)
I also had the afforementioned metadata issue but I was able to fix by completely removing rivalcfg and reinstalling it via my AUR helper.
cynikkk commented on 2023-05-05 07:21 (UTC) (edited on 2023-05-05 07:26 (UTC) by cynikkk)
Hello, after updating to last version (4.8.0-1) rivalcfg doesn't work anymore.
Python version and kernel :
importlibversion :tugyan commented on 2022-11-22 16:52 (UTC)
@FLOZz Awesome, thanks!
FLOZz commented on 2022-11-22 08:15 (UTC)
@tugyan you are now co-maintainer, you should be able to update the package. On my side, I will look for a solution to automate this :)
tugyan commented on 2022-11-22 08:00 (UTC)
@FLOZz You can put me as a maintainer. I can take care of the updates for the time being, until a better solution is found.
FLOZz commented on 2022-11-21 10:05 (UTC) (edited on 2022-11-21 13:27 (UTC) by FLOZz)
@tugyan You are right... I have been put maintainer on this package but I do not have enough time to maintain it... I see two possible solutions:
tugyan commented on 2022-11-18 07:36 (UTC)
@FLOZz Version 4.7.0 is out for 2 months. Any chance the package gets updated?
FLOZz commented on 2022-01-18 14:57 (UTC)
Oops I forget to save the file after updating the checksum... Is it better now?
1 2 Next › Last »