Your message dated Sat, 3 Jan 2015 11:04:44 -0500
with message-id
<CAMKht8icTfrF=4rzav1rqv-ppheg5watywmos4vvhxuxyoc...@mail.gmail.com>
and subject line I fixed this bug, but now #714 is a problem
has caused the X2Go Bug report #699,
regarding epel 5 repos have signature errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
699: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=699
X2Go Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: buildscripts
Severity: normal
As reported here:
http://lists.x2go.org/pipermail/x2go-user/2014-December/002705.html
A CentOS 5 user is getting these errors:
error: nx-libs-3.5.0.28-0.0x2go1.1.git20141114.546.main.el5.centos: Header V4
RSA/SHA1 signature: BAD, key ID 5bfe2b6e
error: libXcomp-3.5.0.28-0.0x2go1.1.git20141114.546.main.el5.centos: Header V4
RSA/SHA1 signature: BAD, key ID 5bfe2b6e
etc....
The cause appears to be that CentOS 5 cannot handle V4 signatures, only V3.
http://adminotes.blogspot.fr/2011/12/centos-6-rpm-sign-problem-v4-signatures.html
--- End Message ---
--- Begin Message ---
I fixed this bug in buildscript.git via commit 1c1553a .
Per the advise of MIke#1, I then rebuilt the EPEL5 packages only by
running commands like the following on japsand.x2go.org as x2go-admin:
NO_DELAY=yes FORCE_BUILD=yes RPM_BUILD_FOR="epel:5"
x2go-build+upload-rpm-package nx-libs main
(I had to run "git pull" under ~x2go-admin/buildscripts/ 1st.)
I tested the fix successfully. The fixed packages have version strings
like the following:
4.0.1.18-0.0x2go1.1.git20150103.949.main.el5.centos
However, I discovered bug #714 along the way. So X2Go Server's support
for epel 5 is still broken :(
--- End Message ---
_______________________________________________
x2go-dev mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-dev
