Same as well. I use yay
so I had to install with yay --mflags --nocheck
.
Search Criteria
Package Details: python-cartopy 0.24.1-1
Package Actions
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: | BSD-3-Clause |
Submitter: | gauteh |
Maintainer: | gauteh (bcb) |
Last Packager: | bcb |
Votes: | 10 |
Popularity: | 0.000053 |
First Submitted: | 2015-11-16 16:00 (UTC) |
Last Updated: | 2024-11-22 12:04 (UTC) |
Dependencies (22)
- python-matplotlib (python-matplotlib-gitAUR)
- python-numpy (python-numpy-flameAUR, python-numpy-gitAUR, python-numpy1AUR, python-numpy-mkl-tbbAUR, python-numpy-mklAUR, python-numpy-mkl-binAUR)
- python-pillow (python-pillow-gitAUR)
- python-pyproj
- python-pyshpAUR
- python-scipy (python-scipy-gitAUR, python-scipy-mklAUR, python-scipy-mkl-tbbAUR, python-scipy-mkl-binAUR)
- python-shapely
- cython (cython-gitAUR, cython0AUR) (make)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-setuptools-scm (make)
- python-wheel (make)
- python-flufl-lock (check)
- python-pytest (check)
- python-pytest-mpl (check)
- python-beautifulsoup4 (optional) – for use with SRTM data
- python-fiona (optional) – faster shapefile reading
- python-gdal (python-gdal-ecwAUR, python-gdal-hdf4AUR, python-gdal-libkmlAUR, python-gdal-libkml-filegdbAUR) (optional) – for use with SRTM data
- python-owslib (optional) – access OGC clients
- python-pyepsgAUR (optional) – interface to https://epsg.io
- python-pykdtreeAUR (optional) – faster warping of images
Required by (14)
- pyqso (optional)
- pyresample (optional)
- python-alphashape
- python-argopy (optional)
- python-geoplot
- python-geoviews
- python-goes2go
- python-metpy (check)
- python-metpy (optional)
- python-nvector
- python-obspy (optional)
- python-xmovie
- pythonprop
- pythonprop-git
Sources (1)
alhirzel commented on 2023-06-07 21:44 (UTC)
Divert commented on 2023-05-28 01:02 (UTC)
I have the same problem as @carlosal1015
carlosal1015 commented on 2023-05-20 17:05 (UTC)
Hi, I have the following message error
==================================================================== short test summary info ====================================================================
FAILED cartopy/tests/test_crs.py::TestCRS::test_epsg - AssertionError:
FAILED cartopy/tests/crs/test_equidistant_conic.py::TestEquidistantConic::test_default - AssertionError:
FAILED cartopy/tests/crs/test_equidistant_conic.py::TestEquidistantConic::test_eccentric_globe - AssertionError:
FAILED cartopy/tests/crs/test_equidistant_conic.py::TestEquidistantConic::test_ellipsoid_transform - AssertionError:
FAILED cartopy/tests/crs/test_sinusoidal.py::TestSinusoidal::test_eccentric_globe - AssertionError:
FAILED cartopy/tests/mpl/test_axes.py::test_geoaxes_subplot - assert "<class 'cart...xes.GeoAxes'>" == "<class 'cart...AxesSubplot'>"
=========================== 6 failed, 642 passed, 50 skipped, 68 deselected, 2 xfailed, 2 xpassed, 5675 warnings in 67.16s (0:01:07) ============================
==> ERROR: A failure occurred in check().
oldherl commented on 2023-04-28 02:08 (UTC)
@Polly Try install python-pyarrow
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!
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!