From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. ada4c102e2f5208f7e9bc33eb48dfce366464444
Date: Tue, 13 Dec 2016 12:18:09 +0000 [thread overview]
Message-ID: <20161213121809.7553D1078E80@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 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 3.x development tree".
The branch, master has been updated
via ada4c102e2f5208f7e9bc33eb48dfce366464444 (commit)
from 87bc1697b8d532632ce054fe860e27ffad587dc5 (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 ada4c102e2f5208f7e9bc33eb48dfce366464444
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Tue Dec 13 13:10:27 2016 +0100
m4: Rebuild against glibc 2.24
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
m4/m4.nm | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/m4/m4.nm b/m4/m4.nm
index 2997dcf..f2dcea4 100644
--- a/m4/m4.nm
+++ b/m4/m4.nm
@@ -5,7 +5,7 @@
name = m4
version = 1.4.17
-release = 1
+release = 2
groups = Applications/Text
url = http://www.gnu.org/software/m4/
@@ -25,6 +25,10 @@ source_dl = http://ftp.gnu.org/gnu/m4/
sources = %{thisapp}.tar.xz
build
+ requires
+ glibc-devel >= 2.24
+ end
+
test
make check
end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-12-13 12:18 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=20161213121809.7553D1078E80@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