Package Details: xen-docs 4.19.1pre-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Xen hypervisor documentation and man pages
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 185
Popularity: 0.38
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Dependencies (35)

Required by (1)

Sources (7)

Pinned Comments

Refutationalist commented on 2024-12-06 01:37 (UTC)

Please Note: Per best-practices by upstream this package follows the git stable branch. Minor releases do not require a version bump and the PKGBUILD will provide the appropriate version number.

stubdom is still broken.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 101 Next › Last »

cman commented on 2020-07-29 21:51 (UTC)

Hi @Refutationalist, thanks for the great package. I have compiled this package with 4.14.0, and can confirm that most, but not all, of the gcc patches are no longer needed. I've also rebased the grub script on what is in the latest Archlinux package, plus added support to the script for cpu microcode updates and xsm, if present.

I, too, am not too conversant with aur, so I don't know whether a standard way exists to do that (other than with git, of course), but I'm happy to contribute patchsets if you would like if you tell me how you want them.

Refutationalist commented on 2020-07-29 19:24 (UTC)

@linuxninja - Yeah, my package is still requiring qemu-xen from my personal repo, something that I'll be fixing in the next update.

I'm also looking at 4.14.0, which is not compiling but looks to have some of the same problems as 4.13.1 did. I'll try to have something ASAP, depending on complexity and my workload.

linuxninja commented on 2020-07-29 06:44 (UTC)

I was able to build with the changes to the source that I noted, however, I am unable to start a HVM VM with the new build options in this PKGBUILD. I had to revert to the old PKGBUILD and go back to Xen 4.13.0.

linuxninja commented on 2020-07-29 03:08 (UTC) (edited on 2020-07-29 04:08 (UTC) by linuxninja)

source = https://src.fedoraproject.org/rpms/xen/raw/master/f/xen.gcc10.fixes.patch https://src.fedoraproject.org/rpms/xen/raw/master/f/xen.ocaml.4.10.patch

Needs to be changed to

source = https://src.fedoraproject.org/rpms/xen/raw/f32/f/xen.gcc10.fixes.patch https://src.fedoraproject.org/rpms/xen/raw/f32/f/xen.ocaml.4.10.patch

in the PKGBUILD. The f32 tag reflects the files the PKGBUILD has been using up to this point. The Master branch has moved on to Xen 4.14.0 and has removed the ocaml patch and the gcc10 patch is no longer the same file.

alaricljs commented on 2020-07-21 21:14 (UTC)

Ok, so it turns out I'm actually blind. Removing --with-system-qemu from the build function does the deed. Makes me think there should be an optdepends or depends on qemu if you're going that route so that it's slightly more obvious.

alaricljs commented on 2020-07-21 16:43 (UTC)

So how do I get a functional HVM with this release? (4.13.1-4) There's no /usr/lib/xen/bin/qemu-dm but I don't see anything obvious in the PKGBUILD as to why.

Refutationalist commented on 2020-07-20 18:55 (UTC)

WANTED: Maintainer or co-maintainer.

I've written a lot of PKGBUILDs for my own purposes, but I'm not that conversant with AUR itself other than using it. I'm also going to be hip deep in work over the next few months and might miss stuff.

Refutationalist commented on 2020-07-20 18:49 (UTC)

Okay, I've added the disable flag for qemut, and at least allowed the package to disable stubdom if people don't want it. I've also split out the docs package, as before. This package is currently at parity with what's in my git.

Next, I'd like to take a closer look at qemu before I willy-nilly push qemu-xen to AUR.

Refutationalist commented on 2020-07-10 05:16 (UTC) (edited on 2020-07-10 05:17 (UTC) by Refutationalist)

@JohnTh:

The minimal-components builds were never useful to me without modification, which is another reason why my personal repo is the way it is. But my build wasn't going to be on AUR, so I suppose I should revisit that. I invariably need stubdom, so I pulled out the optional check. Other stuff I can probably get rid of, qemut in particular.

I'm not familiar with what the community decisions were. I can review the comments, but that wasn't my initial aim and I took over the package as I seemed to have inadvertently caused a problem. Would it make more sense if you or someone else took over the package? I'm open to that.

Otherwise, I'm going to look into fixing what I have outstanding and updating the package sometime next week.

eduncan911 commented on 2020-07-01 10:57 (UTC)

@JohnTh qemu requires the Xen headers to compile Xen support, so unless you can get this into an arch repository, it will be unlikely our qemu maintainers will want to build the Xen tools themselves.

I would prefer such headers/compilation to be a separate package, so to keep this one lean. Much like the kernel headers are available in an addition package.