Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.usenet.ovh!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: James Addison Newsgroups: linux.debian.maint.python Subject: Re: Matplotlib 3.10.0 for trixie? Date: Sun, 23 Mar 2025 13:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Mar 23 12:21:09 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.2 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, GMAIL=1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .jp-hosting. - helo: .mail-ed1-x535.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Forwarded-Encrypted: i=1; AJvYcCV9IwtHMnhJX1IwX0bIsh/LeHRPverR56pdxKIVCpmBmNdF4uX7WEFDZv3XO1rN5MQqem7kHGpWd5e0Agfx@lists.debian.org X-Gm-Message-State: AOJu0YwQdoLzJvnucF4wwuOQWiuIOSPl9894/XdRbrrKuxZtSn/k7TrW p01trMQTqRMV+dKjnXOq9v5Wl3Le4Wg/wtOSKQTqllkocrO4WBfjtNpKvG66Uzu156YayVaA9h/ VsUNK2KbMPDy+CHzh8/KbR97fk/nPySzYnAZA X-Gm-Gg: ASbGncu02Tp7baQWN50EyRHdTrhZVMq3q3mdQcI265ZUOkXTckrcvup2mA3c57Aosgz ZYeLNnFfOyqp6aoAxCWBbsdOb2l5EOAQYKmAsZbvdrsCQd1UZ2UEUZo6gfVnQra7JCcONiwBHwc IhjIVropkaJ86ZbFKquNLpcnFrQA== X-Google-SMTP-Source: AGHT+IEfFCqgGPsOjX53azAffWMW3LQhX75FSyejKrM/5Cxb9ovEdQ3fuRapzwxpJwRgjcPKgGCbG0P0MNLHlbwFV3w= X-Received: by 2002:a05:6402:1d4e:b0:5e7:5b30:3c4f with SMTP id 4fb4d7f45d1cf-5ebcd433b34mr8621029a12.14.1742731471424; Sun, 23 Mar 2025 05:04:31 -0700 (PDT) MIME-Version: 1.0 X-Gm-Features: AQ5f1JqDORV5nqITlhW4Q67eGhQ00zagA5Gp5XTWmRMDE7UuxxqXOWQyILf6E7s Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/22941 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CALDQ5Nz57=jH=wB0djtO7-TNxh+q0LEw_qNgJNeQwV3u7yfrgg@mail.gmail.com Approved: robomod@news.nic.it Lines: 50 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Alexandre Detiste , debian-python@lists.debian.org X-Original-Date: Sun, 23 Mar 2025 12:04:21 +0000 X-Original-Message-ID: X-Original-References: <29b74bd1-2181-4bf3-81a6-003cab5df87f@debian.org> <84b7b620-6f18-4f54-a13d-bb38ae0ee839@fsfe.org> <73CF4D23-2E84-40DB-9EBE-D74E9585ED00@riseup.net> <6d4e26d0-5fbd-4893-9264-1fb255111404@riseup.net> <418B4F61-1ADC-49EE-9946-9D31623456CD@riseup.net> <332450BD-FF2D-4BCC-A313-90809A0DB09D@riseup.net> Xref: csiph.com linux.debian.maint.python:16821 Hi, On Sat, 22 Mar 2025 at 19:08, Nilesh Patra wrote: > [ ... snip ... ] > On 19/03/25 2:11 am, Nilesh Patra wrote: > > On 18 March 2025 5:43:41=E2=80=AFam IST, Alexandre Detiste wrote: > > [ ... snip ... ] > > I cleaned up 2 more. Now there is only one mdanalysis remaining which h= angs on arm64 but works fine on amd64. > > > > On a brief look, it does not really look related to matplotlib. > > > > It could be great to try it out with current matplotlib on arm64 in deb= ci like environment. If it hangs, we can just file a bug report. > > > > I don't have the spoons for this at the moment :-/ > > The timeout looks unrelated to matplotlib, I however still did not manage= to find > time to actually test this. Haven't heard back regarding rebuilding rever= se-build dependencies > as well. > > If this looks not feasible, should we drop the idea of releasing 3.10.1 f= or trixie? My sense from inspecting the ci.debian.net results for mdanalysis is also that the timeout is unrelated to the matplotlib-3.10 update -- the same timeout (at approximately 2 hours and 50 minutes) seems to occur regardless of whether the exp/mpl-3.10 package is pinned into the build -- and in fact, checking again now, the timeout failure seems to occur for both amd64 and arm64. I wonder if it is a particular test case that sometimes gets stuck. In theory, I'd like to say: let's do the upgrade if we can -- I think users would generally be happy to have a (much) fresher version available, and although there's an effort/energy cost to upgrading, that effort cost could also potentially increase if we delay the upgrade to a later date... ...however: I'm not a Debian maintainer/developer (nor deb-python team member), only an eager contributor. I do intend to become a Debian project member at some point (possibly after improving my email etiquette and finding a more suitable laptop), but until then I can't really promise to contribute much assistance, so my opinions on this should be taken with a grain of salt! Cheers, James