Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian.org@packages.debian.org
Usertags: pu
Chromium newest version FTBFS on bullseye with clang-13, but works fine with clang-16.
[ Reason ]
Chromium 118 (which will likely be released as stable today, and probably with CVEs) fails to build on bullseye's clang-13 with an issue that I can't figure out. I've got plenty of clang-13 workarounds in chromium already, but this most recent issue is in a large (tens of thousands of lines long), complex autogenerated c++ file. The file is generated exactly the same on bookworm & bullseye, but fails on bullseye's clang-13 while succeeding on bookworm's clang-14. I'm stuck at this point, and having clang-16 in bullseye would allow us to easily continue chromium's bullseye-security support. It will also allow us to drop a bunch of crufty workaround patches.
[ Impact ]
There's no impact for users, as packages in stable must explicitly choose to build against clang-16.
[ Tests ]
Chromium 118.0.5993.54 succeeded in building and running on bullseye with clang-16 packages from llvm-toolchain-16_16.0.6-15~deb11u1.
[ Risks ]
Low/no risk. Clang-16 is not currently in bullseye.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[ ] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
The changelog entry:
llvm-toolchain-16 (1:16.0.6-15~deb11u1) bullseye; urgency=medium
.
* Non-maintainer upload.
* Rebuild for bullseye.
No additional changes were necessary. I've not included a debdiff, since clang-16 is not already in bullseye.
[ Other info ]
For consistency and ease of maintenance I'll probably prepare this same package for bookworm, once 118 is released and all the security uploads are complete.