Control: found -1 4.5.0.20241231-1
Control: tags -1 sid forky

Hi,

[Doing the above to avoid the BTS getting confused about which suites are affected as sid is fixed by removal (and has cruft so is affected from the bts point of view, blocking migration)]

On Mon, 16 Feb 2026 09:55:58 -0800 keithp <[email protected]> wrote:
As gcc-arm-none-eabi is now built with picolibc as the default C library, the
current newlib package cannot be used with it. I've set gcc-arm-none-eabi to
conflict with all versions of libnewlib-arm-none-eabi, but if that package gets
updated to operate as an add-on C library, a new version of gcc-arm-none-eabi
can be uploaded to adjust that.


Given that the binaries are now removed, I don't think that's necessary. But, how are reverse (build) depends supposed to deal with this? I just spotted a MR against ubertooth (noticed via the autopkgtest failure), but it's missing an RC bug for the same. I still need to check the others.

paul@toba ~ $ reverse-depends -b libnewlib-arm-none-eabi
Reverse-Build-Depends
=====================
* firmware-microbit-micropython
* libstdc++-arm-none-eabi

Reverse-Build-Depends-Indep
===========================
* pico-sdk
* ubertooth

Reverse-Testsuite-Triggers
==========================
* ubertooth

Until newlib can migrate (after ubertooth is fixed or removed), also the other migrations (gcc-arm-none-eabi, ...) are blocked. (It took me quite some time to figure it out also because ofsrc:binutils-embedded taking over binaries, but I think I now get it).

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to