xm new depends on python-lxml

[Stefan Bader]

Release: Precise
Package version: 4.1.0~rc6-1ubuntu2

Running xm new results in the following trace which is avoided by installing python-lxml:
#> xm new
Unexpected error: <type 'exceptions.ImportError'>

Please report to <email address hidden>
Traceback (most recent call last):
  File "/usr/lib/xen-4.1/bin/xm", line 8, in <module>
    main.main(sys.argv)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xm/main.py", line 3983, in main
    _, rc = _run_cmd(cmd, cmd_name, args)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xm/main.py", line 4007, in _run_cmd
    return True, cmd(args)
  File "<string>", line 1, in <lambda>
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xm/main.py", line 1518, in xm_importcommand
    cmd = __import__(command, globals(), locals(), 'xen.xm')
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xm/new.py", line 26, in <module>
    from xen.xm.xenapi_create import *
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xm/xenapi_create.py", line 24, in <module>
    from lxml import etree
ImportError: No module named lxml

[Todd Deshane (todd-deshane)]

xm/xend (and managed domains) are unsupported upstream:

http://lists.xen.org/archives/html/xen-devel/2012-01/msg02143.html

(xcp-)xapi, which has Debian and Ubuntu packages available is the recommended alternative for managed domains.

[Stefan Bader (smb)]

I am very much aware that upstream tries to deprecate xm. But right now it is still used by libvirt and while it is possible to use that, I found that if it is only the missing dependency to a package that makes the difference between a totally broken output to a subcommand and it to (as far as I can see) work, it should be worth having the depends line fixed.