> I just checked and I can't spot any piece that is not fixed in unstable, > so I guess britney2 just got too confused by the src:binutils-embedded > taking over the binaries and what it all implied. I'll extend my hint > with the packages that have different versions between unstable and > testing in the set above and hope that that will help.
Yeah, I kinda wondered if something just got confused. In theory, this is just a change in the source package name which should generate compatible binary packages. Beyond this, there may be more adventures ahead with gcc-arm-none-eabi and gcc-riscv64-unknown-elf as those *do* break some packages in testing. I think all of those have been marked appropriately in unstable, but I don't know how that will carry into testing. In trying to simplify my life, I appear to have made a lot of things more complicated, at least in the short term... Sorry for the trouble; I've been ignoring this transition for several years... -- -keith
signature.asc
Description: PGP signature
