Sean Whitton <spwhitton@spwhitton.name> writes:

> 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?
>

No.  To be clear, python 3.13 + gpgme1.0 1.18.0-6+b1 works.  It should
be the change in gpgme that caused this.

> 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?
>

As the gpgme unit tests are passing, I'm not quite sure whether gpgme
should be in the blame, yet.  It could be that the pgpy use should be
adjusted.  I still need more time to figure this out as it's been a busy
week.  Still hope that someone more familiar with the matter can take a
look sooner than me :)

> -- 
> Sean Whitton

-- 
Regards,
Xiyue Deng