Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by Ladislav Hagara (4cac2cb18bc45f902fde4ff6b65e3cd966516bb1)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Ladislav Hagara <ladislav.hagara AT unob.cz>
  • To: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by Ladislav Hagara (4cac2cb18bc45f902fde4ff6b65e3cd966516bb1)
  • Date: Tue, 12 Feb 2013 18:38:25 +0100


>>>> GIT changes to master grimoire by Ladislav Hagara <hgr AT vabo.cz>:
>>>>
>>>> dev/null |binary
>>>> x11-toolkits/gtk+2/DETAILS | 2 +-
>>>> x11-toolkits/gtk+2/HISTORY | 3 +++
>>>> x11-toolkits/gtk+2/gtk+-2.24.14.tar.xz.sig | 0
>>>> x11-toolkits/gtk+2/gtk+-2.24.15.tar.xz.sig |binary
>>>> 5 files changed, 4 insertions(+), 1 deletion(-)
>>>>
>>>> New commits:
>>>> commit 4cac2cb18bc45f902fde4ff6b65e3cd966516bb1
>>>> Author: Ladislav Hagara <hgr AT vabo.cz>
>>>> Commit: Ladislav Hagara <hgr AT vabo.cz>
>>>>
>>>> gtk+2 2.24.15
>>> I get this error:
>>>
>>> Preparing gtk+2
>>> GPG checking source file gtk+-2.24.15.tar.xz...
>>> gpg: Signature made Mon Feb 11 09:29:46 2013 CET using RSA key ID
>>> 285B52A7
>>> gpg: BAD signature from "Ladislav Hagara (Source Mage GNU/Linux Signing
>>> Key) <lhagara AT sourcemage.org>"
>>> gpg: binary signature, digest algorithm SHA512
>>> Failure to verify gpg signature
>>>
>>>
>>> I assume that I have an obsolete gpg key somewhere. How to update it?
>>>
>>
>> Strange, I just resummon gtk+2 and none problem here.
>> What about other developers? The same problem?
>> Treeve, no problem with tar.xz archive? Are you able to open it?
> Works fine for me.


Thanks for info.
Ladislav Hagara





Archive powered by MHonArc 2.6.24.

Top of Page