public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. d739da6f477bb097a236879c695cd10835a5a55e
Date: Tue, 01 Mar 2022 15:25:53 +0000	[thread overview]
Message-ID: <4K7Lg55Wstz2xhs@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3305 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  d739da6f477bb097a236879c695cd10835a5a55e (commit)
      from  70e23c18a454f97b0a790c3ecd8d930f9999132d (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 d739da6f477bb097a236879c695cd10835a5a55e
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Tue Mar 1 15:25:01 2022 +0000

    python3-cffi: Add 32 bit ARM rootfile again due to "gnueabi" != "gnu"
    
    My fault, again. :-/
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/packages/{ => armv6l}/python3-cffi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 copy config/rootfiles/packages/{ => armv6l}/python3-cffi (95%)

Difference in files:
diff --git a/config/rootfiles/packages/armv6l/python3-cffi b/config/rootfiles/packages/armv6l/python3-cffi
new file mode 100644
index 000000000..52fe37763
--- /dev/null
+++ b/config/rootfiles/packages/armv6l/python3-cffi
@@ -0,0 +1,30 @@
+usr/lib/python3.10/site-packages/_cffi_backend.cpython-310-armv6l-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
+#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/SOURCES.txt
+#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/dependency_links.txt
+#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/entry_points.txt
+#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/not-zip-safe
+#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/requires.txt
+#usr/lib/python3.10/site-packages/cffi-1.15.0-py3.10.egg-info/top_level.txt
+usr/lib/python3.10/site-packages/cffi/__init__.py
+usr/lib/python3.10/site-packages/cffi/_cffi_errors.h
+usr/lib/python3.10/site-packages/cffi/_cffi_include.h
+usr/lib/python3.10/site-packages/cffi/_embedding.h
+usr/lib/python3.10/site-packages/cffi/api.py
+usr/lib/python3.10/site-packages/cffi/backend_ctypes.py
+usr/lib/python3.10/site-packages/cffi/cffi_opcode.py
+usr/lib/python3.10/site-packages/cffi/commontypes.py
+usr/lib/python3.10/site-packages/cffi/cparser.py
+usr/lib/python3.10/site-packages/cffi/error.py
+usr/lib/python3.10/site-packages/cffi/ffiplatform.py
+usr/lib/python3.10/site-packages/cffi/lock.py
+usr/lib/python3.10/site-packages/cffi/model.py
+usr/lib/python3.10/site-packages/cffi/parse_c_type.h
+usr/lib/python3.10/site-packages/cffi/pkgconfig.py
+usr/lib/python3.10/site-packages/cffi/recompiler.py
+usr/lib/python3.10/site-packages/cffi/setuptools_ext.py
+usr/lib/python3.10/site-packages/cffi/vengine_cpy.py
+usr/lib/python3.10/site-packages/cffi/vengine_gen.py
+usr/lib/python3.10/site-packages/cffi/verifier.py


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2022-03-01 15:25 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=4K7Lg55Wstz2xhs@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