Is Gramps 6.0.0-beta1 supposed to fail to launch when orjson is not installed?

I tested the Gramps 6.0.0-beta1 for the flatpak today. It compiled without orjson, but it failed to launch during testing. The cli error mentioned that Gramps failed to launch because orjson is not installed.

There is a problem compiling the Gramps flatpak with orjson that I have not figured out yet. The orjson installation wheels from pypi give unrecognized archive errors for 3.10 and 3.9, and the orjson source at github failed because it needed the deprecated python setup tools that have been dropped in the python 3.12 used in Gnome 47. So it would be easier if Gramps could work without orjson, but I will keep doing trial and error to get orjson to work for now.

I got orjson to install in the flatpak, so the second paragraph is no longer relevant.

3 Likes

Nice work! What did you have to do?

Thanks. I searched the flathub github for other flatpaks that succeeded in getting orjson to work, then modified their command to
pip3 install --verbose --exists-action=i --no-index --find-links="file://${PWD}" --no-build-isolation wheel orjson
This works for orjson 3.9.15 but not the current orjson 3.10.15. The source also had to be changed to “file” from “archive”. Orjson seems to require rust to compile from source, which can be problematic for flatpaks.

The normal pip command used in the Gramps manifest is pip3 install --no-build-isolation .

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.