Re: Timeline for normal buildd operation on MIPS ?
Cyril Brulebois wrote:
> despite the words you're trying to use to mask it, you're really
> harrassing them for no valid reasons.
Actually, he is not. The mips arch (and to a certain extent the mipsel arch)
is causing problems both for the gFortran transition and for the
introduction of armel as a new arch which are now lenny release goals.
>> In order to help the people maintaining such packages to organize
>> themselves, can you publish a timeline of your works and goals for the
>> MIPS infrastructure? It has been more than three months that the
>> backlog is there; this is more than half the time left before the
> In order to keep the noise on this (these) list(s) at a suitable level,
> can you please stop that? It's been more than three weeks that you're
Likewise, if you would publish a timescale for the implementation of the
solutions which you keep saying are in work then a lot of people would be
able to schedule their work better. All people really want to know is are
you talking about a fix this month or this year?
Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id
Debian Developer | +44(0)7799 143369 | 0x1B3045CE
A. Because it breaks the logical sequence of discussion Q. Why is top