Re: Accepted lynx 2.8.5-2sarge1.2 (source i386 sparc amd64)

2006-09-13 Thread Aníbal Monsalve Salazar
On Thu, Sep 14, 2006 at 12:13:03AM -, Thomas Dickey wrote: >Aníbal Monsalve Salazar <[EMAIL PROTECTED]> wrote: > >>>This is the third time this year that patch has been incorrectly >>>ascribed to OpenBSD. > >>Sorry for the misundertanding. I'll fix the lynx changelog file. >>I just used the pat

Re: Accepted lynx 2.8.5-2sarge1.2 (source i386 sparc amd64)

2006-09-13 Thread Thomas Dickey
Aníbal Monsalve Salazar <[EMAIL PROTECTED]> wrote: >>This is the third time this year that patch has been incorrectly >>ascribed to OpenBSD. > Sorry for the misundertanding. I'll fix the lynx changelog file. > I just used the patch from 2.8.5-2sarge2 in stable-security. ok. Perhaps you should r

Re: Accepted lynx 2.8.5-2sarge1.2 (source i386 sparc amd64)

2006-09-13 Thread Aníbal Monsalve Salazar
On Wed, Sep 13, 2006 at 08:19:02AM -0400, Thomas Dickey wrote: >In article <[EMAIL PROTECTED]> you wrote: >>-BEGIN PGP SIGNED MESSAGE- >>Hash: SHA1 > >>Format: 1.7 >>Date: Wed, 13 Sep 2006 18:41:49 +1000 >>Source: lynx >>Binary: lynx >>Architecture: source i386 sparc amd64 >>Version: 2.8.5-

Re: Accepted lynx 2.8.5-2sarge1.2 (source i386 sparc amd64)

2006-09-13 Thread Thomas Dickey
In article <[EMAIL PROTECTED]> you wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > Format: 1.7 > Date: Wed, 13 Sep 2006 18:41:49 +1000 > Source: lynx > Binary: lynx > Architecture: source i386 sparc amd64 > Version: 2.8.5-2sarge1.2 > Distribution: unstable > Urgency: high > Maintainer: