Just tested building latest 6.1.0-beta1 (Slackware Linux), builds without errors and seems to run OK (haven’t, of course, tested each and every function).
Thanks to the devs, looking forward to the stable release.
@dsblank do you want to mention that bsd databases are no longer supported by Gramps on Windows?
The Windows AIO build is failing for 6.1.0-beta1.
I’ll try and take a look later
Probably someone more familiar with the situation should add that, or maybe a full wiki page link.
Related questions that could be addressed: What is BSDDB? What was the last versions that supported BSDDB (on mac, windows, linux)? What should I do if I am migrating from versions older than that?
The Gramps 6.1.0-beta1 is now in an archived flatpak at the gramps-project github Release Gramps Flatpak 6.1.0-beta1--1 · gramps-project/flatpak · GitHub if anyone wants to test the beta on linux without a source install. I did not notice any bugs other than the cli noise pasted below:
[scott@localhost gramps.flatpak.6.1.0-beta1]$ flatpak run org.gramps_project.Gramps
/app/lib/python3.13/site-packages/gramps/gui/glade.py:57: PyGIWarning: GObject derived class Glade shouldn't use __slots__.
class Glade(Gtk.Builder):
WARNING:.upgrade:If upgrade and loading the Family Tree works, you can delete the zip file at /home/scott/.var/app/org.gramps_project.Gramps/data/gramps/Family_Tree_1_2026-04-22_13-24-40.zip
2026-04-22 13:24:41.444: WARNING: upgrade.py: line 2357: If upgrade and loading the Family Tree works, you can delete the zip file at /home/scott/.var/app/org.gramps_project.Gramps/data/gramps/Family_Tree_1_2026-04-22_13-24-40.zip
(gramps:2): OsmGpsMap-CRITICAL **: 13:27:03.756: Map source setup called twice
@dsblank I can give a couple answers for linux and BSDDB3, but it is not a comprehensive answer.
- Flatpak. There is an old archived Gramps 5.1.6 flatpak at the gramps-project github as a way for people to transition to SQLite from BSDDB3. That flatpak depends on getting the Gnome runtime from Flathub, but the runtime will eventually be removed by Flathub due to it being EOL. That is the last Gramps flatpak with BSDDB3. The license Oracle placed on BSDDB3 after acquisition prevents any newer BSDDB3 version from being packaged with Gramps at Flathub. So since the python binding for the older BSDDB3 was abandoned, the python binding no longer works with the python included with the current Gnome runtimes from Flathub.
- System installs on linux. I believe source or .deb installs of Gramps on Linux can still be made to work with BSDDB3. This is because users can use the berkeleydb binding and manually accept Oracle’s end user agreement for BSDDB3. I have not verified this, and this method might be difficult for some users.
Our Snap includes the python3-bsddb3 package. It is available on Ubuntu and Arch, so I would guess it is also available on other Linux distributions. It looks like it is also bundled with our Mac version.
cd aio; ./build.sh works for me locally (fully updated MSSY2 UCRT64) but I can reproduce an error running the github action.
The first sign of problems in the logs is here:
Building wheels for collected packages: orjson, pydotplus, pygraphviz
Building wheel for orjson (pyproject.toml): started
Building wheel for orjson (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
Building wheel for orjson (pyproject.toml) did not run successfully.
exit code: 1
and a little bit further some more detail of the error
Compiling bytecount v0.6.9
error[E0554]: `#![feature]` may not be used on the stable release channel
--> src\lib.rs:4:36
|
4 | #![cfg_attr(feature = "cold_path", feature(cold_path))]
| ^^^^^^^^^^^^^^^^^^
For more information about this error, try `rustc --explain E0554`.
error: could not compile `orjson` (lib) due to 1 previous error
💥 maturin failed
Caused by: Failed to build a native library through cargo
Caused by: Cargo build finished with "exit code: 101": `"cargo" "rustc" "--profile" "release" "--message-format" "json-render-diagnostics" "--manifest-path" "D:\\a\\_temp\\msys64\\tmp\\pip-install-q7sxd6tt\\orjson_7d41824dfa354d46a6bb6b4952d6757b\\Cargo.toml" "--lib"`
Error: command ['maturin', 'pep517', 'build-wheel', '-i', 'D:/a/_temp/msys64/tmp/grampspythonenv/bin/python.exe', '--compatibility', 'off'] returned non-zero exit status 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for orjson
There’s an earlier error collecting pydot
Collecting pydot
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))': /packages/7e/32/a7125fb28c4261a627f999d5fb4afff25b523800faed2c30979949d6facd/pydot-4.0.1-py3-none-any.whl.metadata
Downloading pydot-4.0.1-py3-none-any.whl.metadata (11 kB)
Collecting pydotplus
I can’t say I understand what’s going wrong but at least we have an area to investigate now.
Yes, python-bsddb3 is the abandoned python binding that stopped working reliably when I tested it several years ago with the python 3.10 included with the Gnome runtime at Flathub. I see that Ubuntu is patching python-bsddb3, or perhaps Snaps have older python3 versions available for use? I could not find the version of python used on the Gramps Snap.
About a year or two ago Fedora’s Gramps flatpak still included bsddb3. However, when I checked to see if they got bsddb3 working after python 3.10, their flatpak failed to open or create a bsddb3 database for me. I have not checked lately if Fedora fixed the issue or not.
The Snap is using the python-bsddb3 package from Ubuntu 24.04.