Re: Decide proper solution for binutils' mips* bug

I would like to mention that in my previous mail I forgot another possible fix 
for this bug: going back to binutils 2.27. The current uploads are snapshots 
of the next version, 2.28, and whereas the bug in question seems to habe been 
there all the time it started to affect us since a commit in the to-be 2.28 
version.

I've asked Matthias in [msg217] if there are any technical reasons to really 
go for 2.28 instead of 2.27. So far I did not get a reply to that.

[msg217] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844227#217>

I've taken a look at binutil's [changelog] and there seems to be Debian-
related bugs closed there, but it's not up to me to say wether the mips* bug 
has more precedence or not over the others.

[changelog] <http://metadata.ftp-master.debian.org/changelogs/main/b/binutils/
binutils_2.27.90.20170109-1_changelog>

Thanks, Lisandro.

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

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAlh2JfQACgkQq2RfQGKG
p9B4fBAAnwcBehzSJND6Xa4ykR5VdVTrGczQp4RS35Kk34RgocEkAZLbnIqx83D0
ieHSqJDdDFReOYhsOE8b+4VfldBQlvqFU1hNxhGNkRos085vg4rdDzC5jn0rwwmZ
O9Lv3rTBHy9zbki3G+33dW5wNXnBJQHUJPwP7ENgyLhnY9s+ui7apiHg29fiITNI
CwFNW4IE3yfUgQFcXtDyql0/KEXk3+vLAIU5dTFm8CKU6mdPW51QmLVzoJXCN7wN
rHl9f3jwZYAV2V1hJWLDKX1y+LCKecrKwzFy6DYhfHhfnBgdtwC1DdTnd3MMiaP/
p9EMgc7bp7k1CKoU9w8lfmQOyqJPtvtq8WM0zPy8JXtx6cLb2enSbjV5weuNr35J
3w2FqL0zEYQ+c936OAqmmtPMTTolDGNH2LqBKAHsML6cNYtr8TiOfM/84r5f2fIa
u4daIFn7gT7/cAKR6qytA6Dh8xOyiVbF/mkgbgB1SdnAP8KT/0n/69a0CKh6CvDD
SbucnRDkKO3nJf5ufMYurtBETQbk9J5diM7LwIqMFE5Rm0gU9wGbXRd2CTBFkj+D
MpiMmvkNpxPwPyweatthSLdIwn7FevRmCIVExUrbw6RLJTuBpcHkgsNIlqLryGyc
GMuS+HVMgTYydf8Q15773lspEizXvI18qF6o0WieDl4xitiNFlw=
=aNqk
-----END PGP SIGNATURE-----