Comment 7 for bug 2019086

Another update on this.

Turns out that the header text is not so important, but the header line is, even if it is a blank line between the BEGIN and first signature line. In my case, somehow, the blank lines were stripped between wget-ing the file and copying it to the remote machine where fce was running. And that was the source of my problems since the first line of the signature became the header.

I tested again and made sure that the exact downloaded file was used and I don't see the problem anymore. So this was a red herring for me and I'm not sure my problem was the same as the OP's problem.

Just to summarize.

This DOES NOT WORK:
===========================8<---------------------------------------
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEENTODksx68VxYHaPbcqZmZcXIjuYFAmTlPXQACgkQcqZmZcXI
===========================8<---------------------------------------

This works (and is how the downloaded file is, actually):
===========================8<---------------------------------------
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEENTODksx68VxYHaPbcqZmZcXIjuYFAmTlPXQACgkQcqZmZcXI
===========================8<---------------------------------------

This also works (real header instead of just a blank line):
===========================8<---------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)
iQEzBAEBCgAdFiEENTODksx68VxYHaPbcqZmZcXIjuYFAmTlPXQACgkQcqZmZcXI
===========================8<---------------------------------------

Maybe original license file from landscape could have a proper header there to avoid this kind of confusion (or errors, since blank lines could be stripped like it happened to me), but it is not broken.

Sorry for the noise. This may be unrelated to original issue.