portable-ruby 3.4.2

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

• resource blocks have been checked for updates.

[p-linnane]

@Bo98 Everything looks good here except for the expected error on El Capitan.

[MikeMcQuaid]

@Bo98 Everything looks good here except for the expected error on El Capitan.

@p-linnane @Bo98 what's expected about the error here? Missing context.

[p-linnane]

Per Bo on the previous PR:

This has however been useful in revealing a bug on older macOS so will look into upstreaming a fix for that.

I have no other info than that.

[EricFromCanada]

It's a usage of clock_gettime which, as we all remember, was only implemented in macOS 10.12. It's been patched before, but doesn't look like a PR has been issued so far.

[p-linnane]

Would it not make more sense to drop El Capitan support if this a recurring issue?

[Bo98]

Yeah lost track of this with all the AGM stuff.

Patch would be fairly trivial but 10.11 was on track for being dropped if we end up using copyfile (not in Ruby 3.4 though, maybe 3.5).

We can drop 10.11 but I'll need to update the CI images to 10.12 which could be done on the 11th March maintenance window. And then coordinate Homebrew 4.5.0 to happen with that and the Ruby 3.4 minimum version bump. It's more work than patching but probably was going to happen eventually anyway.

[p-linnane]

Let's just patch for now since it's trivial. Better than rushing with everything else that needs to happen.

[MikeMcQuaid]

@Bo98 I'd also consider patching to be better her but if the CI images are changing anyway: feel free to do that instead. Would like to have this merged before end of March if at all possible.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[p-linnane]

Do we still want to patch this?

[Bo98]

Yes, sorry. The Orka upgrade took priority. If you don't hear from me by the next week feel free to do whatever here. The "before end of March" comment from above still applies.

[p-linnane]

Definitely did not mean to insinuate this got dropped, so I'm sorry if it came off that way. I know how crazy the Orka upgrade was. I just wanted to throw a comment on here to ward off stalebot and bring this back to top of mind. Let me know if there's any way I can help with this.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Bo98]

Handling in #306.

While not necessarily intentional, the delay here probably actually worked out for the best given RuboCop only got full 3.4 support a couple weeks ago. The idea of ignoring Ruby X.Y.0 releases was to make sure all dependencies were updated and any regressions were addressed - and that process seems to have taken longer than usual this time round on the dependencies side.