On Mon, Mar 9, 2026 at 1:39 PM Michael J Gruber <[email protected]> wrote:
> Hi there > > Apparently, LLVM changed something in the python API even though their > release notes seem to claim otherwise. Here's a failed scratch build > of a rawhide commit which worked before LLVM 22 landed > > https://koji.fedoraproject.org/koji/taskinfo?taskID=143160960 > > Builds against other Fedoras work (until LLVM 22 lands there). > > This is unfortunate at this point in the release cycle. It's made > worse by the fact that we do not ship python-clang compat packages. Is > there a particular reason why not? > I believe the reason we don't ship python-clang in compat packages is that we don't know how to do that correctly. Normally, all the compat packages are shipped in /usr/lib64/llvmNN, so that would be something like /usr/lib64/llvmNN/lib/python3.14/site-packages/clang for python-clang. But I assume that wouldn't actually work because that's not the location where Python packages are expected to be located? I tried to look at what some compat packages from the Python ecosystem do. Looking at a package like python3-sqlalchemy1.4 it seems to just ship the files in the same location as the normal package and conflicts with it. This seems very fishy to me, and not really viable for us (as we'd have to conflict across all present and future compat packages). Regards, Nikita
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
