From: Xiyue Deng <manphiz@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: debian-python@lists.debian.org, notmuch@notmuchmail.org,
mailscripts@packages.debian.org,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: Anyone interested in python-pgpy?
Date: Fri, 06 Dec 2024 12:40:44 -0800 [thread overview]
Message-ID: <874j3gsfxv.fsf@debian-hx90.lan> (raw)
In-Reply-To: <87ttbhle3f.fsf@melete.silentflame.com>
[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]
Hi Sean,
Sean Whitton <spwhitton@spwhitton.name> writes:
> Hello,
>
> Thank you very much for the update and help thus far.
>
Sure thing!
I have further identified that this was caused by GPGME adding
"--verify" when invoking "gpg" command. I have updated Bug#1086378[1]
with more details and forwarded it[2] in hope to have a proper fix from
upstream.
Meanwhile, I have updated my MR[3] to disable the failed checks due to
GPGME upstream change only to fix the build and tests so that we still
have test coverage on the rest, hoping this would be acceptable for an
NMU. PTAL.
> --
> Sean Whitton
[1] https://bugs.debian.org/1086378
[2] https://github.com/SecurityInnovation/PGPy/issues/471
[3] https://salsa.debian.org/debian/pgpy/-/merge_requests/2
--
Regards,
Xiyue Deng
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2024-12-06 20:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 2:56 Anyone interested in python-pgpy? Sean Whitton
2024-12-02 21:28 ` Xiyue Deng
2024-12-03 2:34 ` Sean Whitton
2024-12-03 18:22 ` Xiyue Deng
2024-12-04 9:18 ` Xiyue Deng
2024-12-05 2:35 ` Sean Whitton
2024-12-05 4:03 ` Xiyue Deng
2024-12-06 2:50 ` Sean Whitton
2024-12-06 20:40 ` Xiyue Deng [this message]
2024-12-07 8:59 ` Sean Whitton
2024-12-07 10:27 ` Xiyue Deng
2024-12-08 1:34 ` Sean Whitton
2024-12-08 2:56 ` Xiyue Deng
2024-12-08 5:08 ` Sean Whitton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874j3gsfxv.fsf@debian-hx90.lan \
--to=manphiz@gmail.com \
--cc=debian-python@lists.debian.org \
--cc=dkg@fifthhorseman.net \
--cc=mailscripts@packages.debian.org \
--cc=notmuch@notmuchmail.org \
--cc=spwhitton@spwhitton.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).