Package Details: pkg_scripts 2022-1

Git Clone URL: https://aur.archlinux.org/pkg_scripts.git (read-only, click to copy)
Package Base: pkg_scripts
Description: A collection of pacman and package-related utilities.
Upstream URL: https://xyne.dev/projects/pkg_scripts
Keywords: pacman utilities
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 27
Popularity: 0.46
First Submitted: 2013-11-10 21:47 (UTC)
Last Updated: 2022-01-27 23:20 (UTC)

Latest Comments

thiagowfx commented on 2021-06-28 22:08 (UTC)

FYI: pkg-abs_path can probably be deleted, as ABS doesn't exist in arch anymore.

Also FYI: pkg-list_link_deps.py is the only utility that contains the .py extension. All others do not contain the .py extension.

jpkotta commented on 2017-08-10 19:42 (UTC)

Source archive is 404

karol_007 commented on 2015-01-03 05:02 (UTC)

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-02 23:06 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

berbae commented on 2014-12-29 11:34 (UTC)

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 (UTC)

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.