Package Details: python-cartopy 0.22.0-1

Git Clone URL: https://aur.archlinux.org/python-cartopy.git (read-only, click to copy)
Package Base: python-cartopy
Description: A cartographic Python library with Matplotlib support for visualisation
Upstream URL: https://scitools.org.uk/cartopy/
Licenses: LGPL3
Submitter: gauteh
Maintainer: gauteh (bcb)
Last Packager: bcb
Votes: 10
Popularity: 0.006799
First Submitted: 2015-11-16 16:00 (UTC)
Last Updated: 2023-12-08 10:43 (UTC)

Pinned Comments

bcb commented on 2023-12-08 10:48 (UTC)

The currently enabled tests pass (repeatedly) for me in a clean chroot. I am reluctant to disable too many tests in the PKGBUILD, especially when I cannot reproduce the failures and make sure I am disabling the correct test for a build failure reported by somebody else. For now, if you run into failures you may have to build with --nocheck. I am hoping to make the checks more robust -- suggestions welcome!

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Polly commented on 2023-01-02 17:07 (UTC) (edited on 2023-01-02 17:11 (UTC) by Polly)

@bcb Absolutely the right package to report. After building from AUR (without the checks) and upon import I get the following:

libpodofo.so.0.9.8: cannot open shared object file: No such file or directory libpodofo.so.0.9.8: cannot open shared object file: No such file or directory libarrow_dataset.so.1000: cannot open shared object file: No such file or directory libarrow_dataset.so.1000: cannot open shared object file: No such file or directory libarrow.so.1000: cannot open shared object file: No such file or directory libarrow.so.1000: cannot open shared object file: No such file or directory libpodofo.so.0.9.8: cannot open shared object file: No such file or directory libpodofo.so.0.9.8: cannot open shared object file: No such file or directory libarrow_dataset.so.1000: cannot open shared object file: No such file or directory libarrow_dataset.so.1000: cannot open shared object file: No such file or directory libarrow.so.1000: cannot open shared object file: No such file or directory libarrow.so.1000: cannot open shared object file: No such file or directory

My system is up to date as of today (2023/01/02).

bcb commented on 2022-09-16 09:50 (UTC)

Hi @user20159,

Sorry for the delay, I was out of town.

This is due to a recent change in the build directory setuptools uses, see https://github.com/pypa/setuptools/commit/1c23f5e1e4b18b50081cbabb2dea22bf345f5894

This should be fixed by the new package I have just pushed.

bcb commented on 2022-09-16 09:46 (UTC)

Hi @Polly,

Are you sure you reported this on the correct package? There is no mention of such libraries in the documentation, and using grep on the source doesn't find any imports of libraries named podofo or arrow. podofo seems to be a PDF manipulation library which isn't particularly relevant to cartopy, and arrow is a date/time library which cartopy doesn't seem to use.

user20159 commented on 2022-09-06 20:28 (UTC)

Hi everyone, thanks for packaging this! However, check() fails for me with:

line 41: cd: Cartopy-0.20.3/build/lib.linux-x86_64-3.10: No such file or directory

The correct name for the directory in my case is:

build/lib.linux-x86_64-cpython-310/

Am I the only one having this issue?

Polly commented on 2022-09-02 12:19 (UTC)

There seem to be two missing dependencies: podofo and arrow.

Xavier commented on 2022-07-28 07:02 (UTC)

Hi @bcb thanks for your answer and for maintain this package, I know how to avoid it and the different options for AUR helpers, It's quite annoying for a normal user to wait for more than 650 tests to install a simple lib, I forgot to mention that it was only my humble opinion, disable by default for users and keep it for a check on every release for maintainers. However, it's ok to keep those tests, you are the current maintainers. Thanks again and regards!

bcb commented on 2022-07-28 06:25 (UTC) (edited on 2022-07-28 06:26 (UTC) by bcb)

Hi @XavierCLL,

As per the wiki:

check()

Place for calls to make check and similar testing routines. It is highly recommended to have check() as it helps to make sure software has been built correctly and works fine with its dependencies.

Users who do not need it (and occasionally maintainers who can not fix a package for this to pass) can disable it using BUILDENV+=('!check') in PKGBUILD/makepkg.conf or call makepkg with --nocheck flag.

I have disabled a few image comparison tests which always seem to fail. The rest pass for me, on two different computers and in a clean chroot. At some point I would like to find a more reliable arrangement to allow these image comparisons to pass but I am not sure how straightforward that would be as the failures are often very small shifts in position rather than real errors.

In the meantime, I think the remaining ~650 tests are a useful check of the package's behaviour. You can edit /etc/makepkg.conf or use makepkg --nocheck as stated above if you wish to skip the checks on your machine (if you use an AUR helper, see if they have an equivalent option; yay uses --mflags to pass options to makepkg so you could use yay --mflags --nocheck -S python-cartopy for example).

Xavier commented on 2022-07-28 00:46 (UTC)

Hi @gauteh and @bcb, I think running the tests is more for the CI, development cycle and package maintainers but not for users. Right now the tests for this package are generating more cons than pros. Please disable it, thanks

krisboorger commented on 2021-12-10 19:57 (UTC)

The package doesn't build. Two tests fail. Here's the output: https://pastebin.com/c60aWGt2

The images referenced in the error log have a few lines shifted, compared to the ones expected by the test, if that helps with anything.

Downloaded this package using yay, so all dependencies listed here should be installed on my machine.

richli commented on 2019-08-27 23:54 (UTC)

@bcb: Thank you! I've included your hack into the PKGBUILD and disabled the tests for now.