From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 63c3f2f085041cd2fc3d93505cc099d29b8002e7
Date: Thu, 13 Oct 2016 13:20:17 +0100 [thread overview]
Message-ID: <20161013122017.F2A5C1078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1762 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 63c3f2f085041cd2fc3d93505cc099d29b8002e7 (commit)
from 7dcf09a681fba7e1b5d511e92caea9b59dcea8b1 (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 63c3f2f085041cd2fc3d93505cc099d29b8002e7
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Oct 13 13:17:38 2016 +0100
nettle: Update to 3.3
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
nettle/nettle.nm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/nettle/nettle.nm b/nettle/nettle.nm
index 9f2213f..1c0695f 100644
--- a/nettle/nettle.nm
+++ b/nettle/nettle.nm
@@ -4,7 +4,7 @@
###############################################################################
name = nettle
-version = 3.2
+version = 3.3
release = 1
groups = System/Libraries
@@ -23,7 +23,7 @@ source_dl = http://www.lysator.liu.se/~nisse/archive/
build
requires
- gmp-devel
+ gmp-devel >= 5.0.0
m4
end
@@ -63,7 +63,7 @@ packages
package %{name}-devel
template DEVEL
- requires += gmp-devel
+ requires += gmp-devel >= 5.0.0
end
package %{name}-debuginfo
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-10-13 12:20 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=20161013122017.F2A5C1078E81@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