A related bonus topic I found worth to bring up here: The reason this is so split, has to wait on other builds to pull it in and more is that there is no explicit seeding of a llvm-toolchain-**. There is neither a ...-default package seeded pointing to one as in other languages nor is there a seed entry per release which clearly defines which one is meant to be pulled in.
https://static-reports.ubuntu.com/germinate/germinate- output/release/ubuntu.stonking/all%2Bextra shows: libllvm21 | llvm-toolchain-21 | mesa-libgallium | Ubuntu Developers <[email protected]> | 30710558 | 135358 libclang-cpp21 | llvm-toolchain-21 | libbpfcc | Ubuntu Developers <[email protected]> | 13724698 | 58935 And then a lot of informal generated by (not pulling anything in) clang-21 | llvm-toolchain-21 | Generated by llvm-toolchain-21 | Ubuntu Developers <[email protected]> | 127928 | 498 libclang-cpp21-dev | llvm-toolchain-21 | Generated by llvm-toolchain-21 | Ubuntu Developers <[email protected]> | 3298 | 37 So bpf and mesa kind of keep the llvm they depend on in main. I'd suggest to consider to explicitly seed the binary packages and version you really want, that would allow more control of all of this and the seed git would track the timing, motivation and intend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/391375 Title: [MIR] llvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm/+bug/391375/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
