Re: Do we know the last binutils version it used to work?

2017-01-09 Thread Lisandro Damián Nicanor Pérez Meyer
On domingo, 8 de enero de 2017 23:40:00 ART Matthias Klose wrote:
> The
> binutils update plan was announced last June [1], and I plan to stick to
> it.
> 
> [1] https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

The binutils update plan says:

  Expecting binutils 2.27 (or maybe binutils 2.28) for stretch. binutils 2.27
  will be uploaded to unstable after the GCC defaults change.

We had binutils 2.27 which did not cause the issue and no technical reason why 
we *need* 2.28. Would you mind stating it?

-- 
Combata las características. Si una característica no es absolutamente
esencial, descártela, especialmente si tiene el mismo efecto que se
puede alcanzar mediante la combinación de otras características.
  Andrew S. Tanenbaum, de su libro "Computer Networks"

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Do we know the last binutils version it used to work?

2017-01-08 Thread Matthias Klose
On 08.01.2017 14:29, Lisandro Damián Nicanor Pérez Meyer wrote:
> Matthias: this bug is stopping a lot of packages from migrating and in doing 
> so near the freeze is hurting many teams (and their users!) like the Qt/KDE 
> one, so I'm planning to NMU it to the last working version.
> 
> Do we know which was the last version to properly work on mips*? Is there any 
> drawback in going back to that version?
> 
> Of course if you have a better course of action suitable for a fast fix, I'll 
> be glad to read it.

Please don't.  I'm fine to apply work arounds for port architectures, but not
for release architectures (I didn't decide on this status).  The binutils update
plan was announced last June [1], and I plan to stick to it.  At least one of
the mips toolchain maintainers (out of the five who committed to in the
architecture qualification process) seems to address RC issues, and according to
the upstream issue, there's work in progress.

Matthias

[1] https://lists.debian.org/debian-devel-announce/2016/06/msg7.html


-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk


Do we know the last binutils version it used to work?

2017-01-08 Thread Lisandro Damián Nicanor Pérez Meyer
Matthias: this bug is stopping a lot of packages from migrating and in doing 
so near the freeze is hurting many teams (and their users!) like the Qt/KDE 
one, so I'm planning to NMU it to the last working version.

Do we know which was the last version to properly work on mips*? Is there any 
drawback in going back to that version?

Of course if you have a better course of action suitable for a fast fix, I'll 
be glad to read it.

Kinds regards, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk