Arch Linux User Repository

ectospasm: For monitoring I'm just using the Update Scanner extension for Firefox for now. That's not ideal, I wanted to switch to something better, but too many projects are not on Github (yet? I see a certain trend), so I end up monitoring some random page with a changelog. For GitHub projects, I have some ugly script that downloads the latest release from Releases page, tries to build it and runs namcap, but that doesn't always work, sometimes people change the base filename or compression method over releases, sometimes they publish the latest releases not on GitHub, but in other places for whatever reason. Then I'm looking through the changelog and run the app (or app that uses the library) manually to check if it's broken, unless that's some minor release of a Python/Ruby library.

dark-saber: Nope, I missed something. In all the hubbub I had forgotten that I actually uninstalled the AUR package (the setup.py install method won't work otherwise). When I didn't see the update come across in my (pikaur) package list, I was alarmed and thought it hadn't updated. Hence my message.

I guess you have a script that polls GitHub for a new release so it builds automatically? Just curious on how that works.

ectospasm: The package was updated to 0.95.7 two hours before your comment. Did I miss something?

Version 0.95.7 was released by the upstream developer TODAY (2019-04-29). Please update the AUR accordingly, it contains a fix I need (bugfixes/issue_257).

This package should be renamed to autokey, as autokey-py3 has been merged upstream (autokey is written in Python3 now).

Also, there is an upstream branch (https://github.com/autokey/autokey/tree/bugfix/issue_257) which fixes an Xlib.error.BadAtom error I encountered with the AUR package released 2019-02-10T10:50 -05:00. I will be eagerly awaiting for upstream to merge this fix with master. The BadAtom error breaks the X loop for autokey, rendering at least typed abbreviations useless.

The upstream developer was EXTREMELY responsive. They gave an initial response within seconds of my post, and within 24 hours the bugfix was applied to a branch. I am extremely impressed by this.

Information for other users of KDE/oxygen-gtk: On Manjaro KDE with GTK3 theme oxygen-gtk the 'Main Window' doesn't display properly and I have to start with something like "GTK_THEME=Adwaita:Manjaro autokey-gtk". I don't know if this a problem with oxygen-gtk or Autokey. If anyone can help I could send verbose logging info.

Alright, with some more patching python-atspi becomes an optional dep again.

But if you need ATSPI on Gtk interface, you still have to install the python-atspi-git package, the error messages are silenced, but the package from extra/ won't work.

Python-atspi is broken in Arch at the moment, see https://bugs.archlinux.org/task/59547.

The git version of python-atspi is currently the same 2.26.0 version with the added fix to the async problem from https://gitlab.gnome.org/GNOME/pyatspi2/merge_requests/3. It should replace the extra/python-atspi without major issues.

I guess we'll have to keep the current state of things till the new release of pyatspi with the fix merged or till the package in extra/ gets patched, whichever comes first.

The issue with python-atspi is the git version needs to be released? I can't swith atspi versions as my gui needs the arch atspi. Have you tried getting the python-atspi maintainer to patch their version with the change needed?

Can't remove python-atspi since it's used for my graphical interface (cinnamon)

Package python-atspi will be removed due to a conflict with autokey-py3
:: Dependency python-atspi of package caribou is not fulfilled
:: Dependency caribou of package cinnamon is not fulfilled

But as you said Qt version work fine