From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 41f3b4296e4ec3f1c0b8d382e020d9b6e03509ee
Date: Thu, 19 Nov 2026 15:12:36 +0000 (UTC) [thread overview]
Message-ID: <4jVhm40pXZz2xNP@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 41f3b4296e4ec3f1c0b8d382e020d9b6e03509ee (commit)
from be93af142b427357666fae8232974864015402b2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 41f3b4296e4ec3f1c0b8d382e020d9b6e03509ee
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu Nov 19 15:07:27 2026 +0000
make.sh: Do not store the Go cache in the shared ccache
The Go build cache does not only contain data, but also executables that
Go runs straight from there (e.g. "go run" for version-gen in
amazon-ssm-agent). The ccache is shared between builders and is mounted
noexec, so these fail with "permission denied". Running binaries from a
shared cache is also not something we want to do.
Go cannot run without a build cache (GOCACHE=off is not supported any
more), so simply drop the override and use the default location in the
chroot which is local to each builder.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 3 ---
1 file changed, 3 deletions(-)
Difference in files:
diff --git a/make.sh b/make.sh
index af6948620..73ec41b02 100755
--- a/make.sh
+++ b/make.sh
@@ -748,9 +748,6 @@ execute() {
# Compiler Cache
[CCACHE_DIR]="/usr/src/ccache"
-
- # Go Cache
- [GOCACHE]="/usr/src/ccache/go"
)
# Fake environment
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-11-19 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4jVhm40pXZz2xNP@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox