Arch Linux User Repository

This package makes use of GPG keys for integrity verification. Here are the PGP keys you need to import (if you trust them):

$ gpg --recv-keys A917B1ECDA84AEC2B568FED6F50ABC807BD5DCD0 528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 1729F83938DA44E27BA0F4D3DBDB397470D12172

Receiving GPG keys might fail with the following error message: $ gpg: keyserver receive failed: Connection refused. If this happens, just check your DNS or use other ones.

maybe you should add bin links or add /opt/php71/usr/bin to PATH via an /etc/profile.d/ entry like this:

/etc/profile.d/php71.sh

!/bin/sh

export PATH=$PATH:/opt/php71/usr/bin

this will avoid fail updates like nextcloud which use the php binary for updates for users that only have installed php71

Hi, A build fix since the latest icu update : https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/php&id=16c36238f69fd9729403a23c650016b424a37285

also a systemd service would be nice thx

could you rewrite it so the files are under /usr like in php70 and php56 package? would be nice

This package puts PHP 7.1 in /opt/php71, so it can be installed alongside the php package in the mirrors. I have also uploaded uwsgi-plugin-php71, php71-apcu, and php71-apcu-bc, which is enough to get ZoneMinder (and the API) working without issues.

Knowing the source and having checked the integrity manually, I went with

makepkg --skipinteg

Thanks for maintaining this package

If --skipinteg isn't working, try --skippgpcheck. Not sure if the first includes the other.

-Michael.

Hi,

That was the same problem yramagicman was having. See my comment there, but to summarize:

Either run the command "gpg --receive-keys <...>" where <...> is the strings between validpgpkeys=( and the following ) without the apostrophes, or

in ~/.gnupg/gpg.conf add the following line:

keyserver-options auto-key-retrieve

Hope this helps,

-Michael.

==> Verifying source file signatures with gpg...

php-7.1.15.tar.xz ... FAILED (unknown public key F9BA0ADA31CBD89E)

==> ERROR: One or more PGP signatures could not be verified!

Sorry about that -- not sure how I missed it. It's fixed now.