each xm command generates warnings caused by new versions of sha and set classes in python 2.6. Reproducible: Always Steps to Reproduce: 1. install python 2.6 or update to this version (use python-updater) 2. install xen-tools 3.3.1/3.4.0 3. use xm utility
Created attachment 202264 [details, diff] xen-tools-3.3.1.ebuild.patch add patch to ebuild
Created attachment 202266 [details, diff] /tmp/xen-tools/xen-tools-3.4.0-r1.ebuild.patch add patch to ebuild
Why aren't you using 3.4.1 ?
Created attachment 202267 [details, diff] xen-tools-3.3.1-python.patch
Created attachment 202268 [details, diff] xen-tools-3.4.0-python.patch
see also http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00477.html patch seems to be already included in xen-tools-3.4.1
(In reply to comment #6) > patch seems to be already included in xen-tools-3.4.1 So just use 3.4.1.
(In reply to comment #7) > So just use 3.4.1. this is not an option IMHO. xen-3.4 did not properly work with xen-sources-2.6.21. there are several systems which have problems with newer xen-kernels. as far as xen-tools-3.3/3.4.0 are in portage they should also support newer python versions or the dependencies needs to be updated.
Hello! I see these deprecation messages when emerging app-emulation/xen-tools-4.0.0: * * Deprecation Warning: Not passing of paths to python_mod_optimize() is deprecated and will be * disallowed on 2010-09-01. Call python_mod_optimize() with paths to Python modules. * The ebuild needs to be fixed. Please report a bug, if it has not been already reported. *
Xen 4.1 in tree. Please test with it and reopen if it doesnt work