#1087806 gpg-from-sq: command --update-trustdb is not yet implemented

Package:
gpg-from-sq
Source:
gpg-from-sq
Submitter:
Martin Dosch
Date:
2024-12-01 11:24:02 UTC
Severity:
normal
Tags:
#1087806#5
Date:
2024-11-18 20:48:31 UTC
From:
To:
Dear Maintainer,

setting up sbuild with the unshare backend according to
wiki.debian.org/sbuild fails when using gpg-from-sq:

```
mmdebstrap --variant=buildd unstable ~/.cache/sbuild/unstable-amd64.tar.zst
I: automatically chosen mode: unshare
I: chroot architecture amd64 is equal to the host's architecture
gpg: The command --update-trustdb is not yet implemented in the Sequoia
gpg: Chameleon.  To help us prioritize our work, please file a bug at
gpg:   https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues
E: gpg failed to initialize trustdb:: 512
```

Best regards,
Martin

#1087806#10
Date:
2024-11-26 16:42:29 UTC
From:
To:
control: forwarded -1 https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/107
thanks

Philip Rinn said in the upstream bug report: "From reading
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077600,
it seems mmdebstrap can easily work around this by using
--check-trustdb."

#1087806#17
Date:
2024-11-27 17:46:40 UTC
From:
To:
Dear Holger,

thank you very much for this information.

Do you happen to know where I have to configure this to make
gbp-buildpackage (ergo sbuild) work with gpg-from-sq?

Best regards,
Martin

#1087806#22
Date:
2024-12-01 11:15:43 UTC
From:
To:
Hi Martin,

* Martin Dosch <martin@mdosch.de> [2024-11-27 17:46]:

Why would this be related to gbp-buildpackage and sbuild?

According to your mail you run mmdebstrap from the command line:

* Martin Dosch <martin@mdosch.de> [2024-11-18 20:48]:

So you should add the argument just there:

mmdebstrap --skip=check/signed-by --variant=buildd unstable ~/.cache/sbuild/unstable-amd64.tar.zst

Cheers Jochen

#1087806#27
Date:
2024-12-01 11:21:50 UTC
From:
To:
Hi Jochen,

to get the things set up I purged gpg-from-sq and now when I reinstall
it, I always get that error thrown when I run gbp-buildpackage, hence
the question.
I'll re-setup it using that command and hope it will also work using
gbp-buildpackage. :)

Best regards,
Martin