On Sonntag, April 27, 2003, at 11:41 Uhr, J.H.M. Dassen (Ray) wrote:
On Tue, Apr 22, 2003 at 14:08:19 -0400, Matt Zimmerman wrote:
This looks like a genuine bug.
This raises the question why to use debian on a sparc system in the
place. This is a serious bug and apparently nobody want's to fix it.
Sure, it's all part of a big conspiracy against you.
That's what I thought. THEY've always been after me! ;-)
If you're unhappy with our priorities, feel
free to offer monetary incentives to change them.
I can not do so.
Emotional blackmail ("I'll
run Red Hat if you don't fix this") won't work.
I am not getting emotional but concerned on how to solve my problem. As
I can not solve it by myself, I am thinking about other options.
I strongly suspect moving to another distribution will be a painful
probably futile exercise.
As I already said: I do not want to move to an other distribution.
Perhaps it can offer some financial incentives to developers to
work on the problems you're running into?
My company is quite small, so I guess this is not an option.
That's not a
big job, but it's quite difficult to do without an actual sparc(64)
to test on. You may want to have a go at it yourself.
Call me stupid, but I can't do this due to lack of knowledge and
experience. What I can do is to give you root and serial (via
terminal-server) access to a sunfire v100 (our spare system) if you are
willing to fix this (and maybe one of the other 700+ bugs). As we
always have a spare system around to be able to replace one of the
running machines in short time, this could even be done with a longer
perspective. As I pointed out before: My company is willing to
contribute to the debian project as far as it can. So if you or anybody
else at the debian project is interested in this, just let me know.
Thanks for your help and best wishes
- From: "J.H.M. Dassen (Ray)" <email@example.com>