Bug#1139451: trixie-pu: package llvm-toolchain-22/1:22.1.7-1~deb13u1

[Andres Salomon]

On 7/25/26 04:38, Fabian Grünbichler wrote:
> On Fri, Jul 24, 2026, at 7:25 PM, Fabian Grünbichler wrote:
>> On Fri, Jul 24, 2026, at 6:35 PM, Andres Salomon wrote:
>>> On 7/24/26 11:39, Fabian Grünbichler wrote:
>>>> On Thu, Jul 23, 2026, at 7:04 PM, Andres Salomon wrote:
>>>>> On 7/6/26 14:37, Andres Salomon wrote:
>>>>>>
>>>>>>
>>> [...]
>>>>> Okay, that took a little longer than expected because building chromium
>>>>> on trixie with llvm-toolchain-22 broke (related to trixie's older
>>>>> bindgen), but we have a workaround for chromium and I was able to test
>>>>> chromium builds with this new ~deb13u2 package.
>>>>>
>>>>> I've attached the full debdiff between sid's version and this backport,
>>>>> but the only non-changelog difference between ~deb13u1 and ~deb13u2 is
>>>>> the bit at the end:
>>> [...]
>>>>
>>>> it would probably be good if we could wait for this MR to land:
>>>>
>>>> https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/224
>>>>
>>>> to avoid the need for another bump for rustc(-web)?
>>>
>>>
>>> Ah jeez - if that were a smaller commit, I'd just cherry-pick it and
>>> roll a ~deb13u3. Given the size though, I'll wait for the llvm packages
>>> to pick it up and migrate to forky.
>>
>> FWIW, the actual change is the first small hunk, the rest is testsuite
>> changes that I don't think the Debian build even runs. Let me
>> double-check and verify (and minimize accordingly).
> 
> updated MR (original one got merged already) opened, since what I wrote
> above holds.

I'm not seeing an updated MR, but if it's just skipping all the test/ 
stuff that's easy enough. I'll start up a deb13u3 build shortly.


> 
>>> Mike & Emilio, are you good with another 2-4 week delay for the llvm
>>> backoprt?
>>>
>>> Also in the meantime, I'd appreciate testing of the current packages:
>>>
>>> https://people.debian.org/~dilinger/llvm22/
>>>
>>> You can grab the orig from sid/forky if you want to rebuild, I'm on a
>>> train right now and don't have very good wifi. I've only tested it
>>> building chromium, so builds of firefox or rustc would help shake out
>>> any additional changes we might need to make.
>>
>> I can give them a spin to build a dlstage0 backport of rustc 1.96 from
>> experimental (the earlier versions are still on LLVM 21) over the
>> weekend.
> 
> rustc 1.96.1 from experimental (with a slight adaptation to match
> trixie's libgit2, and the `pkg.rustc.dlstage0` (no 1.95 in trixie yet)
> and `nowasm` (lack of wasm-tools) build profiles works as expected with
> your current test packages.

Great, thank you!