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. 30ea66cf4b1161d682b489e29096111ddc120c4f
Date: Sun, 07 Aug 2022 09:33:23 +0000 [thread overview]
Message-ID: <4M0vK01C34z2xX7@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2381 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 30ea66cf4b1161d682b489e29096111ddc120c4f (commit)
from 06b4164dfe269704976b52421edbbbdf3b345679 (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 30ea66cf4b1161d682b489e29096111ddc120c4f
Author: Adolf Belka <adolf.belka(a)ipfire.org>
Date: Sat Aug 6 23:35:48 2022 +0200
pyfuse3: Install to provide fuse capability for borgbackup
- v3 version adds specific armv6l based rootfile as xxxMACHINExxx does not get correct
substitution
Fixes: Bug#12611
Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/{ => armv6l}/python3-pyfuse3 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
copy config/rootfiles/packages/{ => armv6l}/python3-pyfuse3 (88%)
Difference in files:
diff --git a/config/rootfiles/packages/armv6l/python3-pyfuse3 b/config/rootfiles/packages/armv6l/python3-pyfuse3
new file mode 100644
index 000000000..c8f17804a
--- /dev/null
+++ b/config/rootfiles/packages/armv6l/python3-pyfuse3
@@ -0,0 +1,10 @@
+usr/lib/python3.10/site-packages/_pyfuse3.py
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info/PKG-INFO
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info/SOURCES.txt
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info/dependency_links.txt
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info/requires.txt
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info/top_level.txt
+#usr/lib/python3.10/site-packages/pyfuse3-3.2.1-py3.10.egg-info/zip-safe
+usr/lib/python3.10/site-packages/pyfuse3.cpython-310-arm-linux-gnueabi.so
+usr/lib/python3.10/site-packages/pyfuse3_asyncio.py
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-08-07 9:33 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=4M0vK01C34z2xX7@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