Moonwalker
2011-May-01 16:15 UTC
[Pkg-xen-devel] Bug#624788: Python version issue: "ImportError: No module named lxml"
Package: xen-utils-4.0 Version: 4.0.1-2 Right after another Wheezy distribution update I've faced the following issue with "xm". ====host:~# xm new /etc/xen/domains/test.cfg Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module> main.main(sys.argv) File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3620, in main _, rc = _run_cmd(cmd, cmd_name, args) File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in _run_cmd return True, cmd(args) File "<string>", line 1, in <lambda> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 1449, in xm_importcommand cmd = __import__(command, globals(), locals(), 'xen.xm') File "/usr/lib/xen-4.0/lib/python/xen/xm/new.py", line 26, in <module> from xen.xm.xenapi_create import * File "/usr/lib/xen-4.0/bin/../lib/python/xen/xm/xenapi_create.py", line 24, in <module> from lxml import etree ImportError: No module named lxml ==== The cause is that the current version (2.3-0.1+b2) of python-lxml package in Debian Wheezy available only for Python 2.6 and 2.7. You can safely change python2.5 dependency to python2.6. Also you need to modify /usr/lib/xen-4.0/bin/xm shebang to "#!/usr/bin/python2.6". Works flawlessly.
Debian Bug Tracking System
2011-May-01 17:45 UTC
[Pkg-xen-devel] Bug#624788: marked as done (Python version issue: "ImportError: No module named lxml")
Your message dated Sun, 1 May 2011 19:43:18 +0200 with message-id <20110501174318.GA23097 at wavehammer.waldi.eu.org> and subject line Re: [Pkg-xen-devel] Bug#624788: Python version issue: "ImportError: No module named lxml" has caused the Debian Bug report #624788, regarding Python version issue: "ImportError: No module named lxml" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 624788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624788 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Moonwalker <moonwalker at hotbox.ru> Subject: Python version issue: "ImportError: No module named lxml" Date: Sun, 01 May 2011 20:15:26 +0400 Size: 3455 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20110501/9356374a/attachment.eml> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: Re: [Pkg-xen-devel] Bug#624788: Python version issue: "ImportError: No module named lxml" Date: Sun, 1 May 2011 19:43:18 +0200 Size: 1836 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20110501/9356374a/attachment-0001.eml>