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!
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!
FS#15889 - [xen] x86_64 package does not include python bits
Attached to Project:
Community Packages
Opened by Sam (waxymouthfeel) - Monday, 10 August 2009, 17:59 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 12 August 2009, 21:18 GMT
Opened by Sam (waxymouthfeel) - Monday, 10 August 2009, 17:59 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 12 August 2009, 21:18 GMT
|
DetailsDescription:
Xen 3.4.1-1 from the community repository does not include the python modules required for xend to start. As a result, Xen will not function from this module. The i686 version includes these files, but as it has compiled parts, using these won't work as a workaround. Additional info: * package version(s) 3.4.1-1 * config and/or log files etc. None outside the standard files included in the package Steps to reproduce: root# pacman -S xen (configure, reboot, hooray) root# /etc/rc.d/xend start Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server .Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server |
This task depends upon
The line:
sed -i 's#x86_32#x86_64#' tools/firmware/Rules.mk || return 1
Appears to be the culprit, as some of those tools want to be 32bit, from the looks of it.
Meanwhile, the PKGBUILD also calls 'msg "FAILED"' if the make errors out, I changed that to 'return 1' as I thought msg was a PKGBUILD internal and might not pass to shell. Probably pointless, but I should document everything I'm doing.
I don't have running VMs yet as I'm locking up on network. That might be the kernel I'm running (2.6.29 with the SUSE patches).