Bug 556701 - libxml2 schemas parser error
Summary: libxml2 schemas parser error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libxml2
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-19 06:09 UTC by David Ward
Modified: 2014-06-03 12:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-03 12:13:00 UTC
Target Upstream Version:
Embargoed:
david.ward: needinfo-
david.ward: needinfo-


Attachments (Terms of Use)
XML schema file (41.31 KB, application/xml)
2010-01-19 06:09 UTC, David Ward
no flags Details
sample XML file (351 bytes, text/xml)
2010-01-19 06:10 UTC, David Ward
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 347316 0 None None None Never

Description David Ward 2010-01-19 06:09:49 UTC
Created attachment 385318 [details]
XML schema file

libxml2 included with RHEL 5.4 (version 2.6.26-2.1.2.8) throws a "schemas parser error" on an XML schema file (attached) that I believe to be valid:

$ xmllint --schema EmulationScriptSchema.xsd emulationscript.xml 
EmulationScriptSchema.xsd:324: element complexType: Schemas parser error : local complex type: The content type must specify a particle.
EmulationScriptSchema.xsd:867: element complexType: Schemas parser error : local complex type: The content type must specify a particle.
WXS schema EmulationScriptSchema.xsd failed to compile
<?xml version="1.0" encoding="UTF-8"?>
[...]


I downloaded the libxml2 source RPM from Fedora 12 (version 2.7.6-1), re-built it for RHEL 5, and installed it.  Afterwards, the error is gone:

$ xmllint --schema EmulationScriptSchema.xsd emulationscript.xml 
<?xml version="1.0" encoding="UTF-8"?>
[...]


Please fix the bug in libxml2 version 2.6, or update RHEL 5 to use version 2.7.

The XML schema file and sample XML file are attached.  They are taken from the source code of EMANE 0.6.1 by CenGen (http://labs.cengen.com/emane), an open-source wireless network emulator.

Comment 1 David Ward 2010-01-19 06:10:26 UTC
Created attachment 385319 [details]
sample XML file

Comment 2 David Ward 2010-01-19 06:21:18 UTC
Upstream bug 347316 appears to be the relevant fix that needs to be imported into RHEL 5.

Comment 3 David Ward 2010-01-19 07:24:36 UTC
Tested the patch for libxml2 bug 347316 applied to the RHEL 5 libxml2 RPM, and it fixed the problem. Patch is at:

http://git.gnome.org/browse/libxml2/patch/?id=f896d44aac4e8a8e1bb60a0bbe8e8107ae2ba72c

Comment 4 David Ward 2010-03-05 14:51:41 UTC
Can I please check the status of this?  This bug should be very easy to resolve (I've already provided the patch and have been using it successfully for over a month).  The latest released package from Red Hat is breaking my software.  Thank you.

Comment 5 Michal Nowak 2010-03-22 09:55:20 UTC
David Ward, if you are RHEL customer you should ask our support team via Issue Tracker to get the support you expect. Thank You.

Comment 6 RHEL Program Management 2014-03-07 12:13:48 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in the  last planned RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX. To request that Red Hat re-consider this request, please re-open the bugzilla via  appropriate support channels and provide additional business and/or technical details about its importance to you.

Comment 7 RHEL Program Management 2014-06-03 12:13:00 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).


Note You need to log in before you can comment on or make changes to this bug.