Bug 884707

Summary: xmlDOMWrapCloneNode discards namespace of the node parameter
Product: Red Hat Enterprise Linux 5 Reporter: Šimon Lukašík <slukasik>
Component: libxml2Assignee: Daniel Veillard <veillard>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-tools-bugs
Severity: high Docs Contact:
Priority: high    
Version: 5.10CC: arubin, bgollahe, jpallich, mcermak, mpreisle, ohudlick, pvrabec, sgrubb
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libxml2-2.6.26-2.1.22.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 11:09:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 871120, 915837, 1007428    
Attachments:
Description Flags
reproducer.xml
none
reproducer.c none

Description Šimon Lukašík 2012-12-06 15:41:50 UTC 
Description of problem:
xmlDOMWrapCloneNode discards namespace of the @node parameter.

I am attaching small reproducer. And git bisect shows that this
has been fixed in upstream since:
978039bbd89fa2daada209e270524d20c9e3ca7e

Version-Release number of selected component (if applicable):
libxml2-2.6.26-2.1.21.el5

How reproducible:
deterministic

Steps to Reproduce:
1. Run attached reproducer
2. 
3.
  
Actual results:
Reproducer fails. And resulting document is exported without namespace.

Expected results:
Reproducer passes. And resulting document has the same 

Additional info:
Comment 1 Šimon Lukašík 2012-12-06 15:43:47 UTC 
Created attachment 658813 [details]
reproducer.xml

This is an input XML file for the reproducer.

Note that Benchmark element within the file is in the 'xccdf' namespace
Comment 2 Šimon Lukašík 2012-12-06 15:46:01 UTC 
Created attachment 658814 [details]
reproducer.c
Comment 4 Daniel Veillard 2012-12-12 06:22:12 UTC 
Okay, patches backports easilly, so technically that should not be a problem !

Daniel
Comment 9 Daniel Veillard 2013-01-28 16:39:08 UTC 
Build libxml2-2.6.26-2.1.22.el5 includes the fix,

Daniel