Arch Linux

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#56074 - [archlinux-keyring] signature has marginal trust

Attached to Project: Arch Linux
Opened by Daniel (bigstumpi) - Sunday, 22 October 2017, 05:43 GMT
Last edited by Jan de Groot (JGC) - Monday, 23 October 2017, 21:34 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Florian Pritz (bluewind)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
when upgrading via pacman -Syu I get the following error on two community packages (blosc,zstd):
Error: <package>: signature from "Andrzej Giniewicz (giniu) <gginiu@gmail.com>" is marginal trust

I already executed the following commands:
pacman-key --refresh-keys
pacman -S archlinux-keyring
but no change.

(I consider this as a bug as this user is listed on the official 'trusted users' list https://www.archlinux.org/people/trusted-users/#aginiewicz)

Additional info:
zstd-1.3.1-1-x86_64.pkg.tar.xz
blosc-1.12.1-1-x86_64.pkg.tar.xz

Steps to reproduce:
pacman -Syu with this community packages installed
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 23 October 2017, 21:34 GMT
Reason for closing:  Fixed
Comment by Bartłomiej Piotrowski (Barthalion) - Sunday, 22 October 2017, 11:15 GMT
Signed by DDB867B92AA789C165EEFA799B729B06A680C281. Should we update archlinux-keyring again or is that enough?
Comment by Doug Newgard (Scimmia) - Sunday, 22 October 2017, 17:04 GMT
Correct me if I'm wrong, but it appears that wonder's key is still active in the latest archlinux-keyring package. If that's the case, there are 3 master key sigs and this would only become an issue after refreshing from a keyserver. Just pushing your sig fixed that case.
Comment by Daniel (bigstumpi) - Monday, 23 October 2017, 20:54 GMT
Works for me now after refreshing keys today! Thanks.

Loading...