On Mon, Jan 24, 2005 at 07:50:23AM -0500, Justin Pryzby wrote:
> On Mon, Jan 24, 2005 at 10:14:39AM +0100, Goswin von Brederlow wrote:
> > Hi,
> >
> > I wanted to track this bug but can't reproduce it on amd64:
> Right. I've been working with the submitter without much success. I
> asked for a s
Excellent news, I am copying upstream with your findings. And I
appologies for reporting that there was a new upstream release; I read
the numbers wrong, of course (the maintainer lowered the severity of
the bug, which allowed to to enter testing, thusly confusing me).
Thanks,
Justin
On Thu, Ja
On Thu, Jan 27, 2005 at 09:48:43AM -0500, pryzbyj wrote:
> On Thu, Jan 27, 2005 at 01:28:55PM +0100, [EMAIL PROTECTED] wrote:
> > hi
> >
> > i'm not familiar with the bug system, so i'm emailing you... sorry
> > if i was doing wrong...
> Nope, this is good.
>
> > it's about the torsmo bug 290733:
On Mon, Jan 24, 2005 at 10:14:39AM +0100, Goswin von Brederlow wrote:
> Hi,
>
> I wanted to track this bug but can't reproduce it on amd64:
Right. I've been working with the submitter without much success. I
asked for a shell account but that wasn't a possibility. Coredumps
all indicate a stack
Hi,
I wanted to track this bug but can't reproduce it on amd64:
Linux frosties 2.6.8-frosties-1 #2 Sun Oct 3 22:06:03 CEST 2004 x86_64 GNU/Linux
Get:1 http://debian-amd64.alioth.debian.org testing/main torsmo 0.18-1 [37.7kB]
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
5 matches
Mail list logo