<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>This worked!</div>
<div><br>
</div>
<div>I cleaned the metadata and was able to install x2goserver.</div>
<div><br>
</div>
<div>
<div>Thank you,</div>
<div>Liz</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Mihai Moldovan <<a href="mailto:ionic@ionic.de">ionic@ionic.de</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, October 17, 2015 at 8:53 PM<br>
<span style="font-weight:bold">To: </span>Elizabeth Real Chavez <<a href="mailto:Elizabeth.Real@jpl.nasa.gov">Elizabeth.Real@jpl.nasa.gov</a>>, "<a href="mailto:x2go-dev@lists.x2go.org">x2go-dev@lists.x2go.org</a>" <<a href="mailto:x2go-dev@lists.x2go.org">x2go-dev@lists.x2go.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [X2Go-Dev] Failing package and GPG Keys<br>
</div>
<div><br>
</div>
<div>
<div>
<div>On 06.10.2015 06:15 PM, Real, Elizabeth (392K) wrote:</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>I need help to setup x2go server on a RHEL7 system. I configured the needed</div>
<div>repos and installed perl modules file::which, config::simple, capture::tiny.</div>
<div>However when I yum install x2goserver x2goserver-xsession I get an error/warning</div>
<div>about the GPG keys not being correct, the repo is looking</div>
<div>at <a href="http://packages.x2go.org/pub.key">http://packages.x2go.org/pub.key</a>. If that does not work, where else can I go</div>
<div>to get the keys?</div>
</blockquote>
<div><br>
</div>
<div>It looks like I didn't enable a shell feature when I manually re-signed all RPM</div>
<div>packages with the appropriate key(s), thus leaving some packages signed with the</div>
<div>"wrong" key.</div>
<div><br>
</div>
<div>I've re-done this operation for all RPM repositories, including EPEL and Fedora,</div>
<div>this time actually catching all packages.</div>
<div><br>
</div>
<div>Retrying the operation, maybe after cleaning metadata with yum clean metadata,</div>
<div>should succeed this time around.</div>
<div><br>
</div>
<div>There's something else that worries me, though...</div>
<div><br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>=========================================================================================================================</div>
<div> Package Arch Version </div>
<div> Repository Size</div>
<div>=========================================================================================================================</div>
<div>Installing:</div>
<div> x2goserver x86_64 4.0.1.19-3.el7 </div>
<div> epel 102 k</div>
<div> x2goserver-xsession x86_64 4.0.1.19-3.el7 </div>
<div> epel 13 k</div>
<div>Installing for dependencies:</div>
<div> libNX_X11-6 x86_64 </div>
<div>3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 516 k</div>
</blockquote>
<div><br>
</div>
<div>This means that x2goserver and x2goserver-xsession will be pulled from EPEL,</div>
<div>while the NX packages will be installed from x2go-release-epel.</div>
<div><br>
</div>
<div>That's probably going to blow up some time or later, especially since the EPEL</div>
<div>and our packages aren't exactly the same.</div>
<div><br>
</div>
<div>You could probably either drop our repository completely and only use EPEL or</div>
<div>play with yum priorities.</div>
<div><br>
</div>
<div>Sadly, RHEL 7 seems to have a history of broken yum priorities plugins, c.f.,</div>
<div><a href="https://access.redhat.com/discussions/1348623">https://access.redhat.com/discussions/1348623</a></div>
<div><br>
</div>
<div>Enable the optional channel, if not already available, and install</div>
<div>yum-plugin-priorities via</div>
<div><br>
</div>
<div>yum install -y yum-plugin-priorities</div>
<div><br>
</div>
<div>Afterwards, yum-config-manager --enable x2go-release-epel</div>
<div>--setopt="x2go-release-epel.priority=5" should give x2go-release-epel a higher</div>
<div>priority over epel. You should see x2goserver and x2goserver-xsession listed as</div>
<div>to-be-installed from x2go-release-epel.</div>
<div><br>
</div>
<div>I'm not entirely sure what the default priority of epel is, though. The digit</div>
<div>provided to yum-config-manager must be smaller than whatever the epel repository</div>
<div>has.</div>
<div><br>
</div>
<div>Naturally, not using our repository but epel will be easier on your part - and</div>
<div>more difficult for me.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Mihai</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>