Alexander Zangerl dijo [Wed, Sep 08, 2004 at 12:17:30AM +1000]: > >If so, please act on > >this bug report - This module is already part of the current stable > >release, and it would not be good to lose it for Sarge. The bug seems > >quite simple to fix. > > i've spent about a day digging through the xml parser mess, to no > avail. upstream (a colleague of mine) has spent some fruitless time > on the 5.8 problem, given up and is currently busy finalising the > new version of the package (which is a complete rewrite, so the > current code is doomed anyway - but i plan to reintroduce the new > version in sarge+1 anyway). > > i certainly don't think the problem is overly simple, but i'm happy > to be convinced otherwise :-)
Well, I certainly didn't go into much detail with it, but I just tried this at my computer. I just deleted the 'build-conflicts: perl (>= 5.8)' and the corresponding 'conflicts', modified the build-dependency on libtest-simple-perl for perl-modules (which now provides it), and it seems to go fine... Whoops, no, my wrong - I thought it was right, but I got 4/11 test scripts dying on me :-( > >I am not uploading a NMU because I prefer hearing directly from > >you. > > please feel free to nmu - or, preferrably, give me a tip for that bug. > i'll tag it help for the time being. As I don't use this module (it only bothers me to see Perl modules with RC bugs ;-) ), I would prefer you to find an adequate solution ;-) I would probably get something wrong -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5554-9450 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
