On Wed, 2025-04-09 at 20:58 -0400, Nicholas D Steeves wrote: Hello,
> > Has a bug been filed against llvmlite? If not, shouldn't there be > one? So it's not clear if there is a bug here. The problem is the llvmlite upstream is currently release is targeting llvm-15, which debian removed for being. Picking up a fix someone else made and updating it I got llvmlite to build against llvm-19 which is in debian, they helped clean up my fixes a bit more and suggested a new PR to use. Updating to 19 is just listed in their "Continuous Discussin: LLVM update plan" https://github.com/numba/llvmlite/issues/1048 > It seems to be that the worst case scenario would be a friendly NMU, > and > a bug is required for that. Ah ok. the regular maintainer for llvmlite M. Zhou responded a bit after you and it looks like they're willing to update it shortly. > > If llvmlite counts as a toolchain package then release team approval > for > an unblock will also be needed. The release team tends to get I don't know if llvmlite is a toolchain package, though it also fell out of testing because the version of llvm it used was removed, so this package looks to be an improvement over no package. > llvmlite fix, because you have been working towards supporting > Trixie's > release goals since February :) I don't lot of free time, and was hoping upstream would fix it but realized we were almost out of time and managed to get the last bits pushed over the finish line. > > I'm not sure if this link: > > > https://lists.debian.org/msgid-search/128a5dff67746a5120e3ab36650282b267a3652d.ca...@ghic.org > > should go at the llvmlite bug, or the release team bug, or both. Ok. I guess my plan is pass the fixes to llvmlite to lumin, then push numba, see how things build, and then go talk to the release team? Diane
signature.asc
Description: This is a digitally signed message part
