Re: Freeze Please?
GOTO Masanori wrote:
> At Sat, 8 Feb 2003 15:14:56 +1000,
> Anthony Towns wrote:
>> On Fri, Feb 07, 2003 at 11:15:43AM -0500, H. S. Teoh wrote:
>> > Of the three bugs, one is recent, one is barely over a week old, but the
>> > m68k problem is a month old. OK, so it *is* making progress, so perhaps
>> > it's not as bad as it appears to be.
>> The m68k problem is *probably* fixed or downgradable, I'm told. The "relocation
>> error" bugs that're popping up probably aren't fixed.
> Yes, it's already fixed in my environment. I second to downgrade its
> severity to important or something. I plan to dupload new m68k
> gcc-3.2 if my build and check is completed.
> The problem is that the buildd of crest.debian.org is something old
> environment, and building gcc always causes the problem. I don't have
? crest runs stable as do most of the build daemons but you have
access to the unstable chroot as do all other developers with
"dchroot unstable". Most debugging tools are installed; if you
need something else, writing email@example.com or me will get
it installed. The user unstable chroot was current yesterday
except for a buggy binutils and bash.
> any accounts for kullervo.debian.org, so kullervo may be not same, but
> it seems it's woody. I'm borrowing sid m68k machine account from
> ISHIKAWA Mutsumi (thanks for his great contribution!), and building
> Toolchain like gcc/glibc sometimes needs the latest development
> environment. We glibc maintainers have a labor to build and check
> such minor architecture.
> Moreover, m68k is too slow to develop. It's another problem.
I'm in touch with that emotion. However it's not as slow as
you might think.
We have another '060 loaned to Debian by Robert Hardy. The gcc
and glibc folk can have this to themselves for a while if they
want. Again, a stable install in base and an unstable chroot.
If you don't need it I'll be posting in a day or two to see if
someone is interested in admining it.