Dear Maintainer,

running dpkg-buildpackage -S -d on the breeze source today gives me the
following :

  Error: Failed to resolve --signer-userid "Aurélien COUDERC <coucouf@debian.org>"
because: 216FFF40001A0E070E283B1F71A7E533F291A324, "Aurélien COUDERC <coucouf@debian.org>" cannot be authenticated at the required level (0 of 120). After checking that Aurélien COUDERC <coucouf@debian.org> really controls 216FFF40001A0E070E283B1F71A7E533F291A324, you could certify their certificate by running `sq pki link add 216FFF40001A0E070E283B1F71A7E533F291A324 "Aurélien COUDERC <coucouf@debian.org>"`.

  Error: Failed to resolve certificates
dpkg-buildpackage: erreur: échec de la signature du fichier ../breeze_6.2.5-2.dsc : la clé ne permet pas la signature


On the contrary, running
  debsign ../breeze_6.2.5-2_source.changes
did work.


I did non experience this error previously although I’m building
packages daily.


Thanks,
--
Aurélien

Hi!

This is because the dpkg OpenPGP sq backend was made aware that sq has
now (secret) keystore support, so it can be autoselected when the
user specifies a keyhandle by fingerprint or keyid (instead of
previously where only keyfiles were available to sq). And sq is used
as a preferential OpenPGP implementation among the available ones.

debsign does not currently have sq or SOP support.

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.

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. :)

Thanks,
Guillem

Hi !

Le jeudi 9 janvier 2025, 02:40:02 UTC+1 Guillem Jover a écrit :

Thanks.


$ sq pki link add 216FFF40001A0E070E283B1F71A7E533F291A324 "Aurélien COUDERC <coucouf@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@debian.org"


How nice and amusing ! :)