Indeed, as you suggest, moving away the old files was sufficient. I can
now successfully run virt-manager.
I don't recall ever doing a manual install of virtinst on this machine ,
so I'm unclear where the old version came from, however, that was the
issue.
Thanks very much! Hopefully this also
Ah ha! I think I have nailed the issue, at least for me: it's a combination of
a python module import path error, and left over debris of an earlier virtinst:
take a look:
First, notice that my python doesn't even have a module path that
includes /usr/share/pyshared:
pjs11@patslinux01 ~ $ pyth
Answered my own question again -- "version.py" is a file being shipped in the
virtinst package, under /usr/share/pyshared/virtinst, and it contains the
single variable "__version__'.
So, for some reason, the import in virtinst/__init__.py expects to find
virtinst/version.py, but can't.
Apologie
This appears to be the root cause:
pjs11@patslinux01 ~ $ python
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import version
Traceback (most recent call last):
File "", line 1, in
ImportError: N
Sorry for the stupid question, answered it myself: yes, it is. The
package containing all the useful stuff in Lucid is just 'virtinst'.
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680627
Title:
Just a stupid question, but is the python-virtinst package supposed to
be empty excepting documentation?
pjs11@patslinux01 ~ $ dpkg-query --listfiles python-virtinst
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python-virtinst
/usr/share/doc/python-virtinst/copyright
/usr/share/doc/python-virt
FWIW, the error is being thrown here:
/usr/share/virt-manager/virt-manager.py line 306:
# Make sure we have a sufficiently new virtinst version, since we are
# very closely tied to the lib
msg = ("virt-manager requires the python-virtinst library version " +
virtinst_str +
I'm still experiencing this issue. Ubuntu hardy, patched up to date as
of this writing.
pj...@patslinux01 ~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 8.04.3 LTS
Release:8.04
Codename: hardy
pj...@patslinux01 ~ $ uname -a
Linux pats
