Arch Linux User Repository

Starting with 4.0.0.dev8+434.g60779ea-1, the main entry point has been changed to isolate plugins install, similarly to how they are handled when using the official AppImage.

The plugins manager is available as a separate package: https://aur.archlinux.org/packages/plover_plugins_manager/.

Flagged out-of-date, due to missing dependencies. Here is a diff for those that want to install in the meantime.

diff --git PKGBUILD PKGBUILD index 8221c5f..1e338a5 100644 --- PKGBUILD +++ PKGBUILD @@ -10,9 +10,14 @@ depends=(    'dbus'    'python'    'python-appdirs' +  'python-evdev' +  'python-pkginfo'    'python-plover_stroke>=1.1.0'    'python-pyqt5'    'python-pyserial' +  'python-readme-renderer' +  'python-requests-cache' +  'python-requests-futures'    'python-rtf_tokenize'    'python-setuptools'    'python-wcwidth' @@ -21,13 +26,13 @@ depends=(  )  makedepends=(    'git' +  'pyside6-tools-wrappers'    'python-babel'    'python-build'    'python-installer'    'python-mock'    'python-pytest'    'python-pytest-qt' -  'python-pytest-xvfb'    'python-wheel'  )  provides=('plover') @@ -55,7 +60,7 @@ build() {   check() {    cd "$pkgname" -  PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest -p pytest-qt -p xvfb test +  PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest -p pytest-qt test  }   package() { 

I disabled xvfb on Wayland, but X11 I was able to build with it. All other changes were needed.

It seems python-pytest-xvfb isn't required at all.

diff --git a/PKGBUILD b/PKGBUILD index 8221c5f..161486a 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -2,7 +2,7 @@   pkgname=plover-git  pkgdesc="Free and open source real-time stenography engine." -pkgver=4.0.0.dev12 +pkgver=4.0.0rc2+8.g9b5a357f  pkgrel=1  arch=('any')  license=('GPL2') @@ -27,7 +27,6 @@ makedepends=(    'python-mock'    'python-pytest'    'python-pytest-qt' -  'python-pytest-xvfb'    'python-wheel'  )  provides=('plover') @@ -55,7 +54,7 @@ build() {   check() {    cd "$pkgname" -  PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest -p pytest-qt -p xvfb test +  PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest -p pytest-qt test  }   package() { 

could not find all required packages: python-pytest-xvfb 

Some comments, for others who have problems with building this package, here's what I did:

1. Rebuilding python-rtf_tokenize and python-plover_stroke helped in removing all expected errors. It seems like indeed my system has updated Python, and building these various AUR-based Python dependencies needs to be done with the same version as the one that this package gets built with.
2. I said "expected errors", because I had some additional unexpected errors, caused entirely by the fact that I symlink my ~/.local/share/plover/user.json. This symlinking causes two of the tests to get confused, breaking the check(). Without making any comment on whether this should break the tests of the package or not: if you want to make the package build, replace the symlink to user.json with the actual file, for the duration of the building of the package. After building, you can symlink it again.

@laura7089: which aur helper are you using? Was python-plover_stroke already installed or built? Check if it was built for an older Python version:

▹ pacman --query --list python-plover_stroke python-plover_stroke /usr/ python-plover_stroke /usr/lib/ python-plover_stroke /usr/lib/python3.11/ python-plover_stroke /usr/lib/python3.11/site-packages/ python-plover_stroke /usr/lib/python3.11/site-packages/__pycache__/ python-plover_stroke /usr/lib/python3.11/site-packages/__pycache__/plover_stroke.cpython-311.opt-1.pyc python-plover_stroke /usr/lib/python3.11/site-packages/_plover_stroke.cpython-311-x86_64-linux-gnu.so python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke-1.1.0.dist-info/ python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke-1.1.0.dist-info/METADATA python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke-1.1.0.dist-info/RECORD python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke-1.1.0.dist-info/WHEEL python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke-1.1.0.dist-info/top_level.txt python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke-1.1.0.dist-info/zip-safe python-plover_stroke /usr/lib/python3.11/site-packages/plover_stroke.py 

Same with python-rtf_tokenize. If that's the case, do a clean re-build/install of those before trying to install plover-git again.

Getting a check() failure:

ImportError while loading conftest '<build-dir>/plover-git/src/plover-git/test/conftest.py'. test/conftest.py:8: in <module>     from plover import system plover/system/__init__.py:8: in <module>     from plover.steno import Stroke plover/steno.py:12: in <module>     from plover_stroke import BaseStroke E   ModuleNotFoundError: No module named 'plover_stroke' 

Unfortunately cleaning the cached repo doesn't seem to affect this.

I'm running into an issue installing this package during check():

This resolved itself after I removed cached build files (yay -Sc) and reinstalled

I'm running into an issue installing this package during check():

Successfully built plover-4.0.0.dev12+18.ge6516275-py3-none-any.whl ==> Starting check()... ImportError while loading conftest '/home/austin/.cache/yay/plover-git/src/plover-git/test/conftest.py'. test/conftest.py:8: in <module>     from plover import system plover/system/__init__.py:8: in <module>     from plover.steno import Stroke plover/steno.py:12: in <module>     from plover_stroke import BaseStroke E   ModuleNotFoundError: No module named 'plover_stroke' ==> ERROR: A failure occurred in check().     Aborting...  -> error making: plover-git-exit status 4  -> Failed to install the following packages. Manual intervention is required: plover-git - exit status 4 

python-plover_stroke does seem to be getting installed; however, I can reproduce the failure in a python repl:

Python 3.11.5 (main, Sep  2 2023, 14:16:33) [GCC 13.2.1 20230801] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import plover_stroke Traceback (most recent call last):   File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'plover_stroke' 

Has anyone else encountered this error?

This is not how you write a pkgver() function for a VCS package, it needs to uniquely refer to the latest commit on the main branch (not just a general version). I suggest checking the wiki page on this topic.

Also renaming the source from plover to plover-git seems unnecessary here.

Trying to upgrade fromplover-4.0.0.dev11+21.g486a032f-1 to *.g486a032-1, it errors during the check() phase,

>       assert config_file.read_text(encoding='utf-8').strip() == dedent_strip(resulting_contents) E       assert '[System: Eng..."main.json"}]' == '[System: Eng..."main.json"}]' E         Skipping 61 identical leading characters in diff, use -v to show E         -  "path": "user.json"}, {"enabled": true, "path": "commands.json"}, {"enabled": true, "path": "main.json"}] E         +  "path": "~/.dotfiles/plover_user_dict.json"}, {"enabled": true, "path": "commands.json"}, {"enabled": true, "path": "main.json"}] E         ?           +++++++++++++++++++    +++++  test/test_config.py:505: AssertionError ============================== warnings summary =============================== test/test_blackbox.py::TestsBlackbox::test_after_initial_being   /usr/lib/python3.10/site-packages/packaging/specifiers.py:255: DeprecationWarning: Creating a LegacyVersion has been deprecated and will be removed in the next major release     warnings.warn(  -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info =========================== FAILED test/test_config.py::test_config[legacy_dictionaries_1] - assert '[Sy... FAILED test/test_config.py::test_config[legacy_dictionaries_2] - assert '[Sy... ================== 2 failed, 1165 passed, 1 warning in 3.58s ================== ==> ERROR: A failure occurred in check(). 

(I just copied the part that was highlighted red +1 line before, there seems to be a bunch of things which work normally before this)

Edit: I changed from a softlink to naming the full path of my user dictionary in the config file, and the error disappeared. My bad.