Arch Linux User Repository

@systemofapwne Thanks for following up. If you ever happen to find a fix, I’ll be happy to include it. Until then, feel free to skip check if it’s not helpful for you!

@Auerhuhn I can understand. I still regret my 6 years old choice on this specific machine.

Anyhow: I traced down the bug to issues with dbus. Specifically mounting "/run/user/1000/doc" for testing pre-build via pytest. It first looked like this issue https://github.com/labelle-org/labelle/issues/87 , but that was already fixed according to the labelle devs.

If I see this correctly, the check() function has been introduced only about 4 months ago in the PKGBUILD. After removing it, labelle just built without any issues and is running as expected.

@systemofapwne Sorry, I can’t help with Manjaro.

I see the same issue as @spease But I have to be clear here: I am on Manjaro (which is shitty in terms of keeping up with base Arch). System is up-to-date (what Manjaro maintainers define as up-to-date) and no broken python dependencies (checked it with checkrebuild)

_______________________________________________________________________________________________________________________________________________________ test session _______________________________________________________________________________________________________________________________________________________
mypy exited with status 2.
_____________________________________________________________________________________________________________________________________________________ test_main_window _____________________________________________________________________________________________________________________________________________________

qtbot = <pytestqt.qtbot.QtBot object at 0x7f4574928830>

    def test_main_window(qtbot: QtBot):
        widget = LabelleWindow()
        qtbot.addWidget(widget)

>       assert not widget._actions.isEnabled()
E       assert not True
E        +  where True = <built-in method isEnabled of QActions object at 0x7f45601696d0>()
E        +    where <built-in method isEnabled of QActions object at 0x7f45601696d0> = <labelle.gui.q_actions.QActions object at 0x7f45601696d0>.isEnabled
E        +      where <labelle.gui.q_actions.QActions object at 0x7f45601696d0> = <labelle.gui.gui.LabelleWindow object at 0x7f457494a990>._actions

src/labelle/gui/tests/test_gui.py:13: AssertionError
------------------------------------------------------------------------------------------------------------------------------------------------- Captured stderr teardown -------------------------------------------------------------------------------------------------------------------------------------------------
qt.accessibility.atspi: Error in contacting registry: "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not activate remote peer 'org.a11y.atspi.Registry': unit failed"

solved. thx.

Thx. Tried –rebuildtree but no change. Thanks for trying.

you can't have to fumble with updating a single aur package specifically. it's fine for testing, but in the end a simple "yay -Syu" has to work

@simona There seems to be a misunderstanding of what yay can do and what it can’t do. One would expect that yay should be smart enough to always do the right thing and always rebuild your Python packages properly, but in reality AUR helpers are nowhere near that smart. (The fact that most PKGBUILD maintainers never bother doing annual courtesy pkgrel bumps is also not exactly helpful.)

That’s why your expectation is unrealistic, and you’re going to have to either a) rebuild your dependency hierarchy yourself, or b) use the --rebuildtree option to have yay do it for you.

But there’s absolutely no way for yay -Syu to always work reliably in the face of a minor Python version upgrade.

And there’s nothing the labelle PKGBUILD can possibly do about it.

AUR helpers are not nearly as smart as you think they are. That’s why I suggested to install checkrebuild, because checkrebuild is that smart, and will warn you about the issue every time it happens.

you can't have to fumble with updating a single aur package specifically. it's fine for testing, but in the end a simple "yay -Syu" has to work

@spease I tried several times both on my development machine and in a clean chroot, but I can’t reproduce.

Does the build work in a clean chroot for you?

Getting the following error:

========================================== FAILURES ===========================================
______________________________________ test_main_window _______________________________________

qtbot = <pytestqt.qtbot.QtBot object at 0x7282f7125be0>

    def test_main_window(qtbot: QtBot):
        widget = LabelleWindow()
        qtbot.addWidget(widget)

>       assert not widget._actions.isEnabled()
E       assert not True
E        +  where True = <built-in method isEnabled of QActions object at 0x7282f702a5d0>()
E        +    where <built-in method isEnabled of QActions object at 0x7282f702a5d0> = <labelle.gui.q_actions.QActions object at 0x7282f702a5d0>.isEnabled
E        +      where <labelle.gui.q_actions.QActions object at 0x7282f702a5d0> = <labelle.gui.gui.LabelleWindow object at 0x7282f71f8690>._actions

src/labelle/gui/tests/test_gui.py:13: AssertionError
=================================== short test summary info ===================================
FAILED src/labelle/gui/tests/test_gui.py::test_main_window - assert not True
================================ 1 failed, 48 passed in 1.05s =================================

I have attempted running checkrebuild and updated all the dependencies it recommended.