[Pkg-rust-maintainers] Bug#1092459: Failed to resolve key, cannot be authenticated at the required level (0 of 120) running dpkg-buildpackage
Aurélien COUDERC
coucouf at debian.org
Fri Jan 10 16:36:40 GMT 2025
Hi !
Le jeudi 9 janvier 2025, 02:40:02 UTC+1 Guillem Jover a écrit :
> > I did non experience this error previously although I’m building
> > packages daily.
>
> See above. Although I think whenever sq transparently uses the GnuPG
> keystore, it might be better to probably treat any private key found
> there equivalent as --own-key, so I've filed that upstream as
> https://gitlab.com/sequoia-pgp/sequoia-sq/-/issues/517.
Thanks.
> To make this work right away, you could (if you have not done that
> already) follow the hint from the sq message, which should make the
> dpkg-buildpackage command work again as before, while not needing to
> remove sq from the system. :)
No but what the message says doesn’t work…
$ sq pki link add 216FFF40001A0E070E283B1F71A7E533F291A324 "Aurélien COUDERC <coucouf at debian.org>"
error: unexpected argument '216FFF40001A0E070E283B1F71A7E533F291A324' found
Usage: sq pki link add [OPTIONS] <--cert <FINGERPRINT|KEYID>> <--all|--userid <USERID>|--userid-or-add <USERID>|--email <EMAIL>|--email-or-add <EMAIL>>
For more information, try '--help'.
Examples:
[… more example …]
Reading through the doc, the following works :
$ sq pki link add --cert=216FFF40001A0E070E283B1F71A7E533F291A324 --email="coucouf at debian.org"
How nice and amusing ! :)
--
Aurélien
More information about the Pkg-rust-maintainers
mailing list