Hei hei,

libxml2 2.9.11 and 2.9.12 were released just recently, containing an
important security fix and lots of other fixes.  libxslt had to be
updated then to fix a build failure against the new libxml2.

Greets
Alex

Alexander Dahl (2):
  libxml2: version bump 2.9.10 -> 2.9.12
  libxslt: version bump 1.1.29 -> 1.1.34

 ...e-loop-in-xmlStringLenDecodeEntities.patch | 28 ------------------
 ...mory-leak-in-xmlSchemaValidateStream.patch | 29 -------------------
 patches/libxml2-2.9.10/series                 |  8 -----
 ...200-xml2-config-is-not-SYSROOT-aware.patch |  0
 patches/libxml2-2.9.12/series                 |  6 ++++
 patches/libxslt-1.1.29/series                 |  4 ---
 ...ml2-config-check-in-configure-script.patch | 23 +++++++++++++++
 ...200-xslt-config-add-SYSROOT-support.patch} |  4 +--
 patches/libxslt-1.1.34/autogen.sh             |  1 +
 patches/libxslt-1.1.34/series                 |  7 +++++
 rules/libxml2.make                            |  6 ++--
 rules/libxslt.make                            | 10 ++++---
 12 files changed, 48 insertions(+), 78 deletions(-)
 delete mode 100644 
patches/libxml2-2.9.10/0001-Fix-infinite-loop-in-xmlStringLenDecodeEntities.patch
 delete mode 100644 
patches/libxml2-2.9.10/0002-Fix-memory-leak-in-xmlSchemaValidateStream.patch
 delete mode 100644 patches/libxml2-2.9.10/series
 rename patches/{libxml2-2.9.10 => 
libxml2-2.9.12}/0200-xml2-config-is-not-SYSROOT-aware.patch (100%)
 create mode 100644 patches/libxml2-2.9.12/series
 delete mode 100644 patches/libxslt-1.1.29/series
 create mode 100644 
patches/libxslt-1.1.34/0001-Fix-xml2-config-check-in-configure-script.patch
 rename patches/{libxslt-1.1.29/0001-xslt-config-add-SYSROOT-support.patch => 
libxslt-1.1.34/0200-xslt-config-add-SYSROOT-support.patch} (87%)
 create mode 120000 patches/libxslt-1.1.34/autogen.sh
 create mode 100644 patches/libxslt-1.1.34/series


base-commit: e999e3a92a2fb0ec9ae249bd1f043f05d74dea90
-- 
2.20.1


_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to 
[email protected]

Reply via email to