On Fri, Apr 4, 2014 at 10:23 AM, Finn Thain <fth...@telegraphics.com.au> wrote:
>> Once we do have a fixed version, we can communicate that around.
>
> If upsteam python gets fixed and that creates work for you, then pin your
> python version until you can build a new aranym, or somehow prevent the
> new python from being uploaded. You probably have a hundred ways to solve
> this issue. It is a problem for Debian buildd's. The upstream python bug
> tracker is obviously not the place to address it.
Indeed. Discussing it there will only put more fuel on the incentive to not
accept patches for unsupport architectures.
(Oh no, I though there was only one m68k user left, but there are three, and
they're fragmented ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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/CAMuHMdX-YbaTvjGuCHnvV3LGyAfNs83Dv18kFD5KzgB6ofQ=w...@mail.gmail.com
