wezterm: Update to sha 30345b36d8a00fed347e4df5dadd83915a7693fb

[eschnett]

Description

Update wezterm to a newer (not yet released) upstream version. Closes https://trac.macports.org/ticket/70833 .

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 15.0 24A335 arm64
Xcode 16.0 16A242d

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 --nitpick?
• 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?

sudo port test fails with a message that I do not understand. The error is

:info:build error: could not load Cargo configuration
:info:build Caused by:
:info:build   could not parse TOML configuration in `/opt/local/var/macports/build/_Users_eschnett_src_macports-ports_aqua_wezterm/wezterm/work/.home/.cargo/config.toml`
:info:build Caused by:
:info:build   TOML parse error at line 14, column 1
:info:build      |
:info:build   14 | [build]
:info:build      | ^
:info:build   invalid table header
:info:build   duplicate key `build` in document root

[macportsbot]

Notifying maintainers:
@herbygillot for port wezterm.

[markemer]

This sha I picked was the HEAD at a random time. We should pick at the current head as of some date, like today, or the first SHA after the last release that works on sequoia. I like the idea of using the current head with a comment saying to update it when the release happens.

The current head would be wez/wezterm@a2f2c07

[reneeotten]

This sha I picked was the HEAD at a random time. We should pick at the current head as of some date, like today, or the first SHA after the last release that works on sequoia. I like the idea of using the current head with a comment saying to update it when the release happens.

The current head would be wez/wezterm@a2f2c07

well... typically a port should install an version released by upstream, not some random git commit hash. If earlier releases don't work on the latest macOS version it might be time to try and persuade upstream to tag a nee version.

If you want to follow upstream development that should be done in a "-devel" subport.

Let's leave a decision in this to the port maintainer @herbygillot

[markemer]

This sha I picked was the HEAD at a random time. We should pick at the current head as of some date, like today, or the first SHA after the last release that works on sequoia. I like the idea of using the current head with a comment saying to update it when the release happens.
The current head would be wez/wezterm@a2f2c07

well... typically a port should install an version released by upstream, not some random git commit hash. If earlier releases don't work on the latest macOS version it might be time to try and persuade upstream to tag a nee version.

If you want to follow upstream development that should be done in a "-devel" subport.

Let's leave a decision in this to the port maintainer @herbygillot

Yeah - I have a git stash just to bring in a SHA that works, but a -devel might not be a bad idea. I can open an issue upstream about not building on 15, sadly since the binary release works and HEAD works, I anticipate some push back, but can't hurt to try.

[herbygillot]

The only issue here is that the SHA version doesn't follow the same format as the version there currently.
So maybe we can do this, but explicitly set a datestamped current version with the assumption that the next release will have a higher (later) datestamp.

So perhaps something like this:

github.setup        wez wezterm 30345b36d8a00fed347e4df5dadd83915a7693fb
version             20240813-000000-30345b36d8

20240813 is the datestamp of that commit.

[markemer]

Not a bad plan. We should decide if this is the SHA we want, too. I want to stress that this was just HEAD at the time I tested to see if it had been fixed upstream, and I've just run with it so far.

[reneeotten]

@herbygillot can you please take over this PR and get it merged? It's not going anywhere - otherwise I'll close it.

[herbygillot]

@herbygillot can you please take over this PR and get it merged? It's not going anywhere - otherwise I'll close it.

Will do