From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 3da7324a721be7bc8f76e8b17068c18aeeae6bdd
Date: Mon, 04 Jun 2018 20:35:11 +0100 [thread overview]
Message-ID: <20180604193512.177D91081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2054 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 3da7324a721be7bc8f76e8b17068c18aeeae6bdd (commit)
from 5bb288a244156c95a61cdf2f3b416061c867bf26 (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 3da7324a721be7bc8f76e8b17068c18aeeae6bdd
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 4 20:32:26 2018 +0100
aarch64: Rootfile update for Python 3
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/aarch64/python3 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/packages/aarch64/python3 b/config/rootfiles/packages/aarch64/python3
index 06be65058..a1b17d942 100644
--- a/config/rootfiles/packages/aarch64/python3
+++ b/config/rootfiles/packages/aarch64/python3
@@ -2714,7 +2714,7 @@ usr/lib/python3.6/lib-dynload/_ctypes_test.cpython-36m-aarch64-linux-gnu.so
usr/lib/python3.6/lib-dynload/_curses.cpython-36m-aarch64-linux-gnu.so
usr/lib/python3.6/lib-dynload/_curses_panel.cpython-36m-aarch64-linux-gnu.so
usr/lib/python3.6/lib-dynload/_datetime.cpython-36m-aarch64-linux-gnu.so
-usr/lib/python3.6/lib-dynload/_dbm.cpython-36m-aarch64-linux-gnu.so
+usr/lib/python3.6/lib-dynload/_dbm.cpython-36m-aarch64-linux-gnu_failed.so
usr/lib/python3.6/lib-dynload/_decimal.cpython-36m-aarch64-linux-gnu.so
usr/lib/python3.6/lib-dynload/_elementtree.cpython-36m-aarch64-linux-gnu.so
usr/lib/python3.6/lib-dynload/_gdbm.cpython-36m-aarch64-linux-gnu.so
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-06-04 19:35 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=20180604193512.177D91081DF2@git01.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