Arch Linux User Repository

PSA: Like most of the PKGBUILDs that I (co-)maintain, I host prebuilt packages for this in my user repository and all its dependencies for those who wish to install it using pacman without messing around with building from the AUR. Issues or contributions are welcome either in comments below or via this GitHub repository.

@rodneyck ~~~Standby, my check build with extra-x86_64-build didn't actually run check() because python-fontparts is not in [community].~~~ I'll look into this a little more, but still those questions I asked might be relevant.

Edit: Yes I need to know what method you are building with. This has an override in it to disable checks because it is part of a circular loop, and it is the part of the loop where the check() rather than the actual build() is affected. This shouldn't be running the check function at all unless you have an aggressive override in place to do so. If you let me know how you are building I'll look into why the override isn't working for you.

@rodneyck I just finished making the rounds and am back to look at this. I had another look and am not able to confirm your issue.

I just tried building this using extra-x86_64-build (which builds in a clean chroot using only repositories core/extra/community available for dependencies) and it builds cleanly. Of course I also build it using my own custom makechrootpkg that also has access to the repository of packages I've built, and also using makepkg on one of my machines. All of these work fine and don't show the error you are seeing.

Can you offer any more insight as to your build environment? Are you using an AUR helper? It's curious that you make trouble with the check function not being able to find itself.

@rodneyck Give me a few more hours to finish some cleanup and then I'll start from the top and check your error.

Getting an error building from AUR...

E ModuleNotFoundError: No module named 'fontPens' =========================== short test summary info ============================ ERROR tests/test_BooleanGlyph.py - ModuleNotFoundError: No module named 'font... ERROR tests/test_BooleanGlyph.py !!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!! ============================== 2 errors in 0.08s =============================== ==> ERROR: A failure occurred in check(). Aborting... rm -rf /tmp/bauh/arch/build_1628003738

Package "python-booleanoperations" upgrade failed

@randomguy343, @MarsSeed, @yochananmarqos, @djmattyg007, and any others with circular dep problems building/installing Python font packages. I think the loop is broken now. If you have any trouble do drop a comment or issue.

PSA: Like most of the PKGBUILDs that I (co-)maintain, I host prebuilt packages for this in my user repository and all its dependencies for those who wish to install it using pacman without messing around with building from the AUR. Issues or contributions are welcome either in comments below or via this GitHub repository.

@randomguy343 You can build by using --nocheck somewhere in the dependency loop to get one package started.

@thrasibule This is an ongoing problem for people trying to break into the loop. I realize this is bad dev practice in the upstream projects that depends on consumer libraries for testing, but that's what we have to work with. Disabling the check() functions by default using options=(!check) would be appropriate. The testing isn't really even testing that the package works right, only that the upstream regression suite passes in the build environment.

The packages python-fontpens, python-booleanoperations and python-fontparts create circular dependencies and can therefore neither be installed individually, nor together for me.

@MarsSeed. I don't understand, if you don't want to test, just disable the tests. That's what !check is for in /etc/makepkg.conf. But the package is not out of date.

Reported this PKGBUILD as 'out-of-date', requesting a PKBUILD fix asked for earlier by @yochananmarqos.

Quote from my request:

TLDR; Please kindly remove / comment out the 'checkdepends' variable.

Reasoning:
Build fails because of unneeded circular dependency.

The checkdepends is not needed here, since the check() function is disabled (commented out) in the PKGBUILD.
(Check is not necessary at all for consumer/end-user build.)

It is impossible to build this package specifically because of checkdepends=('python-fontparts'),
while python-fontparts' PKBUILD specifies checkdepends=('python-fontpens').
So this is a circular dependency.

The 'checkdepends' section can be safely deleted for this current package,
and it is necessary to do so for a successful build.