Your message dated Fri, 6 Feb 2015 17:26:51 +0100 with message-id <20150206162651.ga13...@bogon.m.sigxcpu.org> and subject line Re: Bug#772920: [Pkg-libvirt-maintainers] Bug#772920: virt-manager: ImportError: No module named virtinst has caused the Debian Bug report #772920, regarding virt-manager: ImportError: No module named virtinst 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 ow...@bugs.debian.org immediately.) -- 772920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: virt-manager Version: 1:1.0.1-4 Severity: grave Justification: renders package unusable tglase@tglase:~ $ virt-manager Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager", line 34, in <module> from virtinst import util as util ImportError: No module named virtinst As you can see, all dependencies are fulfilled: tglase@tglase:~ $ apt-get -f install -s NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 0 to remove and 36 not upgraded. -- System Information: Debian Release: 8.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gconf2 3.2.6-3 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-gtk-vnc-2.0 0.5.3-1.3 ii gir1.2-libvirt-glib-1.0 0.1.9-4 ii gir1.2-vte-2.90 1:0.36.3-1 ii librsvg2-common 2.40.5-1 ii python-dbus 1.2.0-2+b1 ii python-gi 3.14.0-1 ii python-gi-cairo 3.14.0-1 ii python-ipaddr 2.1.11-2 ii python-libvirt 1.2.9-1 ii python-urlgrabber 3.9.1-4 pn python2.7:any <none> pn python:any <none> ii virtinst 1:1.0.1-4 Versions of packages virt-manager recommends: pn gir1.2-spice-client-gtk-3.0 <none> pn gnome-icon-theme <none> ii libvirt-daemon-system 1.2.9-6 Versions of packages virt-manager suggests: pn gnome-keyring <none> ii kwalletcli [ssh-askpass] 2.12-3 pn python-gnomekeyring <none> pn python-guestfs <none> pn virt-viewer <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi, On Sat, Dec 13, 2014 at 01:31:38PM +0100, Guido Günther wrote: > On Fri, Dec 12, 2014 at 02:33:23PM +0000, Thorsten Glaser wrote: > > Guido G�nther dixit: > > > > >The module is shipped by the virtinst package. Can you check > > >/usr/share/virt-manager for that: > > > > > > ls -l /usr/share/virt-manager/virtinst/ > > > > ls: cannot access /usr/share/virt-manager/virtinst/: No such file or > > directory > > > > But: > > > > ii virtinst 1:1.0.1-4 all Programs to > > create and clone virtual machines > > > > Huh? > > > > After “sudo apt-get install --reinstall virtinst”, virt-manager works. > > > > Maybe /usr/share/virt-manager/virtinst was a symlink once, > > or something else did a symlink/directory change, which is > > not supported by dpkg? This is the only way I can explain > > this… > > Not that I could remember. Since it's not reproducible I'm tagging as > such. If nobody else chimes in I'm inclinde to close this. The changes > where we merged virtinst into virt-manager happened back in 2013 and > I've not seen a similar report so far. Closing since this seems to be an issue on the reporters machine only. Thorsten if you have any idea what could have caused this please reopen and provide some more information. Cheers, -- Guido
--- End Message ---
