Possible --list-keys bug in 1.2.3

[Martin Ehmsen]

Hi...

I think I have found a bug in gnupg-1.2.3.
It has to do with listing the keyring filename. It all started because 
psi (a jabber client) couldn't parse the output from gnupg-1.2.3.
Is the following the intended output from gnupg??:

#gpg --fixed-list-mode --with-colons --list-public-keys
tru::0:1052827211:1122902031
pub:u:1024:17:A028881BDEA361F6:1052827202:1122902031::u:::scESC:
uid:u::::::::Martin Ehmsen <ehmsen@imada.sdu.dk>:
... and so on

#gpg --fixed-list-mode --list-public-keys
/home/ehmsen/.gnupg/pubring.gpg
-------------------------------
pub 1024D/DEA361F6 2003-05-13 Martin Ehmsen <ehmsen@imada.sdu.dk>
sub 2048g/0D121BB5 2003-05-13
... and so on

The problem is the missing:
/home/ehmsen/.gnupg/pubring.gpg
-------------------------------
in the first output where --with-colons is turned on. Even with the 
--show-keyring option on, it dosen't show the keyring filename when 
--with-colons in turned on.
Is this a bug or is this the intended behaviour??
(This is has changed between 1.2.2 and 1.2.3.)

Thanks in advance

Martin Ehmsen
-- 
"No harm," The Boss burbles on.
"So anyway, I thought maybe we should do something about Branding."
"Branding?" I ask, match poised against the striker behind my back. 
"You mean as in burning a mark onto any user that complains?"
- BOFH