invalid packet (ctb=2d)

[Sjokotof]

Sjokotof <sjokotof2004 <at> hotmail.com> writes:

> 
> Situation:
> - production system Win32 running PGP 6.5.8, daily decrypting a series of 
> incoming files.
> - trial setup Win 32 running GnuPG 1.2.5, decrypting the same series of 
> files.
> - Trial ran OK for months, with the exception of a few days ago, when one 
> of the files choked GnuPG, but ran fine through GPG.
> 
> Below the output.
> What can be done to get this decrypted by GnuPG?

Some additional info I got by issuing [y:\progra~1\gnupg\gpg.exe --verbose --
home y:\progra~1\gnupg --list-sigs]:

y:/progra~1/gnupg\pubring.gpg
-----------------------------
pub  1024D/<ID1> 2002-01-11 <COMPANY1>
sig        <ID1> 2002-01-11   <COMPANY1>
sub  2048g/<ID2> 2002-01-11
sig        <ID1> 2002-01-11   <COMPANY1>

pub  1024D/<ID3> 2002-01-03 <COMPANY2>
sig        <ID3> 2002-01-03   <COMPANY2>
sub  2048g/<ID4> 2002-01-03
sig        <ID3> 2002-01-03   <COMPANY2>

pub  1024D/<ID5> 2001-04-09 <COMPANY3a>
sig        <ID5> 2001-04-09   <COMPANY3a>
sub  2048g/<ID6> 2001-04-09
sig        <ID5> 2001-04-09   <COMPANY3a>

pub  1024D/<ID7> 1998-07-01 <COMPANY3b>
sig        <ID7> 1998-07-01   <COMPANY3b>
sig   L    <ID5> 2001-04-09   <COMPANY3a>
sub  2048g/<ID8> 1998-07-01
sig        <ID7> 1998-07-01   <COMPANY3b>

Don't know if this is normal, but the last part shows a line starting  with 'sig 
L' (no idea what this means) which contains a repeat of <ID5>.
Does this need cleaning up, and if so, how? Or is this unrelated to the original 
error?
I would be grateful for any ideas here, thanks!

S.