all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 0/3] Expat and libxslt changes for core-updates
Date: Tue,  7 Jun 2016 20:54:05 -0400	[thread overview]
Message-ID: <cover.1465347219.git.leo@famulari.name> (raw)

It was not that simple to make these changes for core-updates, so I'm
sending the patches for review.

For expat, I "re-fix" a bug that was fixed on master already. This
bug-fix is actually reachable from the HEAD of core-updates, but for
some reason doesn't exist at HEAD. According to MITRE the bug does
affect all currently released versions of expat:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

I noticed a "left-over" patch for a bug that is apparently fixed in the
version of expat on core-updates (2.1.1), so it is deleted:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1283

For libxslt, I update to the latest version and remove patches that are
no longer needed. The timestamp issue was addressed upstream [0] and the
bug has been fixed in this version. These patches were strangely no
longer listed in 'gnu/local.mk'.

[0]
https://git.gnome.org/browse/libxslt/commit/?id=e57df303eca25a2a3f9e0625c29f4b20177858cc

Leo Famulari (3):
  gnu: expat: Fix CVE-2016-0718.
  gnu: Remove unused patch.
  gnu: libxslt: Update to 1.1.29.

 gnu/local.mk                                       |  1 -
 .../patches/expat-CVE-2015-1283-refix.patch        | 42 --------------
 gnu/packages/patches/libxslt-CVE-2015-7995.patch   | 29 ----------
 .../patches/libxslt-remove-date-timestamps.patch   | 66 ----------------------
 gnu/packages/xml.scm                               |  9 ++-
 5 files changed, 4 insertions(+), 143 deletions(-)
 delete mode 100644 gnu/packages/patches/expat-CVE-2015-1283-refix.patch
 delete mode 100644 gnu/packages/patches/libxslt-CVE-2015-7995.patch
 delete mode 100644 gnu/packages/patches/libxslt-remove-date-timestamps.patch

-- 
2.8.3

             reply	other threads:[~2016-06-08  0:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08  0:54 Leo Famulari [this message]
2016-06-08  0:54 ` [PATCH 1/3] gnu: expat: Fix CVE-2016-0718 Leo Famulari
2016-06-08 13:25   ` Ludovic Courtès
2016-06-09 16:20     ` Leo Famulari
2016-06-08  0:54 ` [PATCH 2/3] gnu: Remove unused patch Leo Famulari
2016-06-08 13:25   ` Ludovic Courtès
2016-06-08  0:54 ` [PATCH 3/3] gnu: libxslt: Update to 1.1.29 Leo Famulari
2016-06-08 13:26   ` Ludovic Courtès
2016-06-08 10:10 ` [PATCH 0/3] Expat and libxslt changes for core-updates Efraim Flashner
2016-06-08 11:50   ` Leo Famulari
2016-06-08 11:55     ` Leo Famulari
2016-06-08 13:27   ` Ludovic Courtès
2016-06-09 16:26   ` Leo Famulari
2016-06-09 16:43   ` Leo Famulari
2016-06-09 23:19     ` Leo Famulari
2016-06-10 12:59       ` Ludovic Courtès
2016-06-11  0:49         ` Leo Famulari
2016-06-12 20:26           ` Ludovic Courtès
2016-06-13  2:20             ` Leo Famulari
2016-06-13 15:05               ` Ludovic Courtès

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=cover.1465347219.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.