From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a735dad621128b7057a03d805deb8aa049ae7f21
Date: Wed, 02 Mar 2022 13:37:52 +0000 [thread overview]
Message-ID: <4K7wD05pVwz2xgg@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
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 a735dad621128b7057a03d805deb8aa049ae7f21 (commit)
from d739da6f477bb097a236879c695cd10835a5a55e (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 a735dad621128b7057a03d805deb8aa049ae7f21
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Mar 2 13:37:28 2022 +0000
python3-cffi: Fix armv6l rootfile
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/armv6l/python3-cffi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/packages/armv6l/python3-cffi b/config/rootfiles/packages/armv6l/python3-cffi
index 52fe37763..9c55c4729 100644
--- a/config/rootfiles/packages/armv6l/python3-cffi
+++ b/config/rootfiles/packages/armv6l/python3-cffi
@@ -1,4 +1,4 @@
-usr/lib/python3.10/site-packages/_cffi_backend.cpython-310-armv6l-linux-gnueabi.so
+usr/lib/python3.10/site-packages/_cffi_backend.cpython-310-arm-linux-gnueabi.so
usr/lib/python3.10/site-packages/cffi
#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info
#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/PKG-INFO
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-03-02 13:37 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=4K7wD05pVwz2xgg@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