Subject: Bug#27440: gnupg: y2k bug in keygen...
From: Martin Schulze (joey@finlandia.Infodrom.North.DE)
Date: Sat Jan 08 2000 - 18:17:39 CET
Christian Kurz wrote:
> On 00-01-08 Martin Schulze wrote:
> > Christian Kurz wrote:
> > > > Package: gnupg
> > > > Version: 0.3.2-1
> > > >
> > > > -s valid for? (0) 15y
> > > > Key expires at 2013-09-30
> > > > Is this correct (y/n)? n
> > > > Key is valid for? (0) 50y
> > > > Key expires at 1912-08-16
> > > > Is this correct (y/n)? n
> > >
> > > This bug has been fixed in the new version of gnupg as you see below. So
> > > I would recommedn closing this bug.
>
> > Was it uploaded to Slink as well? If not, don't close the bug.
>
> Why do we need a fixed version for slink? We will release potato soon if
Maybe because there are still some lamers who use Slink? Who don't
believe that the perl catastrophe should happen now? Who think that
the freeze will at least be one month long and hasn't happened yet?
> nothing comes in our way, so I don't see why we need a fixed version for
> slink?
BS
Regards,
Joey
-- The good thing about standards is that there are so many to choose from. -- Andrew S. Tanenbaum-- To UNSUBSCRIBE, email to debian-bugs-dist-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
This archive was generated by hypermail 2b25 : Sat Jan 08 2000 - 18:19:51 CET