Pkg xen devel - Sep 2011 - Bug#570066: xen-utils-4.1: should depend on python-lxml

retitle 570066 xen-utils-4.1: should depend on python-lxml
thanks

Hi,

''xm new'' fails on a freshly installed sid system
(xen-utils-4.1 4.1.1-2)
with the following import error:

ImportError: No module named lxml

Simply installing python-lxml solves the problem, so I think xen-utils
should depend on it.

Also, can 599520 be closed now that python-lxml is being used by xenapi?

Thanks,
  ema

Processing commands for control at bugs.debian.org:
> retitle 570066 xen-utils-4.1: should depend on python-lxml
Bug #570066 [xen-utils-common] xm new: undeclared dependency on absent Python
library "xmlproc".
Bug #593741 [xen-utils-common] xen-utils-common: python-xml is not marked as a
dependency and xm errors without it
Changed Bug title to ''xen-utils-4.1: should depend on
python-lxml'' from ''xm new: undeclared dependency on absent
Python library "xmlproc".''
Changed Bug title to ''xen-utils-4.1: should depend on
python-lxml'' from ''xen-utils-common: python-xml is not marked
as a dependency and xm errors without it''
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
570066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570066
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems

On Sun, Sep 25, 2011 at 03:22:04PM +0200, Emanuele Rocca
wrote:
> ''xm new'' fails on a freshly installed sid system
(xen-utils-4.1 4.1.1-2)
> with the following import error:
xm create works without.

Bastian

-- 
If I can have honesty, it''s easier to overlook mistakes.
		-- Kirk, "Space Seed", stardate 3141.9

Hi Bastian,

On 25/09 03:42, Bastian Blank wrote:
> On Sun, Sep 25, 2011 at 03:22:04PM +0200, Emanuele Rocca wrote:
> > ''xm new'' fails on a freshly installed sid system
(xen-utils-4.1 4.1.1-2)
> > with the following import error:
> 
> xm create works without.
But their behaviour is different, isn''t it? Correct me if I am wrong,
but my understanding is that machines added with xm create are removed
from Xen management after you shut them down.

For example, they are not manageable with virt-manager, and they do not
show up in xm list.