@mlschroe
Sorry, I'm not a great English speaker, but I assume that when the function is
described as `Parse armored OpenPGP packets from a file.` and returns `type of
armor found`, it will return `PGPARMOR_SIGNATURE` after finding the signature.
Especially when that value is part of the
@nwalfield
> Why does librepo need to parse signature files?
Librepo is used to download data from rpm repositories (metadata, packages,
...). Repository metadata can be signed with an OpenPGP signature. And librepo
can verify them.
Sample on an existing repository:
```
[google-chrome]
@nwalfield
Here is the PR https://github.com/rpm-software-management/librepo/pull/275 . It
contains commit that moves the original implementation of OpenPGP using GpgMe
into "gpg_gpgme.c" file and creates a new based on librpm API in the
"gpg_rpm.c" file.
There is a function `check_signature`