Package Details: qtile-git 0.33.0.r282.gc3d4510-1

Git Clone URL: https://aur.archlinux.org/qtile-git.git (read-only, click to copy)
Package Base: qtile-git
Description: A full-featured, pure-Python tiling window manager
Upstream URL: https://github.com/qtile/qtile
Licenses: MIT
Conflicts: qtile
Provides: qtile
Submitter: Mr.Elendig
Maintainer: xiota (elParaguayo)
Last Packager: elParaguayo
Votes: 69
Popularity: 0.000771
First Submitted: 2008-09-23 19:38 (UTC)
Last Updated: 2025-10-25 03:43 (UTC)

Pinned Comments

xiota commented on 2024-09-20 20:36 (UTC) (edited on 2025-08-05 06:52 (UTC) by xiota)

Re: The tests take a very long time to run.

When I adopted this package, checks were disabled. Upon enabling them, I saw a large number of failures. Leaving the checks enabled will prevent problems from going unnoticed.

Tests are now run in parallel, so they finish much faster. Don't know if it may cause spurious failures though.

Users who rebuild frequently may not need to run checks after every build. They may opt for one of the following:

  • Pass the --nocheck option to makepkg to skip the tests.
  • Configure makepkg to disable checks by default.
    • Edit the BUILDENV array in /etc/makepkg.conf.
    • Occasionally use the --check option.

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

elParaguayo commented on 2025-10-25 03:45 (UTC) (edited on 2025-10-25 03:46 (UTC) by elParaguayo)

@ltor - sorry about that. Left in the old link for testing before we released the new backend. Should be fixed now.

ltor commented on 2025-10-25 02:15 (UTC)

could not build qtile-git. error message below

-> Creating working copy of qtile git repo... Cloning into 'qtile'... done. fatal: invalid reference: origin/wayc ==> ERROR: Failure while creating working copy of qtile git repo Aborting... error: failed to build 'qtile-git-0.33.0.r278.g112f60e-1': error: packages failed to build: qtile-git-0.33.0.r278.g112f60e-1

elParaguayo commented on 2025-10-24 14:35 (UTC)

We've just released the new Wayland backend for qtile which replaces the old one.

I've added Wayland dependencies to makedepends so the Wayland backend is always built when installing this package.

If you have issues installing or with qtile itself, please post these on our github page and we'll get to them as soon as we can.

elParaguayo commented on 2025-08-05 07:48 (UTC)

@xiota Thanks for the comment. We looked at using pytest-xdist in our github repo to speed up the CI test suite. We could never get it to work either.

The tests do take a long time to run but hopefully users can take some comfort from the fact that we don't merge changes upstream unless the test suite runs correctly. That doesn't guarantee that it will run for users on their own system but it should mean we haven't inadvertently added things that completely break qtile!

xiota commented on 2025-08-05 06:48 (UTC) (edited on 2025-08-05 06:52 (UTC) by xiota)

Added python-pytest-xdist to run tests in parallel. They finish much faster now.

I'm seeing ~25 test failures. A lot seem to be related to wayland. Don't know whether they're significant.

elParaguayo commented on 2024-12-18 11:03 (UTC)

xiota - do you want me to take over ownership of this? I'm one of the qtile developers and also maintain the qtile-extras AUR packages.

xiota commented on 2024-09-20 20:36 (UTC) (edited on 2025-08-05 06:52 (UTC) by xiota)

Re: The tests take a very long time to run.

When I adopted this package, checks were disabled. Upon enabling them, I saw a large number of failures. Leaving the checks enabled will prevent problems from going unnoticed.

Tests are now run in parallel, so they finish much faster. Don't know if it may cause spurious failures though.

Users who rebuild frequently may not need to run checks after every build. They may opt for one of the following:

  • Pass the --nocheck option to makepkg to skip the tests.
  • Configure makepkg to disable checks by default.
    • Edit the BUILDENV array in /etc/makepkg.conf.
    • Occasionally use the --check option.

xiota commented on 2024-09-20 20:31 (UTC) (edited on 2024-09-20 20:50 (UTC) by xiota)

Aren't the tests run before merging to main?

While qtile may have a policy to never commit with failed pre-checks, not all projects do. Some projects don't always follow their own policies. Mistakes can happen.

So the repository could never be in a state where the tests would have failed.

There is at least one failed checkin shown in the commit history (currently on second page).

What's the point then in testing again on each install?

Even if upstream checks never failed, the local build environment may be different. Your config may be different from mine or any other users. So local checks could still fail.

bibermann commented on 2024-09-20 17:17 (UTC)

@xiota Aren't the tests run before merging to main? So the repository could never be in a state where the tests would have failed. What's the point then in testing again on each install? Just curious ;)

1 2 3 4 5 6 .. 11 Next › Last »