Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Nicholas D Steeves Newsgroups: linux.debian.maint.python Subject: Re: llvmlite, numba, and llvm versions Date: Thu, 10 Apr 2025 03:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Apr 10 00:58:57 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-115.947 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.438, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MD5_SHA1_SUM=-1, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Debian-User: sten X-Mailing-List: archive/latest/22965 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87o6x4suh4.fsf@navis.mail-host-address-is-not-set Approved: robomod@news.nic.it Lines: 73 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Debian Python , PICCA Frederic-Emmanuel X-Original-Date: Wed, 09 Apr 2025 20:58:31 -0400 X-Original-Message-ID: <87o6x4suh4.fsf@navis.mail-host-address-is-not-set> X-Original-References: <128a5dff67746a5120e3ab36650282b267a3652d.camel@ghic.org> <07ba823bd2da3f97f2ee442eb4c8528a0a90d5c3.camel@ghic.org> Xref: csiph.com linux.debian.maint.python:16844 --=-=-= Content-Type: text/plain Hi Diane! Diane Trout writes: > Hi, > > I have a version of llvmlite that builds against llvm-19 with 2 test > failures that don't look to important. One of them is definitely just > the layout of the object file changed from what was expected. > > I got most of the help in the comments in here: > https://github.com/numba/llvmlite/pull/1092 [snip] > I also pushed all my changes to numba for it to build with the above > version of llvmlite and numpy 2.2 > https://salsa.debian.org/science-team/numba.git > > (numba should work, though I had to merge a small change to the tests > that I forgot to push to salsa a while ago, and it's building again, > but I'm tired and it'll take a while to run through all the tests > again) > > I hope it's still not too late to get numba back in to testing. Has a bug been filed against llvmlite? If not, shouldn't there be one? It seems to be that the worst case scenario would be a friendly NMU, and a bug is required for that. If llvmlite counts as a toolchain package then release team approval for an unblock will also be needed. The release team tends to get progressively busier as the release approaches, so filing an unblock authorisation bug sooner rather than later demonstrates courtesy and goodwill imho. I believe that you will find support for a cherry-picked llvmlite fix, because you have been working towards supporting Trixie's release goals since February :) I'm not sure if this link: https://lists.debian.org/msgid-search/128a5dff67746a5120e3ab36650282b267a3652d.camel@ghic.org should go at the llvmlite bug, or the release team bug, or both. Please feel free to keep me in CC, because I'd appreciate the encouragement of seeing that our processes still work. Kind regards, Nicholas --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmf3F7cQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYb2dD/9TF8o8PmqENwL5c2Mqkqsv9QeBrFnUULuG YaYkzgkarAE/5/2fgTy7CrWNqqrin3mFsfS2ONIVxCPlQ0Z6IVa9Ft9IFQFXgDex yZJ0KNfos8PNs+s8zSDPAoVR+VJSRRWtbS/lPzGxj0eHTjsSELheFF/UhckKedEr blenkWzAXs+YRALB3gqmHVh8fscM05V0Wnlw1YQaJF8MYMVlmKa3VxH6FSYzo6gU ktQfvhF20XgNQ7SpsjZdKwJ9p1yJB7svbmxNZSbaMkDjjY9BiP8C4CtcZPfmUI4g BM3IANYcqgKzveKcWDozBagGH9/tJ57bM4WnMpmtDvnfYO4t6VtHlkt1Loune83Y n1X3Z8avTqFaxIBqj67cG6TemFhaQJyfMxL4lNGNjbvMwczlSWiptMJRmoEGceFh YcVzjYwIerrWkrggxfq92BSCQR4woBYOmDY+z16k4H0AL+7n1d4Tx6nw17QBbQea nS91dtpFRgJJ5ALgmc0ZXYWM8pXSnWdHKJF3qYFJK82SUbwtdDb4ki02dP4tRz4L 2vEsJnMwIZF2xT8lyBEyQQ9ZMCtOuBfYiGP3mnJkMH2n1r0ripsX7+LTr/K6LoXJ aLFGPXswNWS3lqmNQCMs/OWnd1vcPeAQCf0RprNex0uJirDHDHGhR0AtrMqz3DQY Bh8yY5HuKg== =av3m -----END PGP SIGNATURE----- --=-=-=--