I wanted to upgrade my Gramps (Genealogy Research Application) version from 5.1.6 to the current 5.2.2. using the Tumbleweed official release. The software installation went to conclusion successfully. However, Gramps did not start.
Maybe the cause of failure, was the fact that the installed gramps and gramps-lang show different version designations. Is that a feasible explanation? The YaST installation process proposed taking the language file from the ecsos repository giving final version designations
gramps 5.2.2-1.1
gramps-lang 5.2.2-lp156.1.1.
Installation of the main package from ecsos repo requires a package
Just recently, I upgraded from Leap 15.5 to Leap 15.6. On 15.5 I have used Gramps 5.1.6 directly from openSUSE repo. Now, I am on Leap 15.6. And I would like to update Gramps to 5.2.2, too. There is Gramps 5.2.2 directly available for Tumbleweed, but not for Leap. So, I am still with 5.1.6.
User @ecsos made the effort to set up a home OBS build of Gramps 5.2.2. I tried that one: I could install it if I add the /repositories/devel:/languages:/python:/backports repo (in order to resolve python3-bsddb3), but it didn’t run successfully on my system: it was throwing several Python errors like “expected 3 arguments, but only 2 arguments given”. N.B. you have to start Gramps with python3.11 /usr/bin/gramps — not just /usr/bin/gramps or python3 /usr/bin/gramps. (Reason: see soon.)
User @ecsos made some specific changes to the original Gramps. He personally modified File gramps.spec of Package gramps. Additionally he uses /repositories/home:/ecsos:/python for his specific build of Show home:ecsos / gramps. Well, with that repo, he has his “own” Python… In a personal message he told me, that this build of Gramps is running successfully on his system. He made the change on File gramps.spec of Package gramps because Gramps 5.2.2 now requires at least Python 3.8. But python3 of Leap refers to 3.6. With %define pythons python311 (line 21 of SPEC file) he forces to build with Python 3.11.