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