On Sat, Aug 08, 2015 at 09:45:33PM +0000, Thorsten Glaser wrote: > I would like to hear from either of you two how we can fixup the > situation for m68k in the meantime.
In the meantime there is nothing to fix because there is not a *single* package in debian linked against this library. This is only a problem for whoever has a m68k machine (or, for the matter, any other non-released architecture) meeting the following conditions: * running *unstable*. * in a *production* environment. * and having a third party package linked against libasprintf. Frankly, the number of people affected is probably zero. We are at the beginning of a release cycle. There will be more gettext releases in the following two years, and if not, you can always trigger a binary-only NMU for m68k once gcc-5 is in unstable. -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150808221035.ga26...@cantor.unex.es
