1.0.5 bug: expiration date displaying bug

[Frank Tobin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In 1.0.5, I've attempted to set my expiration date for my key to two years
away; this appears to go successfully.  However, GnuPG, upon listing the
key shows the expiration date to be sometime in 2005, which is not two
years away.  My key (56FFD10A260C4FA3), when listed in 1.0.4, shows an
expiration date of 2003-04-27, but in 1.0.5, it is 2005-05-03.  This goes
for both my primary key and subkey.  So, I'm guessing it's being set
correctly in 1.0.5, but displayed incorrectly.

As shown:

GnuPG 1.0.5:
gpg --no-options --with-colons --list-keys 56FFD10A260C4FA3  | grep pub
pub:u:1024:17:56FFD10A260C4FA3:1999-04-22:2005-05-03:66:f:Dekan::scESC:

GnuPG 1.0.4:
gpg --no-options --with-colons --list-keys 56FFD10A260C4FA3  | grep pub
pub:q:1024:17:56FFD10A260C4FA3:1999-04-22:2003-04-27:59:-:Frank J. Tobin
<ftobin@bigfoot.com>:

Note that the expiration date in 1.0.5 is listed as 2005-05-03, while in
1.0.4 it is 2003-04-27.

- -- 
Frank Tobin		http://www.uiuc.edu/~ftobin/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (FreeBSD)
Comment: pgpenvelope 2.10.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjrsgnUACgkQVv/RCiYMT6OZ2ACePf9vF9VlfP3s1yiCvm6jR1YD
b5cAn0bMptv7Cc7K6ymzdodFOz0hcPr0
=eP8H
-----END PGP SIGNATURE-----