ubuntu jammy (22.04) apt installation busted

[tamird]

Installing LLVM via apt in Github Actions:

          wget -qO- https://apt.llvm.org/llvm-snapshot.gpg.key | sudo tee /etc/apt/trusted.gpg.d/apt.llvm.org.asc
          echo deb http://apt.llvm.org/jammy/ llvm-toolchain-jammy main | sudo tee /etc/apt/sources.list.d/llvm.list
          sudo apt update
          sudo apt -y install clang gcc-multilib llvm locate qemu-system-{arm,x86}

produces

The following packages have unmet dependencies:
 clang : Depends: clang-19 (>= 19~) but it is not installable
 llvm : Depends: llvm-runtime (= 1:19.0-58~exp2+0~20240303091736.15~1.gbp3b61b3) but it is not going to be installed
        Depends: llvm-19 (>= 19~) but it is not installable
E: Unable to correct problems, you have held broken packages.

seen in https://github.com/aya-rs/aya/actions/runs/10083697631/job/27880839042?pr=997.

The code hasn't changed in a long time, but the problem is new (as of today).

[sylvestre]

yes, it is expected during the 19 => 20 migration

[imaami]

yes, it is expected during the 19 => 20 migration

If literally the entire upstream LLVM toolchain repo becomes unusable for several days in a row, and this is supposed to be "expected", then there is something fundamentally wrong with the migration process. This sort of oopsie should never be business as usual.

Currently every single GitHub CI workflow that relies on the official LLVM toolchain repo on Ubuntu 24.04 is unable to compile anything with Clang 19. And this happens even when simply trying to install the non-version-specific clang package. Pretty much the most vanilla use case you can think of.

Just adding

deb http://apt.llvm.org/noble/ llvm-toolchain main

to the repository list and doing

apt install clang

will cause a failure because clang depends on clang-19 which doesn't exist at the moment. At all.

I'd like to also remind everyone that Ubuntu 24.04 is a stable long-term support release, and it's also the most recent Ubuntu image available as a GitHub runner right now. No one who thought they could rely on the official LLVM repo can currently run CI builds with Clang-19 on GitHub.

The only reason why my Debian unstable desktop installation didn't break is because Debian's own repo has a clang-19 package. If it weren't for my GitHub CI breaking I would be blissfully unaware about this garbage fire situation.

[sylvestre]

@imaami Thanks for valuable feedback.

[sylvestre]

Should be fixed now

[firewave]

Can confirm that it is working.

[mccolljr]

This appears to be happening again? I'm seeing the same error messages today. This has been working in CI for weeks now, and suddenly it has broken

[sylvestre]

this one ?
#109276

[mccolljr]

Hmmm... I've seen that issue. I'm seeing the same errors that firewave reported in that issue thread, but not the same issue that the original poster of that issue mentioned