From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 588b9cc28b5515f1d8f862b18f538586b9051ed1
Date: Sun, 11 Nov 2012 14:31:46 +0100 [thread overview]
Message-ID: <20121111133147.221AB201DD@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3309 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 588b9cc28b5515f1d8f862b18f538586b9051ed1 (commit)
via a11f51364d2f59e51bed2f6a318da304f1464aed (commit)
via 8f4a16b593b8c5b2f3d312d3248c9ca98f964fa3 (commit)
from 7c69f2c242898e586dc77e79bcfb1ea225e7fd30 (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 588b9cc28b5515f1d8f862b18f538586b9051ed1
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Nov 11 14:31:15 2012 +0100
gnutls: Update to 3.1.4.
Requires up-to-date versions of p11-kit and libtasn1.
commit a11f51364d2f59e51bed2f6a318da304f1464aed
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Nov 11 14:30:55 2012 +0100
libtasn1: Update to 3.0.
commit 8f4a16b593b8c5b2f3d312d3248c9ca98f964fa3
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Nov 11 14:30:42 2012 +0100
p11-kit: Update to 0.14.
-----------------------------------------------------------------------
Summary of changes:
gnutls/gnutls.nm | 8 ++++----
libtasn1/libtasn1.nm | 4 ++--
p11-kit/p11-kit.nm | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
Difference in files:
diff --git a/gnutls/gnutls.nm b/gnutls/gnutls.nm
index 4371149..d634615 100644
--- a/gnutls/gnutls.nm
+++ b/gnutls/gnutls.nm
@@ -4,7 +4,7 @@
###############################################################################
name = gnutls
-version = 3.1.3
+version = 3.1.4
release = 1
groups = System/Libraries
@@ -27,11 +27,11 @@ build
gettext
guile-devel
libgcrypt-devel
- libtasn1-devel
+ libtasn1-devel >= 3.0
lzo-devel
nettle-devel >= 2.5
perl
- p11-kit-devel >= 0.4
+ p11-kit-devel >= 0.14
readline-devel
zlib-devel
end
@@ -55,7 +55,7 @@ packages
package %{name}
requires
nettle >= 2.5
- p11-kit >= 0.4
+ p11-kit >= 0.14
end
end
diff --git a/libtasn1/libtasn1.nm b/libtasn1/libtasn1.nm
index b130a59..eda7e9f 100644
--- a/libtasn1/libtasn1.nm
+++ b/libtasn1/libtasn1.nm
@@ -4,7 +4,7 @@
###############################################################################
name = libtasn1
-version = 2.9
+version = 3.0
release = 1
groups = System/Libraries
@@ -17,7 +17,7 @@ description
be found at http://www.gnu.org/software/gnutls and http://www.gnutls.org.
end
-source_dl =
+source_dl = http://ftp.gnu.org/gnu/libtasn1/
build
requires
diff --git a/p11-kit/p11-kit.nm b/p11-kit/p11-kit.nm
index 6280201..16b754e 100644
--- a/p11-kit/p11-kit.nm
+++ b/p11-kit/p11-kit.nm
@@ -4,7 +4,7 @@
###############################################################################
name = p11-kit
-version = 0.7
+version = 0.14
release = 1
groups = System/Libraries
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-11-11 13:31 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=20121111133147.221AB201DD@argus.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