xslt:copy element is broken in 2.6.29

Bug #147144 reported by Michael Gratton
4
Affects Status Importance Assigned to Milestone
libxml2
Fix Released
High
libxml2 (Ubuntu)
Fix Released
Medium
Matthias Klose
Nominated for Gutsy by Michael Gratton

Bug Description

Binary package hint: libxml2

In libxml 2.6.29 in gutsy, using the XSLT copy element causes the folllowing error:

runtime error: file /home/mjg/[...]/web/style/default.xslt line 306 element copy
Attribute nodes must be added before any child nodes to an element.

Eg:

  <xsl:template match="@*|html:*">
    <xsl:copy>
      <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
  </xsl:template>

This is fixed apparently in 2.6.30, see https://bugzilla.novell.com/show_bug.cgi?id=300675

Downgrading to libxml2 2.6.27 from fiesty also fixes the problem.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for your report.

Changed in libxml2:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
Changed in libxml2:
status: Unknown → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote :

2.6.30 is in Debian, so someone would have to file an upstream version freeze exception and provide a debdiff for the merge to get this into Gutsy.

Changed in libxml2:
status: New → Fix Committed
Revision history for this message
Matthias Klose (doko) wrote :

- set back to "confirmed"
- investigating if 2.6.30 is appropriate at this point

Changed in libxml2:
assignee: desktop-bugs → doko
status: Fix Committed → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :
Revision history for this message
Matthias Klose (doko) wrote :
Revision history for this message
Matthias Klose (doko) wrote :

- attached are the changelog, the diffstat (code only), and the debdiff.
- the new subminor version adds bugs fixes only.
- test packages at http://people.ubuntu.com/~doko/tmp/libxml2/
- please recheck with the test build

Revision history for this message
Michael Gratton (mjog) wrote :

After installing the packages above I can't reproduce the error. Then, after dowgrading back to 2.6.29.dfsg-1ubuntu1 the error reappears, so it seems that 2.6.30.dfsg-2ubuntu1 fixes it.

Revision history for this message
Martin Pitt (pitti) wrote :

bug fixes only, fine for me.

Revision history for this message
Matthias Klose (doko) wrote :

libxml2 (2.6.30.dfsg-2ubuntu1) gutsy; urgency=low

  * Merge with Debian; remaining changes:
    - debian/rules: create a udeb for debian-installer, correct libxml2-dev
      Depends to include zlib1g-dev.
    - Build a python-libxml2-dbg package.
  * Fixes a regression using XSLT copy element. LP: #147144.

libxml2 (2.6.30.dfsg-2) unstable; urgency=low

  * libxml.h: define _LARGEFILE64_SOURCE to properly get gzopen64 defines in
    zlib.h. Closes: #439843. Thanks Dann Frazier.

libxml2 (2.6.30.dfsg-1) unstable; urgency=low

  * New upstream release.

 -- Matthias Klose <email address hidden> Wed, 03 Oct 2007 14:35:16 +0200

Changed in libxml2:
status: Confirmed → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

libxml2 (2.6.30.dfsg-3ubuntu1) hardy; urgency=low

  * Merge with Debian; remaining changes:
    - debian/rules: create a udeb for debian-installer, correct libxml2-dev
      Depends to include zlib1g-dev.
    - Build a python-libxml2-dbg package.
    - Fix a regression using XSLT copy element. LP: #147144.
  * Link using -Bsymbolic-functions.

libxml2 (2.6.30.dfsg-3) unstable; urgency=low

  * debian/libxml2.symbols: Add a symbols file to benefit from the new
    features in dpkg-shlibdeps.
  * debian/control: Build depend on debhelper (>= 5.0.61) and dpkg-dev (>=
    1.14.9), accordingly.
  * debian/rules:
    + Apply rules suggested in autotools-dev documentation.
    + Add -Wl,--as-needed to LDFLAGS so that useless dependencies are not
    added.
  * Makefile.am, Makefile.in: Don't build noinst targets.

 -- Matthias Klose <email address hidden> Wed, 05 Dec 2007 19:50:33 +0000

Changed in libxml2:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.