ティージェーグレェI submitted a Pull Request to update MacPorts' rpki-client to 9.5 here:<br><br><a href="https://github.com/macports/macports-ports/pull/28128" rel="nofollow noopener" target="_blank">https://github.com/macports/macports-ports/pull/28128</a><br><br>GitHub Continuous Integration checks passed!<br><br>Update: Or at least I thought they did?<br><br>Now seeing this error:<br><br>"Creating port index in /Users/runner/work/macports-ports1597/macports-ports1597/ports<br>Adding port net/rpki-client<br>signal interp lost<br>ports/.github/workflows/bootstrap.sh: line 150: 2047 Abort trap: 6 portindex -e<br>Error: Process completed with exit code 134."<br><br>o.O<br><br>From: <a href="https://github.com/artkiver/macports-ports1597/actions/runs/14437970476" rel="nofollow noopener" target="_blank">https://github.com/artkiver/macports-ports1597/actions/runs/14437970476</a><br><br>Even though previously in the GitHub UI, it showed all three checks as green. wtfh? I mean, I <i>hate</i> GitHub and have less than no reason to trust it, but that's a new one, even for me.<br><br>If I check: <a href="https://github.com/macports/macports-ports/pull/28128/checks" rel="nofollow noopener" target="_blank">https://github.com/macports/macports-ports/pull/28128/checks</a><br><br>All is green there too. I am so confused.<br><br>Regardless, it's up to someone else with commit access to merge it.<br><br>Meanwhile, still no assistance regarding my request for help on the MacPorts' patches for OpenSSH 10.0p1/2 for ssh-agent.c and sshd-session.c, but someone else did open another Trac issue regarding OpenSSH's logging (or lack thereof) here:<br><br><a href="https://trac.macports.org/ticket/72345" rel="nofollow noopener" target="_blank">https://trac.macports.org/ticket/72345</a><br><br>Though, they also observe the same behavior with the Apple shipped version, so they pontificate if it may be an issue upstream?<br><br>Ya think?<br><br>Sometimes, I think folks vastly overestimate what "maintainer" means or how much I might be using some of this software or what they expect me to do about it just because it is "assigned" to me.<br><br>For example: I basically do not run sshd on any macOS systems, since I only have Apple laptops which sleep a <i>lot</i> and are absolutely <i>awful</i> as anything that should be a server running daemonized software.<br><br>Did these folks not notice that Apple <i>themselves</i> discontinued their XServe hardware line circa 2004? Or that even their "OS X Server" product was discontinued from the App Store in 2022?<br><br>I guess they missed the memos, couldn't read the room or writing on the wall?<br><br>But then, they observed this in macOS Monterey, which itself is from 2021, so maybe they just prefer livin in the past? I have no idea.<br><br>I am not even sure how to meaningfully reply to that Trac issue.<br><br><a href="https://snac.bsd.cafe?t=rpki" class="mention hashtag" rel="nofollow noopener" target="_blank">#RPKI</a> <a href="https://snac.bsd.cafe?t=rpkiーclient" class="mention hashtag" rel="nofollow noopener" target="_blank">#rpkiーclient</a> <a href="https://snac.bsd.cafe?t=macports" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacPorts</a> <a href="https://snac.bsd.cafe?t=macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://snac.bsd.cafe?t=bgp" class="mention hashtag" rel="nofollow noopener" target="_blank">#BGP</a> <a href="https://snac.bsd.cafe?t=openbgpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBGPD</a> <a href="https://snac.bsd.cafe?t=opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a><br>