On Thu, Oct 19, 2006 at 12:11:40PM +0200, Aurélien GÉRÔME wrote: > On Sun, Oct 15, 2006 at 07:01:43PM -0700, Steve Langasek wrote: > > On Sun, Oct 15, 2006 at 04:02:24PM +0200, Aurélien GÉRÔME wrote: > > > It only appears on alpha and it is probably a kernel bug, because > > > it works fine on other architectures. Therefore, I am setting the > > > severity to important.
> > Sorry, the reasoning seems to be lost on me here. The alpha binary package > > is completely unusable, right? That makes it a grave bug rather than an > > important one. > Well, yes, an IRC client cannot connect to the IRC server running on > an Alpha machine. I attempted to trace the issue into the kernel, but > the code for rt_sigtimedwait is really generic to any architectures > and the problem probably comes from elsewhere. > It does not happen on the other architectures which are the majority, > so I thought important was the correct severity. However, if you say > it is a grave bug, then it is... > Should I reassign it to linux-2.6 source package, because it does > not come from ircd-hybrid itself? Not at grave severity, no. "Alpha does not implement rt_sigtimedwait" would be a medium-severity bug. The grave bug is "ircd-hybrid is built on alpha and depends on a syscall that isn't properly implemented", which is a bug of ircd-hybrid that can be fixed in one of three ways: getting the kernel fixed, using some other kernel interface that works on alpha (which obviously isn't epoll either since that's 2.6-only), or dropping alpha from the architecture list for the package and asking the ftpmasters to remove the binaries. Speaking as an alpha porter, I think any of these three are ok here. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
