Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Sean Whitton Newsgroups: linux.debian.maint.python Subject: Re: Anyone interested in python-pgpy? Date: Thu, 05 Dec 2024 04:00:01 +0100 Message-ID: References: X-Original-To: Xiyue Deng X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Dec 5 02:51:09 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.198 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -5.5 Feedback-ID: 20115:3760:null:purelymail X-Pm-Original-To: debian-python@lists.debian.org User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Mailing-List: archive/latest/22611 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87mshaoo0r.fsf@melete.silentflame.com Approved: robomod@news.nic.it Lines: 23 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, notmuch@notmuchmail.org, mailscripts@packages.debian.org, Daniel Kahn Gillmor X-Original-Date: Thu, 05 Dec 2024 10:35:16 +0800 X-Original-Message-ID: <87mshaoo0r.fsf@melete.silentflame.com> X-Original-References: <875xo2u70p.fsf@melete.silentflame.com> <87ed2pu64q.fsf@debian-hx90.lan> <87v7w1qysu.fsf@melete.silentflame.com> <87y10wsk2d.fsf@debian-hx90.lan> <87ser3st5v.fsf@debian-hx90.lan> Xref: csiph.com linux.debian.maint.python:16526 Hello, On Wed 04 Dec 2024 at 01:18am -08, Xiyue Deng wrote: > Looks like this has nothing to do with Python version but gpgme: I have > tested with a snapshot of gpgme1.0 version 1.18.0-6+b1 and everything > works; upgrading to version 1.23.2-5 and the tests start to show the > same errors. I have been trying to see what has changed from gpgme side > but so far nothing conclusive yet. > > On the other hand, python-pgpy may be working fine as all failures in > the tests are caused by using the gpgme python binding, which somehow > doesn't like the PGP signed message generated by python-pgpy anymore. So the bug has nothing to do with the python 3.13 transition, in fact? I think that means its severity should be changed. I guess you're not sure yet whether or not it should be reassigned to pgpme? -- Sean Whitton