Xiyue Deng writes: > Hi Sean, > > Sean Whitton writes: > >> Hello Xiyue, >> >> On Mon 02 Dec 2024 at 01:28pm -08, Xiyue Deng wrote: >> >>> I have made a MR[1] including a few quick fixes for the RC bugs, in hope >>> that they are acceptable for another NMU to unblock this package and its >>> dependencies. PTAL. Thanks! >>> >>> [1] https://salsa.debian.org/debian/pgpy/-/merge_requests/2 >> >> Thank you very much for taking a look at this one. >> >> I'm a bit queasy about just disabling the failing tests. Do we have >> reason to believe that pgpy is not actually broken with Python 3.13? >> In other words, what makes you think that it's just the tests that are >> broken, not the program? >> > > I don't have an answer yet. I have tested 0.6.0-1.3 in a bookworm > sbuild chroot which has Python 3.11 and the tests passed. The build log > in Bug#1086378 shows it was using Python 3.12, so I would assume > something changed in Python 3.12 was the cause. I would do some further > checks to be sure. Though I do hope people familiar with the matters > can beat me to it. > 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. >> Thanks. >> >> -- >> Sean Whitton > > -- > Regards, > Xiyue Deng -- Regards, Xiyue Deng