Bug 871770 - Problem with DTD validation
Summary: Problem with DTD validation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libxml2
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-31 10:56 UTC by Nicolas Morey
Modified: 2013-08-01 18:39 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 18:39:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Test Case (380 bytes, text/x-csrc)
2012-10-31 10:56 UTC, Nicolas Morey
no flags Details
XML Sample file (722 bytes, text/xml)
2012-10-31 10:59 UTC, Nicolas Morey
no flags Details
Sample DTD (2.36 KB, application/xml-dtd)
2012-10-31 10:59 UTC, Nicolas Morey
no flags Details

Description Nicolas Morey 2012-10-31 10:56:44 UTC
Created attachment 636016 [details]
Test Case

Description of problem:
When parsing an XML file with a DTD an DTD validation enabled, parsing breaks with error "No declaration for attribute id of element platform".
Same parsing works on previous versions. 

Version-Release number of selected component (if applicable):
Works with libxml2-2.7.8-7. Broken with 2.7.8-8 and 2.7.8-9

How reproducible:
Always

Steps to Reproduce:
1. Compile xmltest.c with 'gcc -o xmltest xmltest.c -I/usr/include/libxml2 -lxml2'

2. Put x86.xml and myDTD.dtd into the same directory
3. Run ./xmltest
  
Actual results:
element platform: validity error : No declaration for attribute id of element platform
rkstation" execution_type="hypervised" ignore_constraints="1" default_type="x86"

Expected results:
Parsing should be OK

Additional info:
Running xmllint --valid on the same file produces no error message

Comment 1 Nicolas Morey 2012-10-31 10:59:16 UTC
Created attachment 636017 [details]
XML Sample file

Comment 2 Nicolas Morey 2012-10-31 10:59:43 UTC
Created attachment 636018 [details]
Sample DTD

Comment 3 Daniel Veillard 2012-11-01 10:57:59 UTC
Tiens un ensimag ! Bonjour de Chine !

You're hitting that bug:

https://bugzilla.gnome.org/show_bug.cgi?id=684774

fix is there:

http://git.gnome.org/browse/libxml2/commit/?id=6c91aa384f48ff6d406553a6dd47fd556c1ef2e6

I didn't make a build for Fedora yet, probably once 2.9.1 is out
within 1-2 weeks,

Daniel

Comment 4 nmorey 2012-11-02 07:47:51 UTC
Bonjour la Chine ;)

Thanks for the info, I'll wait till a new package is out and try it out then.

Comment 5 Fedora End Of Life 2013-07-04 06:58:35 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 nmorey 2013-07-04 07:49:48 UTC
This seems fixed in FC19. I haven't check it on FC18

Comment 7 Daniel Veillard 2013-07-05 13:03:30 UTC
Yeah sorry it wasn't too critical, so i didn't pushed on F17,

Daniel

Comment 8 Fedora End Of Life 2013-08-01 18:39:50 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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