Re: Do we know the last binutils version it used to work?
Lisandro Damián Nicanor Pérez Meyer <[email protected]>
| Newsgroups | gmane.linux.debian.kde.talk,gmane.linux.debian.ports.mips,gmane.linux.debian.devel.release |
|---|---|
| Message-ID | <4431722.HaJnil5AGX@tonks> |
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/msg00007.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/ -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAlhzqdkACgkQq2RfQGKG p9BJmQ//fXgxrvN6n0M9VcyRjeQfAWyIBFGLUGaevv+DmSZ2Qyz5Lut/qsK+Ep3R tQj3ifaXZYnij/wCFen6od9QfqUOsTJQIzG9fm21pkEFwfeUB+QVCAbbnj+eGRFi ayu1mwQh48q+e1mSniJQOr0nrTGOzl9RKMDfOGe5+jeCdWQzsUq6aGulsoDU591N 1o0G+jaR6DCOlWU6EwAgozafB7o/39Uu4+Iew9MbiZM5/l/DM26EYGdG6ruVAN9y k/Ggix7OvIJUsL81SJmIgGa3iHISpruh1QsSq6HBKJwDDTTki0+po93b6/7hyEmR 3GQleAg8NH5Xc7szUy0f28QqQ5fvlgROi70sZoH5bYEt972DInaVIDeHDLCVOi1+ h4t5T5rvk1fDf80iBec9LpB9XnZV189HPiC6hq1TdB4oNrH5kxt4MJADNPfPwuBI tgpizuDBX7RAGVBM+OsSz0Oznz3cUv8L769nIkxM0TOEy38rE0qGuzcFDtsw5dNo 8jOnIzTKT2VVIOrSljiiGGyyngiYKC3WHRcVktQMpGtvzefAlhrrogxWUklmgT1H NIaQnmg+FxjCUwV4NNAiJbWoqcl8D+DvH18nwvAWWrNC5uonsIjABiHuh9EGU5zg Yk8H4IwgV8reyjbNQa5Ueb7xC3GDDWpuihEAdUKMz23u4T/in+k= =epHa -----END PGP SIGNATURE-----