On Mon, Jan 15, 2007 at 06:02:22PM +0100, Reinhard Tartler wrote: RT> Package: oops RT> Severity: serious RT> stop RT> RT> Max Kutny <[EMAIL PROTECTED]> writes: RT> RT> > On Mon, Jan 15, 2007 at 02:07:48PM +0100, Reinhard Tartler wrote: RT> > RT> Max Kutny <[EMAIL PROTECTED]> writes: RT> > RT> > Oops is very unstable and constantly aborts (every 30-60 mins) after RT> > RT> > upgrade from 1.5.23.cvs-3. RT> > RT> > RT> > RT> > It's not reproduceable although I'm sure it's possible to get trace if RT> > RT> > needed. RT> > RT> RT> > RT> Could you please get the source from RT> > RT> http://snapshot.debian.net/archive/2006/01/27/debian/pool/main/o/oops/oops_1.5.23.cvs-3.dsc, RT> > RT> rebuild it in a current etch or unstable system/chroot, and retry with RT> > RT> that? RT> > RT> RT> > RT> After that, please rebuild -4, and recheck. Can you now confirm the RT> > RT> problem is in the source change from -3 to -4? RT> > RT> > Rebuild 3 and 4 from scratch. The problem persists. RT> > RT> > Original source was not changed. RT> RT> Okay, this means that you confirm that a simple rebuild of oops RT> 1.5.23.cvs-3 (which is currently in debian/testing) makes the package RT> unusable for you. I'm therefore bumping the severity, since this would RT> mean that e.g. no security updates are possible, which makes the package RT> unsuitable for release, IMO.
Err. Sorry for misleading but I meant that it pesists the way I initially described it (1.5.23.cvs-3 is ok and 1.5.23.cvs-4 fails). RT> I ask you again, since I cannot reproduce the problem on my side: Are RT> you sure that this is not a hardware problem, and the problem is RT> actually already in -3? No, it's only in -4. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
