Package Details: pacserve 2018-11

Git Clone URL: (read-only)
Package Base: pacserve
Description: Easily share Pacman packages between computers. A replacement for PkgD.
Upstream URL:
Keywords: arch_linux pacman server
Licenses: GPL
Conflicts: pacredir
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 99
Popularity: 0.842654
First Submitted: 2011-04-17 00:30
Last Updated: 2018-10-03 01:20

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Xyne commented on 2019-05-06 21:34

At the moment only avahi and basic multicast are supported. I'm open to the idea of addding systemd-resolved's mDNS but I won't have time to implement it myself any time soon.

ReekyMarko commented on 2019-05-06 14:41

Hi, didn't find an issue tracker upstream, so I'm going to ask here. Is it possible to use systemd-resolved's mDNS instead of avahi?

Xyne commented on 2018-10-03 06:27

Sorry, a lot happened in the last few weeks and I didn't notice that my release scripts had broken. Everything should be working again now.

ghthor commented on 2018-09-28 03:27

I hope this package hasn't been fixed because Xyne is just on vacation.

kantras commented on 2018-09-27 19:43

I believe that the key issue appears to be that the source archive is currently unavailable - the "Fixed" PKGBUILD, mentioned below, simply grabs the prebuilt package, extracts the files, and then just rebuilds it again, which feels counter-intuitive to me.

Speranskiy commented on 2018-09-11 04:48


jnanar commented on 2018-09-10 20:44

Same here. However, the source seems to be here:
This is the unofficial repository of the xyne-x86_64 mentioned on the wiki. (

steadybright commented on 2018-09-09 15:47

Cannot find build tar.xz file (same as knedlyk reported below)":

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading Aborting...

knedlyk commented on 2018-09-08 20:07

pacserve-2018.tar.xz not found!

olive commented on 2018-08-22 18:17

@Mouath I have tried to rebuild both packages but the error remain. You will see that the unit status is "restarting" (systemctl list-units) and the crash log from python can be see in the journal (journalctl). Have you tried with an up to date system (the error is recent, it used to work).

Update: I had ipv6 disabled (because I don't use it). The error seems to disappear if I enable it. Don't know why it must be enabled.