On Wed, Dec 16, 2015 at 9:22 AM, Paul Fertser <fercer...@gmail.com> wrote: > > Hello, thank you for the prompt reply. > > On Wed, Dec 16, 2015 at 09:05:19AM +0100, Hakan Ardo wrote: > > Thanks, this is fixed in unstable. > > It is, but users of Debian testing right now receive confusing > messages and are not able to build anything. I might be > misunderstanding something but this seems important to me.
Indeed. I'm not sure what more to do about it though. The new packages should propagate to testing in 3 days. > > > Also, do you think it's worth considering to use more stricter > dependencies between avr-libc and gcc-avr (exact version match)? An exact version match is too strong as most versions are backwards compatible. But the current situation is not acceptable. What I have done in binutils version 2.25+Atmel3.5.0-2 (currently in unstable) is to declear it incompatible with any avr-libc older than 1.8.0+Atmel3.5.0 and latest avr-gcc already depends on any binutils-avr newer than 2.25+Atmel3.5.0. Maybe we should increase that to 2.25+Atmel3.5.0-2 though... -- Håkan Ardö
