From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8e9dd5d165b1cbb6b9ebd6d1e4bd0a7a2af0a3dd
Date: Tue, 16 Sep 2025 10:01:49 +0000 (UTC) [thread overview]
Message-ID: <4cQy9T4tG9z2xcq@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 8e9dd5d165b1cbb6b9ebd6d1e4bd0a7a2af0a3dd (commit)
from d3725fecec79b5d2c807e9830d983a1804b14616 (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 8e9dd5d165b1cbb6b9ebd6d1e4bd0a7a2af0a3dd
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue Sep 16 10:01:32 2025 +0000
python3: Don't try to remove setuptools outside the toolchain stage
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/python3 | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/python3 b/lfs/python3
index 4e5afa285..10e85b37e 100644
--- a/lfs/python3
+++ b/lfs/python3
@@ -113,7 +113,9 @@ else
endif
# Remove the bundled setuptools directories
- cd /usr/lib/python3.10/site-packages/ && rm -r setuptools*
+ifeq "$(ROOT)" ""
+ rm -rfv /usr/lib/python3.10/site-packages/setuptools*
+endif
@rm -rf $(DIR_APP)
@$(POSTBUILD)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-09-16 10:01 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=4cQy9T4tG9z2xcq@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