From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. d7ce23e5deccf3fbe56c44ff4c29817c03166c76
Date: Mon, 04 Jun 2018 12:17:46 +0100 [thread overview]
Message-ID: <20180604111746.73F861081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1747 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 d7ce23e5deccf3fbe56c44ff4c29817c03166c76 (commit)
from acb41000189b667324ab601f30a97f506c461f72 (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 d7ce23e5deccf3fbe56c44ff4c29817c03166c76
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 4 12:15:26 2018 +0100
aarch64: Fix rootfile for Python
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/aarch64/python | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/aarch64/python b/config/rootfiles/common/aarch64/python
index 7495c0115..463dfed8f 100644
--- a/config/rootfiles/common/aarch64/python
+++ b/config/rootfiles/common/aarch64/python
@@ -1967,7 +1967,7 @@ usr/lib/python2.7/lib-dynload/cStringIO.so
usr/lib/python2.7/lib-dynload/cmath.so
usr/lib/python2.7/lib-dynload/crypt.so
usr/lib/python2.7/lib-dynload/datetime.so
-usr/lib/python2.7/lib-dynload/dbm.so
+usr/lib/python2.7/lib-dynload/dbm_failed.so
usr/lib/python2.7/lib-dynload/fcntl.so
usr/lib/python2.7/lib-dynload/future_builtins.so
usr/lib/python2.7/lib-dynload/gdbm.so
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-06-04 11:17 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=20180604111746.73F861081DF2@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