git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Mar 2026, #08)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 23, 2026, 16:54 UTC
Message-ID
<xmqq8qbi5vvx.fsf@gitster.g>
In-Reply-To
<458ad3c1-96df-4575-ee42-e6eb754f25f6@gmx.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 5 quoted lines
> And indeed, the broken `macos-14-arm64/20260317.0174` release has been
> deleted from https://github.com/actions/runner-images/releases -- the
> latest published `macos-14-arm64` release as of time of writing is once
> again (the last known good one):
> https://github.com/actions/runner-images/releases/tag/macos-14-arm64%2F20260302.0147
Great to know.
Show 5 quoted lines
> In light of that, the workaround in
> `js/macos-homebrew-forgets-reg-enhanced` may still be worth keeping as
> insurance, even though the immediate breakage has been mitigated by the
> image rollback. We would be one image refresh away from the same failure
> otherwise.

Yes, it will become necessary to resurrect it or something similar when they break it the same way in the future.

The question is where we keep it---I am assuming that forcing build with "clang" to use the compat/ regexp library replacement would not be something we want to do until they break it again, so keeping it forever in 'seen' does not feel quite right (let alone merging it down anywhere near 'next' or 'master'). The lore archive will of course keep it safely and we can retrieve it when it becomes necessary *and* if we remember which patch it was.

Would the best thing we can do here be something like this patch, perhaps?

--- >8 ---
Subject: regexp: leave a pointer to resurrect workaround for Homebrew

Recently some GitHub CI jobs were broken by update on the platform side, which was eventually resolved by image rollback, but in the meantime Dscho invented a workaround patch to sidestep the broken part of the platform. Their future image update may contain the same bug, in which case the workaround may again become needed.

As we do not want to be building with workaround that avoids system regexp library altogether unless the system is known to be broken, so short of an automated "detect broken system and apply workaround" mechanism, let's use the folks who are compiling the code to detect breakage on their system and cope with the breakage ;-)

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 compat/regcomp_enhanced.c | 5 +++++
 1 file changed, 5 insertions(+)
diff --git c/compat/regcomp_enhanced.c w/compat/regcomp_enhanced.c
index 84193ce53b..29c74eee99 100644
--- c/compat/regcomp_enhanced.c
+++ w/compat/regcomp_enhanced.c
@@ -3,6 +3,11 @@
 
 int git_regcomp(regex_t *preg, const char *pattern, int cflags)
 {
+	/*
+	 * If you are on macOS with clang and fail to compile this line,
+	 * https://lore.kernel.org/git/458ad3c1-96df-4575-ee42-e6eb754f25f6@gmx.de/
+	 * might be relevant.
+	 */
 	if (!(cflags & REG_EXTENDED))
 		cflags |= REG_ENHANCED;
 	return regcomp(preg, pattern, cflags);
Previous: Johannes SchindelinNext: Jeff King
Message 7 of 8 in “What's cooking in git.git (Mar 2026, #08)”
  1. Junio C HamanoMar 22, 2026
  2. Shreyansh PaliwalMar 22, 2026
  3. Junio C HamanoMar 22, 2026
  4. René ScharfeMar 22, 2026
  5. Junio C HamanoMar 22, 2026
  6. Johannes SchindelinMar 23, 2026
  7. Junio C HamanoMar 23, 2026
  8. Jeff KingMar 22, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.