public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. c955da5a71e3b553d83c4cd304149b06d791a5e4
Date: Mon, 08 Jul 2013 21:34:52 +0200	[thread overview]
Message-ID: <20130708193453.B89B2202C1@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2852 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  c955da5a71e3b553d83c4cd304149b06d791a5e4 (commit)
      from  f1561badd0b8b780ca96111a8582be957806011d (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 c955da5a71e3b553d83c4cd304149b06d791a5e4
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Jul 8 21:34:27 2013 +0200

    gnutls: Add patch to fix pem-decoding error in testsuite.

-----------------------------------------------------------------------

Summary of changes:
 gnutls/gnutls.nm                               |  2 +-
 gnutls/patches/gnutls-3.2.1-pem-decoding.patch | 35 ++++++++++++++++++++++++++
 2 files changed, 36 insertions(+), 1 deletion(-)
 create mode 100644 gnutls/patches/gnutls-3.2.1-pem-decoding.patch

Difference in files:
diff --git a/gnutls/gnutls.nm b/gnutls/gnutls.nm
index 070a7fc..9d1f727 100644
--- a/gnutls/gnutls.nm
+++ b/gnutls/gnutls.nm
@@ -7,7 +7,7 @@ name       = gnutls
 version    = %{ver_maj}.%{ver_min}
 ver_maj    = 3.2
 ver_min    = 1
-release    = 1.1
+release    = 1.2
 
 groups     = System/Libraries
 url        = http://www.gnu.org/software/gnutls/
diff --git a/gnutls/patches/gnutls-3.2.1-pem-decoding.patch b/gnutls/patches/gnutls-3.2.1-pem-decoding.patch
new file mode 100644
index 0000000..2764f8b
--- /dev/null
+++ b/gnutls/patches/gnutls-3.2.1-pem-decoding.patch
@@ -0,0 +1,35 @@
+From b12040aeab5fbaf02677571db1d8bf1995bd5ee0 Mon Sep 17 00:00:00 2001
+From: Nikos Mavrogiannopoulos <nmav(a)gnutls.org>
+Date: Sun, 2 Jun 2013 12:10:06 +0200
+Subject: [PATCH] Avoid comparing the expiration date to prevent false positive error in 32-bit systems.
+
+---
+ tests/cert-tests/pem-decoding |    6 ++++--
+ 1 files changed, 4 insertions(+), 2 deletions(-)
+
+diff --git a/tests/cert-tests/pem-decoding b/tests/cert-tests/pem-decoding
+index fe769ec..f8c6372 100755
+--- a/tests/cert-tests/pem-decoding
++++ b/tests/cert-tests/pem-decoding
+@@ -61,7 +61,9 @@ if test "$rc" != "0"; then
+   exit $rc
+ fi
+ 
+-diff $srcdir/complex-cert.pem tmp-pem.pem
++cat $srcdir/complex-cert.pem |grep -v "Not After:" >tmp1
++cat $srcdir/tmp-pem.pem |grep -v "Not After:" >tmp2
++diff tmp1 tmp2
+ rc=$?
+ 
+ if test "$rc" != "0"; then
+@@ -69,6 +71,6 @@ if test "$rc" != "0"; then
+   exit $rc
+ fi
+ 
+-rm -f tmp-pem.pem
++rm -f tmp-pem.pem tmp1 tmp2
+ 
+ exit 0
+-- 
+1.7.1
+


hooks/post-receive
--
IPFire 3.x development tree

                 reply	other threads:[~2013-07-08 19:34 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=20130708193453.B89B2202C1@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