Some of your Debian packages might need attention

[Jay Bonci]

Hey everybody, 
    I'm looking at the XML::SAX thing right now. There are a couple of
solutions. 

    One of which is to simply reorder the final list with some perl hack so
that XML::SAX::PurePerl is never set as the default unless it started that
way. 

    The suggested method in the bug of a SAX-based priority parser election
doesn't really seem to make good organizational sense. It'd have to be a
fairly large upstream change to the file, which we could work out if that's
kind of what everbody wants.

    Would simply making sure that XML::SAX::PurePerl isn't the default
parser seem like a solution with an obvious pitfall (either due to extreme
ingrace or something technical).  That and a new version should address
everything.  I can do a general rework, but it'll take some time to trace
through and fix everything.

-Jay
  Apologies for no signature due to work email.


On 7/3/07 2:29 PM, "Niko Tyni" <ntyni at iki.fi> wrote:

> On Tue, Jul 03, 2007 at 08:38:43AM -0500, Gunnar Wolf wrote:
>  
>> Niko, as you are clearly more involved in this than me: You submitted
>> two patches to #419757. The bug report also mentions upgrading to a
>> newer upstream version. Does the upstream version include the patches
>> for this problem?
> 
> Yes, upstream 0.16 fixes #419757 and should make libxml-filter-sort-perl
> build again (#419689). The other patch was a minor warning issue (#419758)
> already fixed in 0.15.
> 
> However, the situation is a bit more complicated than that. The 0.14
> upload also caused #405186. I have sent a patch for it upstream (CPAN
> #26588), but for some reason it wasn't included in the recent upstream
> 0.16 release.
> 
> Furthermore, as described in #430118, the parser used by XML::SAX is now
> almost always XML::SAX::PurePerl (included in libxml-sax-perl), which is
> generally not desirable. Even the XML::SAX upstream maintainer doesn't
> recommend using the PurePerl parser; see his comments in CPAN #26588.
> 
> Thus the main blocker to get libxml-sax-perl into a decent state is really
> #430118, and fixing it would probably make the other bugs irrelevant
> since everyone would rush to use XML::SAX::Expat.
> 
> In any case, uploading 0.16 would certainly be an improvement to the
> current situation.
> 
> Hope I got the bug numbers right,