Bug#311168: cpqarrayd: segfault on ProLiant DL385

2008-04-09 Thread Petter Reinholdtsen
severity 311168 important thanks [Kurt Roeckx] > Like I said, I can't reproduce it anymore. OK. I take this to mean that it at least work for someone, and reduce it to important. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscr

Bug#311168: cpqarrayd: segfault on ProLiant DL385

2008-03-16 Thread Petter Reinholdtsen
This bug keep cpqarrayd out of Lenny. Is this bug really release critical? The last comment about not being able to reproduce it make me wonder it perhaps should not be of severity serious. I am reluctant to change the severity without input from the package maintainer or the bug reporter. Can

Bug#311168: cpqarrayd: segfault on ProLiant DL385

2008-03-16 Thread Kurt Roeckx
On Sun, Mar 16, 2008 at 10:33:32PM +0100, Petter Reinholdtsen wrote: > > This bug keep cpqarrayd out of Lenny. Is this bug really release > critical? The last comment about not being able to reproduce it make > me wonder it perhaps should not be of severity serious. I am > reluctant to change t

Bug#311168: cpqarrayd: segfault on ProLiant DL385

2008-01-19 Thread Kurt Roeckx
On Sat, Jan 19, 2008 at 01:19:10AM +0100, Kurt Roeckx wrote: > severity 311168 serious > thanks > > On Sun, May 29, 2005 at 11:51:11AM -0700, Matt Taggart wrote: > > > > Your report is for 2.6.11, have you tried the 2.6.8 that will ship with > > sarge? > > You say the kernel is a "vanilla 2.6.11

Processed: Re: Bug#311168: cpqarrayd: segfault on ProLiant DL385

2008-01-18 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 311168 serious Bug#311168: cpqarrayd: segfault on ProLiant DL385 Severity set to `serious' from `important' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrato