Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method "getXMLDecl" via package "XML::DOM::Element"

2017-08-01 Thread intrigeri 
Niko Tyni:
> There's been no reaction on the upstream bug, and the last upstream
> release was in 2002. There are no reverse dependencies. I suggest
> removal unless somebody objects?

Requested: https://bugs.debian.org/870424

Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method "getXMLDecl" via package "XML::DOM::Element"

2016-05-21 Thread Niko Tyni 
On Fri, Sep 04, 2015 at 11:06:20PM +0300, Niko Tyni wrote:
> Control: tag -1 sid stretch
> 
> On Sat, Aug 29, 2015 at 10:38:43AM +0100, Dominic Hargreaves wrote:
> > Source: libxml-easyobj-perl
> > Version: 1.12-3
> > Severity: serious
> > Justification: FTBFS
> > 
> > This package FTBFS in a clean sid chroot:
> > 
> > Can't locate object method "getXMLDecl" via package "XML::DOM::Element" at 
> > /usr/
> > share/perl5/XML/DOM.pm line 1221.
> > t/write.t . 
> 
> This was apparently broken by libxml-dom-perl 1.44-2, which added 
> debian/patches/output_encoding.patch . Now that the patch was
> integrated upstream in XML-DOM-1.45, it's probably failing upstream
> too. 

Confirmed; there's an upstream bug

for this as well.

> Not sure if XML::EasyObj is doing something nasty or if > printing
out XML::DOM::Element objects is broken for everybody...

There's been no reaction on the upstream bug, and the last upstream
release was in 2002. There are no reverse dependencies. I suggest
removal unless somebody objects?
-- 
Niko Tyni   nt...@debian.org

Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method "getXMLDecl" via package "XML::DOM::Element"

2015-09-09 Thread Chris Lamb 
merge 797289 798488
thanks

Oh, this was already filed. (How did I miss this..)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: Re: Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method "getXMLDecl" via package "XML::DOM::Element"

2015-09-04 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 sid stretch
Bug #797289 [src:libxml-easyobj-perl] libxml-easyobj-perl: FTBFS: Can't locate 
object method "getXMLDecl" via package "XML::DOM::Element"
Added tag(s) sid and stretch.

-- 
797289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method "getXMLDecl" via package "XML::DOM::Element"

2015-09-04 Thread Niko Tyni 
Control: tag -1 sid stretch

On Sat, Aug 29, 2015 at 10:38:43AM +0100, Dominic Hargreaves wrote:
> Source: libxml-easyobj-perl
> Version: 1.12-3
> Severity: serious
> Justification: FTBFS
> 
> This package FTBFS in a clean sid chroot:
> 
> Can't locate object method "getXMLDecl" via package "XML::DOM::Element" at 
> /usr/
> share/perl5/XML/DOM.pm line 1221.
> t/write.t . 

This was apparently broken by libxml-dom-perl 1.44-2, which added 
debian/patches/output_encoding.patch . Now that the patch was
integrated upstream in XML-DOM-1.45, it's probably failing upstream
too. 

Not sure if XML::EasyObj is doing something nasty or if
printing out XML::DOM::Element objects is broken for everybody...
-- 
Niko Tyni   nt...@debian.org

Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method getXMLDecl via package XML::DOM::Element

2015-08-29 Thread Dominic Hargreaves 
Source: libxml-easyobj-perl
Version: 1.12-3
Severity: serious
Justification: FTBFS

This package FTBFS in a clean sid chroot:

Can't locate object method getXMLDecl via package XML::DOM::Element at /usr/
share/perl5/XML/DOM.pm line 1221.
t/write.t . 
1..11
# Running under perl version 5.020002 for linux
# Current time local: Fri Aug 28 19:12:33 2015
# Current time GMT:   Fri Aug 28 19:12:33 2015
# Using Test.pm version 1.26
ok 1
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 10/11 subtests 
Failed 1/5 test programs. 0/33 subtests failed.

Test Summary Report
---
t/write.t   (Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 11 tests but ran 1.
Files=5, Tests=33,  1 wallclock secs ( 0.07 usr  0.05 sys +  1.16 cusr  0.14 
csys =  1.42 CPU)
Result: FAIL

Cheers,
Dominic.