summaryrefslogtreecommitdiff
path: root/debian/patches/0056-Stop-parsing-on-entities-boundaries-errors.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches/0056-Stop-parsing-on-entities-boundaries-errors.patch')
-rw-r--r--debian/patches/0056-Stop-parsing-on-entities-boundaries-errors.patch28
1 files changed, 0 insertions, 28 deletions
diff --git a/debian/patches/0056-Stop-parsing-on-entities-boundaries-errors.patch b/debian/patches/0056-Stop-parsing-on-entities-boundaries-errors.patch
deleted file mode 100644
index d0d9a79..0000000
--- a/debian/patches/0056-Stop-parsing-on-entities-boundaries-errors.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-From: Daniel Veillard <veillard@redhat.com>
-Date: Mon, 23 Feb 2015 11:17:35 +0800
-Subject: Stop parsing on entities boundaries errors
-
-For https://bugzilla.gnome.org/show_bug.cgi?id=744980
-
-There are times, like on unterminated entities that it's preferable to
-stop parsing, even if that means less error reporting. Entities are
-feeding the parser on further processing, and if they are ill defined
-then it's possible to get the parser to bug. Also do the same on
-Conditional Sections if the input is broken, as the structure of
-the document can't be guessed.
----
- parser.c | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/parser.c b/parser.c
-index c187327..f96cd5f 100644
---- a/parser.c
-+++ b/parser.c
-@@ -5653,6 +5653,7 @@ xmlParseEntityDecl(xmlParserCtxtPtr ctxt) {
- if (RAW != '>') {
- xmlFatalErrMsgStr(ctxt, XML_ERR_ENTITY_NOT_FINISHED,
- "xmlParseEntityDecl: entity %s not terminated\n", name);
-+ xmlStopParser(ctxt);
- } else {
- if (input != ctxt->input) {
- xmlFatalErrMsg(ctxt, XML_ERR_ENTITY_BOUNDARY,