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#51701 - [libseccomp] PKGBUILD does not have validpgpkeys
Attached to Project:
Arch Linux
Opened by Luke (Gaming4JC) - Saturday, 05 November 2016, 03:26 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 05 November 2016, 05:09 GMT
Opened by Luke (Gaming4JC) - Saturday, 05 November 2016, 03:26 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 05 November 2016, 05:09 GMT
|
DetailsDescription:
This PKGBUILD does not have validpgpkeys or sha256 checksums to check for file integrity. Additional info: Officially GPG signed SHA256 is provided upstream: https://github.com/seccomp/libseccomp/releases |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 05 November 2016, 05:09 GMT
Reason for closing: Not a bug
Saturday, 05 November 2016, 05:09 GMT
Reason for closing: Not a bug
Comment by Doug Newgard (Scimmia) -
Saturday, 05 November 2016, 05:09 GMT
They don't sign the releases, just the checksum. Pacman can't handle that.