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!
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!
FS#55742 - [lttng-ust] "validpgpkeys" missing in PKGBUILD
Attached to Project:
Community Packages
Opened by Erich Eckner (deepthought) - Monday, 25 September 2017, 09:36 GMT
Last edited by Thore Bödecker (foxxx0) - Monday, 25 September 2017, 14:11 GMT
Opened by Erich Eckner (deepthought) - Monday, 25 September 2017, 09:36 GMT
Last edited by Thore Bödecker (foxxx0) - Monday, 25 September 2017, 14:11 GMT
|
DetailsDescription:
The package can't be built, because the pgp-key is not trusted. Please add the following line to the PKGBUILD: validpgpkeys=(2A0B4ED915F2D3FA45F5B16217280A9781186ACF) Additional info: * package version(s) lttng-ust-2.10.0-8 * config and/or log files etc. ==> Verifying source file signatures with gpg... lttng-ust-2.10.0.tar.bz2 ... FAILED (the public key 2A0B4ED915F2D3FA45F5B16217280A9781186ACF is not trusted) ==> ERROR: One or more PGP signatures could not be verified! Steps to reproduce: (in a clean environment) > makepkg --verifysource |
This task depends upon
Fixed as of lttng-ust-2.10.0-10.
Cheers,
Thore