gramps: update to 6.0.6

[szhorvat]

• update to 6.0.6
• move graphviz to a runtime dependency
• fix indending in Portfile

Description

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 26.1 25B78 arm64
Xcode 26.1.1 17B100

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@mascguy for port gramps.
@dbevans for port gramps.

[szhorvat]

The main motivation for this is to move graphviz to a runtime dependency. Tests were already failing before the update and are still failing. I quickly verified that the program starts up. CC @Dave-Allured

[szhorvat]

This installs fine locally, but on the CI runner the following error occurs:

2025-11-23T19:54:22.4028000Z DEBUG: Executing proc-post-org.macports.activate-activate-0
2025-11-23T19:54:22.4030980Z DEBUG: system: /opt/local/bin/update-desktop-database /opt/local/share/applications
2025-11-23T19:54:22.4160150Z The databases in [/opt/local/share/applications] could not be updated.
2025-11-23T19:54:22.4160540Z Command failed: /opt/local/bin/update-desktop-database /opt/local/share/applications
2025-11-23T19:54:22.4160640Z Exit code: 1
2025-11-23T19:54:22.4168730Z Error: Failed to activate gramps: command execution failed

Do you have any idea what may be going wrong here, @mascguy ?

[szhorvat]

@dbevans @mascguy Can you help here? If not, I'll abandon this PR as my motivation was to clean up when graphviz is used as a dependency. I don't actually use this port, and can't afford the time to debug this issue, given that I can't even reproduce it locally.

[mascguy]

@dbevans @mascguy Can you help here? If not, I'll abandon this PR as my motivation was to clean up when graphviz is used as a dependency. I don't actually use this port, and can't afford the time to debug this issue, given that I can't even reproduce it locally.

Perhaps there's something different about the CI environment? That's a stretch though, I can't say without spending more time in it.

Dave/anyone...?

[Dave-Allured]

The core build seems fine. This error is coming from update-desktop-database in the post-activate block. I think there is confusion over where two databases org.gramps_project.Gramps.metainfo.xml and org.gramps_project.Gramps.xml should be installed. The path logic may have changed between releases. I do not think this is the CI environment.

It looks like those files are being installed into a python-specific Frameworks directory, but the post-activate commands want to find them under the generic /opt/local/share/applications. This would explain the current error message. There are more specifics in the last few lines of the CI logs. I would need to look deeper to figure out which path is correct or intended. Perhaps look at a successful build of the previous version, see what they are doing there.

There is a commented-out (2024) patch related to "resource paths". It is a simple thing, just fixing a line ending character. It does not look related to the current problem -- but it might be.

I am out of time for today. Maybe later. Anyone else want to join the fun?

[Dave-Allured]

I think there is confusion over where two databases org.gramps_project.Gramps.metainfo.xml and org.gramps_project.Gramps.xml should be installed. The path logic may have changed between releases.

This is incorrect. The related install paths are exactly the same between the old v6.0.5 and the new v6.0.6. Also the old version 6.0.5 now gets exactly the same CI error as the new version, so the problem seems to be a change in the CI environment, or in one of the MacPorts components installed in the CI. Adding a verbose flag to the database command shows a little more information:

DEBUG: system: /opt/local/bin/update-desktop-database -v /opt/local/share/applications
Search path is now: [/opt/local/share/applications]
Could not create cache file in "/opt/local/share/applications": Error opening directory ?/opt/local/share/applications?: No such file or directory
The databases in [/opt/local/share/applications] could not be updated.

So the real problem is that /opt/local/share/applications was not created for the start of the post-activate phase. More than a hundred other ports use exactly the same post-activate command. I do not see what is different about this port, or what changed since the earlier successful 6.0.5 builds. Anyone?