On Mon, Aug 29, 2011 at 13:51, Myra Nelson wrote:
> On Mon, Aug 29, 2011 at 12:42, Gaetan Bisson wrote:
>> [2011-08-29 12:13:29 -0500] Myra Nelson:
>>> If I sign the
>>> package with makepkg or manually with gpg --detach-sign, it creates a
>>> it creates a detached signature, .sig file. I have my
[2011-08-29 13:51:07 -0500] Myra Nelson:
> If I use gpg --sign instead of gpg --detach-sign the package verifies
> and installs just fine. That's what stumped me.
That's because since its suffix is not sig (in that case, a gpg file is
created containing both the package and the signature) the sign
On Mon, Aug 29, 2011 at 12:42, Gaetan Bisson wrote:
> [2011-08-29 12:13:29 -0500] Myra Nelson:
>> If I sign the
>> package with makepkg or manually with gpg --detach-sign, it creates a
>> it creates a detached signature, .sig file. I have my key using
>> pacman-key. When I attempt to install the p
[2011-08-29 12:13:29 -0500] Myra Nelson:
> If I sign the
> package with makepkg or manually with gpg --detach-sign, it creates a
> it creates a detached signature, .sig file. I have my key using
> pacman-key. When I attempt to install the package I get an error
> message "invalid or corrupted packa
I'm going to plead ignorance hear and have not been able to find the
solution. I've done a google search, read the man pages, read the help
documentation for gpg, and I still have a problem. If I sign the
package with makepkg or manually with gpg --detach-sign, it creates a
it creates a detached si
5 matches
Mail list logo
