From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: libxml2 2.9.4-1
Date: Fri, 26 Aug 2016 23:00:00 -0000 [thread overview]
Message-ID: <201608262252.u7QMqUcp023730@int-mx13.intmail.prod.int.phx2.redhat.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* libxml2-2.9.4-1
* libxml2-devel-2.9.4-1
* libxml2-doc-2.9.4-1
* python-libxml2-2.9.4-1
* python3-libxml2-2.9.4-1
* mingw64-i686-libxml2-2.9.4-1
* mingw64-x86_64-libxml2-2.9.4-1
Libxml2 is the XML C parser and toolkit developed for the GNOME project.
XML itself is a metalanguage to design markup languages, i.e. text language
where semantic and structure are added to the content using extra 'markup'
information enclosed between angle brackets. HTML is the most well- known
markup language. Though the library is written in C, a variety of language
bindings make it available in other environments.
This is an update to the latest upstream release, which includes fixes for
CVE-2016-1762, CVE-2016-1833, CVE-2016-1834, CVE-2016-1835, CVE-2016-1836,
CVE-2016-1837, CVE-2016-1838, CVE-2016-1839, CVE-2016-1840, CVE-2016-4447,
CVE-2016-4448, and CVE-2016-4449:
https://bugzilla.redhat.com/show_bug.cgi?id=1338682
https://bugzilla.redhat.com/show_bug.cgi?id=1338686
https://bugzilla.redhat.com/show_bug.cgi?id=1338691
https://bugzilla.redhat.com/show_bug.cgi?id=1338696
https://bugzilla.redhat.com/show_bug.cgi?id=1338700
https://bugzilla.redhat.com/show_bug.cgi?id=1338701
https://bugzilla.redhat.com/show_bug.cgi?id=1338702
https://bugzilla.redhat.com/show_bug.cgi?id=1338703
https://bugzilla.redhat.com/show_bug.cgi?id=1338705
https://bugzilla.redhat.com/show_bug.cgi?id=1338706
https://bugzilla.redhat.com/show_bug.cgi?id=1338708
https://bugzilla.redhat.com/show_bug.cgi?id=1338711
--
Yaakov
reply other threads:[~2016-08-26 23:00 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=201608262252.u7QMqUcp023730@int-mx13.intmail.prod.int.phx2.redhat.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).