Package Details: pacserve 2021-1

Git Clone URL: (read-only, click to copy)
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: 102
Popularity: 0.100536
First Submitted: 2011-04-17 00:30
Last Updated: 2021-02-11 12:51

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

Xyne commented on 2015-01-07 00:44

The signature is already in the validpgpkeys array. You should have checked before flagging the package. Check the discussion in the comments on the pkg_scripts page for instructions to eliminate the error.

asdil12 commented on 2015-01-03 19:41

==> Validating source files with sha512sums...
pacserve-2013.9.tar.xz ... Passed
pacserve-2013.9.tar.xz.sig ... Passed
==> Verifying source file signatures with gpg...
pacserve-2013.9.tar.xz ... FAILED (unknown public key 5CED81B7C2E5C0D2)
==> ERROR: One or more PGP signatures could not be verified!

I think you need to define the GPG key fingerprint in the validpgpkeys array:

Xyne commented on 2014-11-01 16:37

It seems that you have deleted the "ACCEPT" target on that machine. I recommend that you restore it.

untitaker commented on 2014-10-30 21:24

Since a while i had a mysterious failure of "pacserve-ports open":

running "iptables -A INPUT -p tcp --dport 15678 -j ACCEPT"
running "iptables -A INPUT -p udp -m pkttype --pkt-type multicast --dport 15679 -j ACCEPT"
iptables: No chain/target/match by that name.

Funnily this happens on only one system.

Xyne commented on 2014-04-05 13:17

> Just _rebuild_ the necessary packages. You need to do this manually for all python packages from the AUR.

This. It is the user's responsibility to rebuild AUR packages against new packages in the official repos.

You could also enable the repo on my site to install all of my packages directly with pacman without worrying about manual rebuilds.

lahwaacz commented on 2014-04-04 21:25

Just _rebuild_ the necessary packages. You need to do this manually for all python packages from the AUR.

Anonymous comment on 2014-04-04 21:04

It probably isn't a good fix but copying /usr/lib/python3.3/site-packages/ThreadedServers to /usr/lib/python3.4/site-packages/ThreadedServers
fixes the problem for the time being

schmoken commented on 2014-04-04 03:14

Python 3.4 update breaks pacserve.

● pacserve.service - Pacserve
Loaded: loaded (/usr/lib/systemd/system/pacserve.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2014-04-03 20:47:28 MDT; 4s ago
Process: 7526 ExecStart=/usr/bin/pacserve $PACSERVE_ARGS (code=exited, status=1/FAILURE)
Main PID: 7526 (code=exited, status=1/FAILURE)

Xyne commented on 2013-11-21 00:39

Hi altrus,

I see how that may be useful, but at the same time anyone who has configured their firewall with rules specific enough to drop the target packets before they reach the end of the chain is likely someone who will want to manage their own rules entirely on their own. More importantly, inserting the rule would usurp other rules. If the user has decided to filter those packets for some reason, I think it's best to let the user determine the best configuration.

Besides, I don't feel like getting stabbed by fukawi2 [1] :P


altrus commented on 2013-11-17 19:19


The default behaviour of pacserve-ports is to append the allow rules to the end of the INPUT chain.

Depending on how iptables is configured, this may result in otherwise legitimate packets being dropped by earlier rules. To avoid this from happening, consider replacing the 'append' rule with an 'insert' rule.

This requires changing the invocation of the iptables binary in the /usr/bin/pacserve-ports file. This requires first substituting the -A (append) flag to -I (insert) on line 12, so it reads:

"$iptables_bin" -I $@ || exit 1

Next, we have to specify what rule number we want to insert at in the /etc/pacserve/pacserve-ports.conf file. This requires us to specify the rule number we want to insert the rule at. I've (somewhat arbitrarily) decided to insert the rule at line 3. This means the new conf file reads:

'INPUT 3 -p tcp --dport 15678 -j ACCEPT'
'INPUT 3 -p udp -m pkttype --pkt-type multicast --dport 15679 -j ACCEPT'

You may wish to consider making this the default behaviour, as it ensures the pacserve rules will accept the packages, even if later rules try to drop the packets.