Package Details: xen-qemu 8.2.1-1

Git Clone URL: https://aur.archlinux.org/xen-qemu.git (read-only, click to copy)
Package Base: xen-qemu
Description: A xen-specific QEMU, built to qemu-builtin standards
Upstream URL: https://www.qemu.org
Licenses: GPL2, LGPL2.1
Conflicts: xen-qemu-builtin
Provides: qemu-xen, xen-qemu, xen-qemu-builtin
Replaces: xen-qemu-builtin
Submitter: Refutationalist
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 0
Popularity: 0.000000
First Submitted: 2022-11-15 02:23 (UTC)
Last Updated: 2024-02-11 01:58 (UTC)

Latest Comments

1 2 Next › Last »

Refutationalist commented on 2023-08-24 23:45 (UTC)

alright, back near my stuff, version bumped to 8.1.0, did a test compile.

ArthurBorsboom commented on 2023-08-17 13:11 (UTC)

@Refutationalist any chance of updating the package to 8.0.3 (or newer) to fix the building issue ?

samcday commented on 2023-07-27 19:04 (UTC)

I ran into the same issue ArthurBorsboom noted a few days ago. I confirm that the linked patch was released in qemu 8.0.3 and I successfully built this package with that version.

ArthurBorsboom commented on 2023-07-20 15:00 (UTC) (edited on 2023-07-20 15:00 (UTC) by ArthurBorsboom)

[1778/2765] Generating pc-bios/keymaps/ar with a custom command
FAILED: pc-bios/keymaps/ar 
/home/arthur/.cache/yay/xen-qemu/src/build/qemu-keymap -f pc-bios/keymaps/ar -l ar
xkbcommon: ERROR: Couldn't find file "symbols/ar" in include paths
xkbcommon: ERROR: 1 include paths searched:
xkbcommon: ERROR:       /usr/share/X11/xkb
xkbcommon: ERROR: 3 include paths could not be added:
xkbcommon: ERROR:       /home/arthur/.config/xkb
xkbcommon: ERROR:       /home/arthur/.xkb
xkbcommon: ERROR:       /etc/xkb
xkbcommon: ERROR: Abandoning symbols file "(unnamed)"
xkbcommon: ERROR: Failed to compile xkb_symbols
xkbcommon: ERROR: Failed to compile keymap

The problem is known and a patch has been created upstream.

https://gitlab.com/qemu-project/qemu/-/issues/1709

Maybe this patch can be (temporary?) applied until available in a newer version?

ArthurBorsboom commented on 2022-11-18 10:40 (UTC)

I have created a new VM and installed Arch with the help of the Arch installer, installation type: minimal.

After installing git and yay I ran the following. yay -S xen xen-qemu libvirt-xen

This resulted in the three packages being installed without conflicts.

So, I guess the question remains what triggers the conflict on the 'existing' system? Any pointers that I can try?

Refutationalist commented on 2022-11-18 04:22 (UTC)

@ahmubashshir: if you build in a clean chroot it doesn't build those files, thus no collision. This is why I suggested it. I'm happy to accept a PR for a more permanent fix, but until I receive one or I get to one myself, build in a clean chroot.

ahmubashshir commented on 2022-11-18 04:15 (UTC) (edited on 2022-11-18 04:40 (UTC) by ahmubashshir)

@Refutationalist, building in clean chroot won't solve anything... cause the files in your package are conflicting with qemu-common, it's better to either mark it as conflicting package with qemu-common or remove the files provided by qemu-common and depend on it.

FYI, arch maintainers now split qemu in several packages to ease installation, you should follow upstream and remove common files.

P.S. you can check out arch pkgbuild for qemu with asp checkout qemu

Refutationalist commented on 2022-11-17 00:23 (UTC) (edited on 2022-11-17 00:24 (UTC) by Refutationalist)

@ArthurBorsboom: Can you try building your package in a clean chroot or VM with nothing unnecessary to the build process installed? My package doesn't create locale files, which is why I recommend building these packages in such a way.

chroot instructions: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot