Subject: Bug#897 closed by Mihai Moldovan <[email-masked]> (Re: [X2Go-Dev] epel 5 repos have signature errors)

From: [email-masked] (X2Go Bug Tracking System)
Date: Thu, 02 Jul 2015 01:45:02 +0000

This is an automatic notification regarding your Bug report
which was filed against the buildscripts package:

#897: epel 5 repos have signature errors

It has been closed by Mihai Moldovan <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mihai Moldovan <[email-masked]> by
replying to this email.

-- 
897: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=897
X2Go Bug Tracking System
Contact [email-masked] with problems

Subject: Re: [X2Go-Dev] epel 5 repos have signature errors
From: Mihai Moldovan <[email-masked]>
To: [email-masked]
Date: Thu, 2 Jul 2015 03:41:44 +0200

Control: reassign -1 buildscripts 0
Control: close -1

On 02.07.2015 01:49 AM, Mihai Moldovan wrote:
> Created a VM and tested this hunch with one package. Looks like I was right. Will update the buildscript now and re-sign manually for now...

Changed the buildscripts in this commit to use the new GPG key for EPEL 5
(package and repo data signing):
http://code.x2go.org/gitweb?p=buildscripts.git;a=blob;f=bin/build-rpm-package;h=8af6d23fa7fdc5270993cbf2a19e839d9f78df83;hb=e6f76455ac92c08197f6d50e0dee989ff548a0d1

Additionally, all packages will be signed with the "new" GPG key.

I have verified that packages can now be successfully installed in a CentOS 5.8 VM.

Re-signing of the packages in the repository and the repo data is currently
underway.

Mihai

Subject: epel 5 repos have signature errors
From: Christian Trenkwalder <[email-masked]>
To: <[email-masked]>
Date: Tue, 30 Jun 2015 11:22:01 +0200

Package: <buildscripts>
Version: x2goserver.x86_64
0:4.0.1.19-0.0x2go2.1.git20150608.1064.main.el5.centos

Hello,
im using Red Hat Enterprise Linux Client release 5.8 (Tikanga) and get
the following error for more than 1 dependency:

> Header V3 RSA/SHA1 signature: BAD

For the full log see the attachemend, i think this may be just like #699.