From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. af2dc11c921062608c4537368885eb195f54c177
Date: Tue, 19 Mar 2019 11:28:39 +0000 [thread overview]
Message-ID: <20190319112839.B5C4A84FDAF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1731 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 af2dc11c921062608c4537368885eb195f54c177 (commit)
from b60fd7a3e2640d7da41a3bdb875669c302849acc (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 af2dc11c921062608c4537368885eb195f54c177
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Mar 16 23:09:11 2019 +0000
Rootfile update
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/armv5tel/python3-yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/packages/armv5tel/python3-yaml b/config/rootfiles/packages/armv5tel/python3-yaml
index 6f8354a24..9525d0e37 100644
--- a/config/rootfiles/packages/armv5tel/python3-yaml
+++ b/config/rootfiles/packages/armv5tel/python3-yaml
@@ -1,5 +1,5 @@
#usr/lib/python3.6/site-packages/PyYAML-3.13-py3.6.egg-info
-usr/lib/python3.6/site-packages/_yaml.cpython-36m-arm-linux-gnu.so
+usr/lib/python3.6/site-packages/_yaml.cpython-36m-arm-linux-gnueabi.so
usr/lib/python3.6/site-packages/yaml
#usr/lib/python3.6/site-packages/yaml/__init__.py
#usr/lib/python3.6/site-packages/yaml/__pycache__
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-03-19 11:28 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=20190319112839.B5C4A84FDAF@people01.i.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