Search Criteria
Package Details: xen-qemu 9.0.0-1
Package Actions
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-06-05 02:55 (UTC) |
Dependencies (6)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- numactl (numactl-gitAUR)
- xenAUR
- meson (meson-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- python-packaging (make)
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 ?
<deleted-account> 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)
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 withqemu-common
or remove the files provided byqemu-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
1 2 Next › Last »