On Thu, Feb 12, 2026 at 02:49:29PM -0800, Keith Packard wrote: > > > 1. libstdc++-arm-none-eabi-newlib:amd64 is selected for install > > This was the problem -- debian/tests/control didn't get updated to track > the changes in the package. > > > Was this change intentional and necessary? > > https://salsa.debian.org/debian/gcc-arm-none-eabi/-/commit/2b6ec1f7e7db63d43befefb4d97323d82cf830c7#58ef006ab62b83b4bec5d81fe5b32c3b4c2d1cc2_46_46 > > Yes. This package no longer supports the newlib C library, so it will > conflict with any version of newlib for arm-none-eabi, or any > newlib-depending package like libstdc++-arm-none-eabi-newlib. >...
How are you transitioning libnewlib-arm-none-eabi and the ecosystem behind it? Reverse-Build-Depends ===================== * firmware-microbit-micropython * hackrf (for libnewlib-arm-none-eabi) * libstdc++-arm-none-eabi (for libnewlib-arm-none-eabi) Reverse-Build-Depends-Indep =========================== * pico-sdk (for libnewlib-arm-none-eabi) * ubertooth (for libnewlib-arm-none-eabi) Reverse-Testsuite-Triggers ========================== * ubertooth (for libnewlib-arm-none-eabi) Reverse-Depends =============== * libstdc++-arm-none-eabi-newlib * libstdc++-arm-none-eabi-newlib * pico-sdk-source (for libnewlib-arm-none-eabi) Reverse-Recommends ================== * qmk (for libnewlib-arm-none-eabi) * ubertooth-firmware-source (for libnewlib-arm-none-eabi) > -keith cu Adrian
