reassign 546990 libxml2
thanks
Daniel Leidert wrote:
> Hi,
>
> I also stumbled over this issue. This is what I can say about it:
>
> - downgrading subversion-tools does not work
> - however, in a Lenny CHROOT the whole thing works
>
> Both let me think, that it might not be a bug in svn2cl. What happens
> is, that in the "wrap" template the test
>
> <xsl:when test="contains($txt,'&newl;')">
>
> succeeds, when the text contains a space and
>
> substring-before($txt,'&newl;')
>
> then splits the text into words. This goes a slong as there is still a
> space in the text left. When there is no text left, the lines:
>
> <!-- this is easy, nothing to do -->
> <xsl:value-of select="$normtxt" />
> <!-- add newline -->
> <xsl:text>&newl;</xsl:text>
>
> output every word followed by a newline.
>
> I have no idea why the test succeeds and why the result returned by
> substring-before() is the text before the space.
>
> BUT: Downgrading libxml2 to the version in Squeeze works. So this seems
> to be a bug(?) in libxml2.
It seems indeed that libxml2 could be the problem. I regularly execute
svn2cl and it worked on 11/09 and did not work at 14/09 => something
broke between these two dates. And I see in libxml2 changelog:
libxml2 (2.7.4.dfsg-2) unstable; urgency=low
* debian/libxml2.symbols: Force binaries that use versioned symbols to
depend on version 2.7.4 at least.
* parser.c: Fix a parsing problem with little data at startup.
Cherry-picked from upstream git. Closes: #546254, #546488.
-- Mike Hommey <[email protected]> Wed, 16 Sep 2009 00:12:50 +0200
libxml2 (2.7.4.dfsg-1) unstable; urgency=low
* New upstream release.
* Revert old change to entities.c.
* debian/copyright: Change upstream url. Closes: #541082.
* debian/libxml2.symbols: Change symbols file to use newly introduced
symbol versioning
* debian/rules: bump shlibs to current version.
-- Mike Hommey <[email protected]> Thu, 10 Sep 2009 23:04:35 +0200
It might well be 2.7.4.dfsg-1 which introduced this problem.
Re-assigning bug to libxml2.
--
Eugen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
