Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38929 - [virt-manager] 1.0.0-1 fails to start

Attached to Project: Community Packages
Opened by (webmeister) - Saturday, 15 February 2014, 22:26 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 15 February 2014, 23:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Trying to run virt-manager fails:
/usr/bin/virt-manager: /usr/share/virt-manager/virt-manager: /usr/bin/python22: bad interpreter: No such file or directory
/usr/bin/virt-manager: line 3: /usr/share/virt-manager/virt-manager: Success

Apparently, replacing the Python interpreter in the PKGBUILD is not necessary anymore.
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 15 February 2014, 23:08 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#38928 
Comment by Karol Błażewicz (karol) - Saturday, 15 February 2014, 22:28 GMT
Maybe
sed -i 's#bin/python#bin/python2#' virt-*
from prepare() is at fault?
Comment by (webmeister) - Saturday, 15 February 2014, 22:32 GMT
Yes, that seems to be the problem. All /usr/share/virt-manager/virt-* files try to use /usr/bin/python22. So without the prepare step they should correctly reference /usr/bin/python2.
Comment by crashbit (crashbit) - Saturday, 15 February 2014, 22:40 GMT
Duplicate bug of: https://bugs.archlinux.org/task/38928?project=5

Loading...