Package Details: pkg_scripts 2016.4-1

Git Clone URL: https://aur.archlinux.org/pkg_scripts.git (read-only)
Package Base: pkg_scripts
Description: A collection of pacman and package-related utilities.
Upstream URL: http://xyne.archlinux.ca/projects/pkg_scripts
Keywords: pacman utilities
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 23
Popularity: 0.543428
First Submitted: 2013-11-10 21:47
Last Updated: 2016-04-20 01:17

Latest Comments

karol_007 commented on 2015-01-03 05:02

Oops: https://wiki.archlinux.org/index.php?title=Makepkg&diff=355057&oldid=354228

http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

karol_007 commented on 2015-01-03 04:56

Oops: https://wiki.archlinux.org/index.php?title=Makepkg&diff=355057&oldid=354228

karol_007 commented on 2015-01-02 23:06

The wiki tells you to https://wiki.archlinux.org/index.php/Makepkg#Signature_checking
Add the following line to the end of your GPG configuration file to include the pacman keyring in your
user's personal keyring.

~/.gnupg/gpg.conf

[...]
keyring /etc/pacman.d/gnupg/pubring.gpg


Works for me, no need to use 'export GNUPGHOME'.

eisen commented on 2015-01-02 13:28

I still had a similar issue :
==> Verifying source file signatures with gpg...
pkg_scripts-2014.12.31.tar.xz ... FAILED (unknown public key 1D1F0DC78F173680)

Performing the command below suggested by steinkrauz solved the issue.
export GNUPGHOME=/etc/pacman.d/gnupg

Xyne commented on 2014-12-30 03:36

I have added the new validpgpkeys array too all of my PKGBUILDs. Let me know if this solves the problem.

steinkrauz commented on 2014-12-29 20:16

export GNUPGHOME=/etc/pacman.d/gnupg
This command will force makepkg to use pacman's keyring.

berbae commented on 2014-12-29 11:34

I found that makepkg uses my local gpg db in ~/.gnupg and not the pacman key db.
So I trusted the key in my local database key file and now it works.

makepkg now requires to use a trusted signature.

How to force it to use the pacman key db?

berbae commented on 2014-12-29 10:29

After upgrading pacman:
pacman 4.1.2-7 -> 4.2.0-5
pyalpm 0.6.2-2 -> 0.7-1

I ran the 'pacman-db-upgrade' command

then trying to build your package, I get:

==> Verifying source file signatures with gpg...
pkg_scripts-2014.12.25.1.tar.xz ... FAILED (the public key EC3CBE7F607D11E663149E811D1F0DC78F173680 is not trusted)

Why your signature is not trusted any longer?
I am not sure what I need to do.