Search Criteria
Package Details: autokey-common 0.96.0-7
Package Actions
Git Clone URL: | https://aur.archlinux.org/autokey.git (read-only, click to copy) |
---|---|
Package Base: | autokey |
Description: | A desktop automation utility for Linux and X11 - common data |
Upstream URL: | https://github.com/autokey/autokey |
Licenses: | GPL-3.0-or-later |
Conflicts: | autokey |
Provides: | autokey |
Submitter: | dark-saber |
Maintainer: | yochananmarqos |
Last Packager: | yochananmarqos |
Votes: | 69 |
Popularity: | 0.000192 |
First Submitted: | 2019-02-12 12:21 (UTC) |
Last Updated: | 2024-12-23 17:57 (UTC) |
Dependencies (14)
- imagemagick (imagemagick-gitAUR, imagemagick-full-gitAUR, imagemagick-fullAUR)
- python-dbus
- python-magic (python-magic-gitAUR)
- python-packaging
- python-pyinotify
- python-xlib
- wmctrl
- xautomation
- xorg-xwd
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-pyqt5 (python-pyqt5-sip4AUR, python-pyqt5-webkitAUR) (make)
- python-setuptools (make)
- python-wheel (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 14 Next › Last »
JoeSchr commented on 2020-11-29 12:50 (UTC) (edited on 2020-11-29 12:51 (UTC) by JoeSchr)
Hi, would it be possible to at this dependency:
python-qscintilla-qt5
It was missing and because of this
autokey-qt
wasn't working. See here: autokey/issues/475Thanks and great work!
EDIT: Ah sorry, I just saw, it's alread in optional dependencies, sorry about that
lateparty commented on 2020-11-13 00:19 (UTC)
@yochananmarqos yes please! thank you. I feel like I'm going to see a dark saber on the Mandalorian again before I get a response from the package owner here :(
yochananmarqos commented on 2020-11-12 21:39 (UTC)
I fixed my PKGBUILD if anyone is interested.
lateparty commented on 2020-10-17 14:19 (UTC)
@dark-saber using the current version, and did a rebuild, and I am still experiencing Traceback issues when opening autokey-qt from the terminal.
yochananmarqos commented on 2019-12-06 19:11 (UTC)
@dark-saber: I've updated my split-package PKGBUILD. It's actually proper this time and mimics the contents of the Debian packages of the same names. The only way I can see to avoid duplicate / conflicting files is to remove them manually.
dark-saber commented on 2019-11-19 00:05 (UTC)
ronjouch:
Yes, I've run into that with yay. Clearing the pkgdest or using
yay -S --rebuild autokey
seems to do the trick for me.ronjouch commented on 2019-11-18 02:36 (UTC)
Thanks @dark-saber.
I had rebuilt and it didn't solve the issue. I guess my AUR helper (yay) must maintain a cache and the simple rebuild I did must have failed to bust its cache.
Anyway, problem addressed with 0.95.8-2 :)
dark-saber commented on 2019-11-17 23:48 (UTC)
Thanks, ectospasm.
Yeah, usually you have to rebuild all foreign (AUR) python packages after major python upgrades.
pacman -Qqm
may be helpful.I've bumped the pkgrel to make sure everyone has rebuilt the package, but if I understand it correctly the philosophy of AUR is it's a user's responsibility to rebuild packages after the updates of their dependencies.
ectospasm commented on 2019-11-17 23:31 (UTC)
I changed directory to ~/.local/share/pikaur/aur_repos/autokey, and ran
makepkg -sri
to rebuild the package. That worked. This upstream issue defines the problem @ronjouch and I were getting:https://github.com/autokey/autokey/issues/323
Make sure you rebuild the package. Apparently my AUR helper (
pikaur
) wasn't doing that properly after the change to Python3.8.ronjouch commented on 2019-11-17 19:12 (UTC)
Same issue as user ectospasm since Arch's Python 3.8 upgrade. Re-building the package from PKGBUILD does not address the issue.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 14 Next › Last »