Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40240 - Pacman->makepkg signature check fail

Attached to Project: Community Packages
Opened by Christoph Hoopmann (choopm) - Tuesday, 06 May 2014, 13:03 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 06 May 2014, 13:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If you use makepkg to build a PKGBUILD, it will complain over a non existent public key (EAE999BD).
Confirmed by 4 other people and present in latest ISO.
Adding --homedir as option to the gpg call solves the problem.

Diff (makepkg.sh.in):
1282c1282
< if ! gpg --quiet --batch --status-file "$statusfile" --homedir /etc/pacman.d/gnupg --verify "$file" "$sourcefile" 2> /dev/null; then
---
> if ! gpg --quiet --batch --status-file "$statusfile" --verify "$file" "$sourcefile" 2> /dev/null; then

Additional info:
pacman 4.1.2-5
gnupg 2.0.22-2

Steps to reproduce:
Boot from latest ISO.
pacman -Sy abs && abs
cp -r /var/abs/core/pacman . && cd pacman
makepkg --asroot -o
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 06 May 2014, 13:14 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Tuesday, 06 May 2014, 13:14 GMT
Or you can just import the key -- it belongs to Allan.

NAK on your proposed change -- the package builder's gpg keyring should be used, as /etc/pacman.d/gnupg is declared sacred and only used for validating binary packages for pacman. If you want to use /etc/pacman.d/gnupg, you can opt into this yourself by setting GNUPGHOME=/etc/pacman.d/gnupg in ~/.makepkg.conf.

Loading...