| Git Clone URL: | https://aur.archlinux.org/qemu-git.git (read-only, click to copy) |
|---|---|
| Package Base: | qemu-git |
| Description: | QEMU iSCSI block module. Git version. |
| Upstream URL: | https://wiki.qemu.org/ |
| Keywords: | git kvm qemu |
| Licenses: | GPL-2.0-or-later, LGPL-2.1-or-later |
| Conflicts: | qemu-block-iscsi |
| Provides: | qemu-block-iscsi |
| Submitter: | None |
| Maintainer: | FredBezies |
| Last Packager: | FredBezies |
| Votes: | 30 |
| Popularity: | 0.004425 |
| First Submitted: | 2009-09-19 20:02 (UTC) |
| Last Updated: | 2026-09-05 10:50 (UTC) |
depends needs to be changed (libjpeg):Can you please change
libjpeg to libjpeg-turbo (any maybe existing make dependency libjpeg needs also to be changed to libjpeg-turbo),libjpeg to libjpeg.so AND add make dependency libjpeg-turbo?Reason: Arch Linux does not have libjpeg anymore, and libjpeg-turbo stopped to declare libjpeg in it's provides array.
Regards and thanks for maintaining!
As nobody adopt the package, I own it again. I won't promise any split package effort for the moment.
Don't have time to manage it anymore. It needs to be synchronized with the official qemu splitted PKGBUILD. I failed to migrate it. If somebody adopts it, please do this synchronization at first.
I had a lot of good time with this PKGBUILD, but time is come to disown it.
Does this version actually come with proper clipboard sharing functionality? In that case it might be very much worth using it.
Because I cannot get it to work with the default one in the Arch repos.
According to https://gitlab.com/qemu-project/qemu/-/issues/1455 there's a compile option --enable-gtk-clipbard which can be enabled, it should at least fix the problem when using the gtk display option, like I do.
(I am using the gtk display because from all my experimenting with QEMU/KVM it's seems the best available one of all.)
However even with other displays I currently don't get it working, so I suspect much more is going on and maybe I am still doing something wrong, but I really tried lots of things already, so I am beginning to believe there might be also another bug going on somewhere.
@AkechiShiro: just rebuild it, it will take into account the new libbpf version.
This is probably due to this change of libbpf, it provides libbpf.so=1-64 and not 0-64 anymore.
https://archlinux.org/packages/core/x86_64/libbpf/
Pinned Comments