[elbe-devel] elbe 1.9.13 fails on extracting licenses (jessie)

[Manuel Traut]

Hi Erich,
 
> Good point. After removing the empty <archive> tag, and after removing
> any comments[1] in the .xml file, the error message changes. And that was
> most likely the reason I blamed it to the license stuff:
> 
> >Build failed
> >Traceback (most recent call last):
> >  File "/usr/lib/python2.7/dist-packages/elbepack/asyncworker.py",
> >line 116, in execute
> >    skip_pbuild=self.skip_pbuilder)
> >  File "/usr/lib/python2.7/dist-packages/elbepack/elbeproject.py",
> >line 291, in build
> >    self.buildenv.rfs.write_licenses(f, self.log, os.path.join(
> >self.builddir, "licence.xml"))
> >  File "/usr/lib/python2.7/dist-packages/elbepack/efilesystem.py",
> >line 131, in write_licenses
> >    licence_xml = copyright_xml()
> >  File "/usr/lib/python2.7/dist-packages/elbepack/licencexml.py",
> >line 57, in __init__
> >    self.outxml = etree (None)
> >  File "/usr/lib/python2.7/dist-packages/elbepack/treeutils.py",
> >line 111, in __init__
> >    et = parse (fname, parser=parser)
> >  File "lxml.etree.pyx", line 3299, in lxml.etree.parse
> >(src/lxml/lxml.etree.c:72655)
> >  File "parser.pxi", line 1814, in lxml.etree._parseDocument
> >(src/lxml/lxml.etree.c:106512)
> >TypeError: cannot parse from 'NoneType'
> >
> >
> >Exception:
> >cannot parse from 'NoneType'
> 
> The effects are that
> 1. elbe-build-*/licence.txt has size zero,
> 2. sda.img.gz is not produced or not downloaded ... let me check.
>    It seems sda.img.gz is not even produced.
> 
> So I disable the extraction of the licenses, just to make sure ...
> building ...
> 1. licence.txt is not produced/downloaded any more, OK.
> 2. sda.img.gz is produced and downloaded, OK!
> 
> 
> Thank you for your patience.
> Cheers,
> Erich
> 
> 
> [1] is there a reason that lxml is called with
> "remove_comments=False"? (elbepack/treeutils.py class etree(ebase))

yes; we want to keep the comments e.g. if the file
is read and rewritten, as in elbe chg_archive for example.

But this change, seems to be the source of the problem.
And we are currently working on a fix.

Regards,

  Manuel