Hi there I just wanted to report that the Warpinator app on the Raspberry pi 4 Arm64 is broken
Using bubblewrap for incoming file isolation. Write access for the application will be limited to the save directory only.
Traceback (most recent call last):
File "/usr/lib/warpinator/warpinator.py", line 21, in <module>
File "/usr/lib/warpinator/server.py", line 13, in <module>
File "/usr/lib/python3.11/site-packages/grpc/__init__.py", line 22, in <module>
from grpc import _compression
File "/usr/lib/python3.11/site-packages/grpc/_compression.py", line 20, in <module>
from grpc._cython import cygrpc
ImportError: libgmock.so.1.14.0: cannot open shared object file: No such file or directory
I can reproduce it on my PineBook Pro.
gtest. No idea why Warpinator would be looking for that library, but it works.
warpinator may need a rebuild. It is a ARCH-ARM package. I can not get to their PKGBUILD right now as I do not know what branch you all are running.
The ALARM Source Files and View Changes links haven’t worked for quite some time now, no idea why.
They’re probably using the x86_64 PKGBUILD since the architecture is ‘any’.
I’m on the unstable branch, by the way.
Installing gtest fixes the issue, not sure why it requires that package either but it looks like the package needs to be rebuilt with that dependency added
Highly doubtful as there are no compiled binaries (ELF files). There’s never been a rebuild required on x86_64 except for the annual Python release to reinstall into the matching directory.
That does sound logical based on the information we have, however it’s neither listed as a dependency upstream nor required on x86_64.
If it can be reproduced on ALARM, then perhaps create a post on the ALARM forums. Maybe someone there will know who to contact regarding the issue.
Right I see and I could but wouldn’t that be Manjaro’s job as package maintainers also do this and not the users even if I they bug testing/reporting?