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.28
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

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 .. 63 64 65 66 67 68 69 70 71 72 73 .. 101 Next › Last »

Lastebil commented on 2013-06-12 10:06 (UTC)

It builds perfectly fine without bluez (or bluez4) and if you don't care to have bluetooth, it's not needed. (In my case, I'm a good 8km from the machines with xen - fully remote, serial consoles, etc - so I definately don't need bluetooth. It's range isn't anywhere near 8km (: ) I also am very interested in the xen-api stuff, if we end up setting up a mailing list or whatever, ping me, please.

<deleted-account> commented on 2013-06-09 17:14 (UTC)

I was unable to build the package install -d -m0755 -p txt/man pod2text man/xl.pod.1 txt/man/xl.1.txt.tmp man/xl.pod.1 around line 854: Expected text after =item, not a bullet POD document had syntax errors at /usr/bin/core_perl/pod2text line 84. make[2]: *** [txt/man/xl.1.txt] Error 255

kantras commented on 2013-06-08 04:46 (UTC)

You can simply change 'bluez' to 'bluez4' in the PKGBUILD and it will work. Having said that, I wonder if its even really needed - I know qemu references it, but I don't see why it would need it. Something to test

hugleo commented on 2013-06-07 12:09 (UTC)

Or xen can compile selecting bluez version 5

hugleo commented on 2013-06-07 12:02 (UTC)

Now is needed to replace the bluez dependence with bluez4.

kantras commented on 2013-06-05 15:37 (UTC)

Actually I was already intending to look into what it would take to do that; I'm wanting to rebuild one of my main systems and this sounded like an interesting thing to add

tritron commented on 2013-06-05 15:30 (UTC)

We should start working on xen-api for arch linux.

kantras commented on 2013-06-05 15:29 (UTC)

Looking back over my notes, the other thing which was added was the ability to change the 'name'of the dom0 automatically on startup. Simply add a line 'XENDOM0_NAME=<new name>' into /etc/conf.d/xenstored and you'll be able to see the change when the xenstored service is next restarted ( "xl top" will show the new name, for example )

kantras commented on 2013-06-05 15:25 (UTC)

The pod2man "fix" was added to the texi2html.patch file; pod2man is returning an error code when parsing qemu.pod, due to using non-ascii characters when no '=encoding' parameter has been set. The file would still be created, which is why rebuilding the package a second time would work (since it would skip running pod2man as the file already existed) Two ways to fix, either a) add in "=encoding utf8' at the top of the qemu.pod file before you run it through pod2man or b) add the option '--errors=none' into the command line calling pod2man. I opted for the second as it was easier.

« First ‹ Previous 1 .. 63 64 65 66 67 68 69 70 71 72 73 .. 101 Next › Last »