Package Details: python-fontpens 0.2.4-3

Git Clone URL: https://aur.archlinux.org/python-fontpens.git (read-only, click to copy)
Package Base: python-fontpens
Description: A collection of classes implementing the pen protocol for manipulating glyphs.
Upstream URL: https://github.com/robotools/$_pyname
Licenses: BSD
Submitter: thrasibule
Maintainer: alerque (thrasibule)
Last Packager: alerque
Votes: 4
Popularity: 1.08
First Submitted: 2019-08-18 01:37 (UTC)
Last Updated: 2021-12-14 08:48 (UTC)

Pinned Comments

alerque commented on 2021-08-03 15:18 (UTC)

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.

Latest Comments

alerque commented on 2021-12-16 10:13 (UTC)

@Alkaris In that case I think pacmac or your usage of it is broken. The package works fine. You can verify this by cloning this repository and building it with extra-x86_64-build which will use a clean chroot to build this from scratch. It currently works fine.

Alkaris commented on 2021-12-14 06:27 (UTC)

@alerque it's all done within Pamac. I've cleaned the cache and chroot in Pamac, but it always fails to install/upgrade.

alerque commented on 2021-12-11 19:52 (UTC) (edited on 2021-12-11 19:53 (UTC) by alerque)

@Alkaris I just double checked that this package builds in a clean chroot with no packages except the ones listed as dependencies then installed it as an upgrade, and it works just fine. What tooling are you using for your "Install/Upgrade"?

Alkaris commented on 2021-12-11 16:46 (UTC)

Upon Install/Upgrade it complains No module named 'FontPens' exists for Test Component. Like this shouldn't be an issue. The module exists within the package, yet it's trying to check for something that exists in it's own source files that it can't find. How does it expect to find the module on the system when it's in the source files?

======================================================================
ERROR: test_decompose_digest (fontParts.test.test_component.TestComponent)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/pamac-build-user/python-fontparts/src/fontParts-0.9.11/Lib/fontParts/test/test_component.py", line 695, in test_decompose_digest
    from fontPens.digestPointPen import DigestPointPen
ModuleNotFoundError: No module named 'fontPens'

this line is repeated multiple lines for test_component.py line 695, 733, 470, 485, and in another file for legacyPointPen.py at line 1 in <module>.

alerque commented on 2021-08-03 18:55 (UTC) (edited on 2021-08-03 19:05 (UTC) by alerque)

@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.

alerque commented on 2021-08-03 18:53 (UTC)

@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.

alerque commented on 2021-08-03 15:20 (UTC)

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

rodneyck commented on 2021-08-03 15:19 (UTC)

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

alerque commented on 2021-08-03 15:19 (UTC) (edited on 2021-08-03 15:19 (UTC) by alerque)

@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.

alerque commented on 2021-08-03 15:18 (UTC)

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.

alerque commented on 2021-06-02 16:38 (UTC)

@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.

randomguy343 commented on 2021-06-02 09:42 (UTC)

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

thrasibule commented on 2021-04-19 20:32 (UTC)

@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.

MarsSeed commented on 2021-04-19 16:30 (UTC) (edited on 2021-04-19 16:32 (UTC) by MarsSeed)

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.

yochananmarqos commented on 2020-06-14 02:39 (UTC)

@djmattyg007: I was talking about disabling the check for python-booleanoperations, not this package. Also, I'm not a maintainer, I was referring to my personal PKGBUILDs.

djmattyg007 commented on 2020-06-14 02:30 (UTC)

"I disabled the check() function for it for now"

As long as checkdepends is specified, AUR wrappers will still try to process these dependencies and run into issues with circular dependency trees. If you're going to comment out the check() function, it would be greatly appreciated if you could also comment out the checkdepends list.

yochananmarqos commented on 2019-12-17 01:16 (UTC) (edited on 2019-12-17 01:16 (UTC) by yochananmarqos)

Neither python-fontparts nor python-pytest are required for the test. fontParts will be downloaded from PyPi during the test. However, it does require python-booleanoperations, otherwise it fails. Problem is, python-booleanoperations requires python-fontpens for the test, so I disabled the check() function for it for now.

This also does not require python-unicodedata2 directly; instead it requires python-defcon which depends on it.

thrasibule commented on 2019-08-23 14:09 (UTC)

@caleb, these are only checkdepends. You can disable the tests on one to install both. These dependencies are not bogus, you can't run the tests without them.

alerque commented on 2019-08-23 12:45 (UTC)

Something is wrong here, python-fontparts depends on python-fontpens but python-fontpens depends on python-fontparts. That's circular and we can't have it both ways. One of these packages needs to drop the bogus dependency.