Search Criteria
Package Details: xml-security-c 3.0.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/xml-security-c.git (read-only, click to copy) |
---|---|
Package Base: | xml-security-c |
Description: | Shibboleth Project's C++ implementation of W3C security standards for XML |
Upstream URL: | https://shibboleth.atlassian.net/wiki/spaces/SP3/pages/2067398783/XML-Security-C |
Licenses: | Apache |
Submitter: | None |
Maintainer: | grawity |
Last Packager: | grawity |
Votes: | 17 |
Popularity: | 0.113359 |
First Submitted: | 2010-08-25 09:12 (UTC) |
Last Updated: | 2024-10-17 06:18 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 Next › Last »
zeroconf commented on 2021-07-08 05:21 (UTC)
Can you reveal keyservers, where you have been uploaded your key?
kevku commented on 2021-07-08 04:39 (UTC)
the sks-keyserver has been dead for a while now.
zeroconf commented on 2021-07-08 02:44 (UTC) (edited on 2021-07-08 02:46 (UTC) by zeroconf)
Trying to install digidoc software, where current package is one of the dependencies.
I'm unable to build package: [code]==> Verifying source file signatures with gpg... xml-security-c-2.0.2.tar.bz2 ... FAILED (unknown public key 378B845402277962) ==> ERROR: One or more PGP signatures could not be verified!
In file /etc/pacman.d/gnupg/gpg.conf added:
keyserver hkp://pool.sks-keyservers.net
Also ~/.gnupg/gpg.conf added:
keyring /etc/pacman.d/gnupg/pubring.gpg
keyserver hkp://pool.sks-keyservers.net
Updated keys:
sudo pacman-key --refresh-keys -u --keyserver hkps.pool.sks-keyservers.net
Tried to import GPG-key gpg --keyserver pool.sks-keyservers.net --recv-keys DCAA15007BED9DE690CD9523378B845402277962
tried also server hkps.pool.sks-keyservers.net
Still error: gpg: keyserver receive failed: No name
Same error, when trying to see: gpg --show-keys xml-security-c-2.0.2.tar.bz2.asc
Any solution?
bml commented on 2020-11-05 12:32 (UTC)
I'm unable to build package:
Building xml-security-c... ==> Making package: xml-security-c 2.0.2-2 (qui 05 nov 2020 12:12:48) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found xml-security-c-2.0.2.tar.bz2.asc -> Found xml-security-c-2.0.2.tar.bz2 ==> Validating source files with sha256sums... xml-security-c-2.0.2.tar.bz2.asc ... Skipped xml-security-c-2.0.2.tar.bz2 ... Passed ==> Verifying source file signatures with gpg... xml-security-c-2.0.2.tar.bz2 ... FAILED (unknown public key 378B845402277962) ==> ERROR: One or more PGP signatures could not be verified! Failed to build xml-security-c
joomars commented on 2020-09-26 09:41 (UTC)
gpg --keyserver pool.sks-keyservers.net --recv-keys DCAA15007BED9DE690CD9523378B845402277962
yupi commented on 2020-08-05 05:54 (UTC) (edited on 2020-08-05 05:58 (UTC) by yupi)
I cannot build the latest version (which presumably should build fine without xalan-c), when new xalan-c is installed.
azymohliad commented on 2020-08-02 21:18 (UTC)
Is anybody having this error during PGP key import?
I also have exactly the same error when I try to import the key manually using:
kevku commented on 2020-07-28 05:03 (UTC)
yes, downgrade xalan-c to 1.11
Saduff commented on 2020-07-27 12:16 (UTC)
This package fails to build after today's update of xalan-c.
kevku commented on 2020-02-29 21:22 (UTC)
2.1.4 is the Java version, this package is the c++ lib
« First ‹ Previous 1 2 3 4 5 Next › Last »