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: Tue, 03 Dec 2024 10:22:34 -0800 [thread overview]
Message-ID: <87y10wsk2d.fsf@debian-hx90.lan> (raw)
In-Reply-To: <87v7w1qysu.fsf@melete.silentflame.com>
[-- Attachment #1.1: Type: text/plain, Size: 1149 bytes --]
Hi Sean,
Sean Whitton <spwhitton@spwhitton.name> 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.
> Thanks.
>
> --
> Sean Whitton
--
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-03 18:31 UTC|newest]
Thread overview: 5+ 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 [this message]
2024-12-04 9:18 ` Xiyue Deng
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=87y10wsk2d.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).