| Summary: | app-misc/gramps-5.1.6-r2: ResourcePath.ERROR: Unable to determine resource path | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Julien Papasian <julien.papasian> |
| Component: | Current packages | Assignee: | Marek Szuba (RETIRED) <marecki> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=909880 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This may have been fixed by: commit 5c7e102c618f78275f994d75344766fdb42a1426 Author: Marek Szuba <marecki@gentoo.org> Date: Thu Sep 7 09:29:51 2023 +0100 app-misc/gramps: set the resource path again Still needed, as it turns out. In the past we did it using the upstream setup.py option --resource-path but that seems to be broken in PEP-517 mode, and a single echo call utilising ebuild helper functions and variables produces exactly the same result. Signed-off-by: Marek Szuba <marecki@gentoo.org> yesterday, although it didn't revbump which will be needed if the fix works for you. Can you re-emerge it please? Indeed, it was built 2 days ago, and rebuilding now fixes the problem. Should I keep the bug open for revbump? The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=884a833a26000f36bb645fd24fe42eddb4ac953e commit 884a833a26000f36bb645fd24fe42eddb4ac953e Author: Marek Szuba <marecki@gentoo.org> AuthorDate: 2023-09-08 09:54:34 +0000 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: 2023-09-08 09:54:34 +0000 app-misc/gramps: revbump for 5c7e102c618f78275f994d75344766fdb42a1426 That commit has changed the run-time behaviour of Gramps so it should have been accompanied by a revision bump to begin with. Closes: https://bugs.gentoo.org/913855 Signed-off-by: Marek Szuba <marecki@gentoo.org> app-misc/gramps/{gramps-5.1.6-r2.ebuild => gramps-5.1.6-r3.ebuild} | 0 1 file changed, 0 insertions(+), 0 deletions(-) |
#909880 introduces a critical regression (works fine with 5.1.6-r1). I can't open the app, I get: ResourcePath.ERROR: Unable to determine resource path There are various threads on Gramps forums about this, but basically it worked before. I don't know the technical details about how this ebuild is written but I can see something that seem close to the error on -r1: ${PYTHON} setup.py --verbose install --root="${ED}" --resourcepath=/usr/share Here we have a resourcepath parameter. In -r2, this parameter seems missing from the ebuild. Reproducible: Always Steps to Reproduce: 1.Open app Actual Results: App doesn't open and fails with message: ResourcePath.ERROR: Unable to determine resource path Expected Results: App opens