On Tue, 31 Mar 2020 at 09:34:04 +0100, Simon McVittie wrote: > I think the options to resolve this bug are: > > - Move llvm-toolchain-9 from gcc-8 development libraries to -9 or -10 > (I don't know whether this is a simple binNMU or whether it needs more > intrusive changes) > - Change the default to llvm-toolchain-10, as has already happened in > unstable
Er, that should of course say: as has already happened in *experimental*. On #debian-devel, kilobyte pointed out that if any packages are broken by advancing from LLVM 9 to 10, we will likely need to fix them for the bullseye release anyway, so perhaps nothing is lost by doing that transition sooner rather than later. However, mesa appears to be a prominent example of a package that currently requires LLVM 9, and doesn't work with 10 yet. > - Convince the gcc-8 maintainer to fix #954826 by removing the epoch from > the dependency (and possibly disabling gnat, since apparently gnat-8 is > no longer available) instead of by removing the package
