Package: gcc-arm-none-eabi Version: 15:15.2.rel1.1-1 Severity: serious https://ci.debian.net/packages/g/gcc-arm-none-eabi/testing/amd64/68631758/
... 61s The following packages have unmet dependencies: 61s satisfy:command-line : Depends: gcc-arm-none-eabi but it is not going to be installed 61s Depends: gcc-aarch64-none-elf but it is not going to be installed 61s Depends: gcc-arm-none-eabi-source but it is not going to be installed 61s Depends: libstdc++-arm-none-eabi-newlib but it is not going to be installed 61s E: Unable to satisfy dependencies. Reached two conflicting assignments: 61s 1. libstdc++-arm-none-eabi-newlib:amd64 is selected for install because: 61s 1. satisfy:command-line:amd64=1 is selected for install 61s 2. satisfy:command-line:amd64 Depends libstdc++-arm-none-eabi-newlib 61s 2. libstdc++-arm-none-eabi-newlib:amd64 Depends gcc-arm-none-eabi (= 15:14.2.rel1-1) 61s but none of the choices are installable: 61s - gcc-arm-none-eabi:amd64=15:14.2.rel1-1 is not selected for install ... This also affects some rdeps of the toolchain. Was this change intentional and necessary? https://salsa.debian.org/debian/gcc-arm-none-eabi/-/commit/2b6ec1f7e7db63d43befefb4d97323d82cf830c7#58ef006ab62b83b4bec5d81fe5b32c3b4c2d1cc2_46_46
