From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 768e8218a84f58f128aff97efb0137f521a6a7dd
Date: Sat, 28 Mar 2026 12:57:52 +0000 (UTC) [thread overview]
Message-ID: <4fjcxX1Hqvz2xNn@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 768e8218a84f58f128aff97efb0137f521a6a7dd (commit)
from f13abe9156398b8a95c71bd0d87ac801c90d543d (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 768e8218a84f58f128aff97efb0137f521a6a7dd
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Sat Mar 28 12:57:31 2026 +0000
python3-yaml: Fix rootfile
Third time lucky?
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/python3-yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/packages/python3-yaml b/config/rootfiles/packages/python3-yaml
index e9d2c11d4..26bc99b15 100644
--- a/config/rootfiles/packages/python3-yaml
+++ b/config/rootfiles/packages/python3-yaml
@@ -7,7 +7,7 @@ usr/lib/python3.10/site-packages/_yaml
usr/lib/python3.10/site-packages/_yaml/__init__.py
usr/lib/python3.10/site-packages/yaml
usr/lib/python3.10/site-packages/yaml/__init__.py
-usr/lib/python3.10/site-packages/yaml/_yaml.cpython-310-x86_64-linux-gnu.so
+usr/lib/python3.10/site-packages/yaml/_yaml.cpython-310-xxxMACHINExxx-linux-gnu.so
usr/lib/python3.10/site-packages/yaml/composer.py
usr/lib/python3.10/site-packages/yaml/constructor.py
usr/lib/python3.10/site-packages/yaml/cyaml.py
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-03-28 12:57 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=4fjcxX1Hqvz2xNn@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