Hello,
I need help to setup x2go server on a RHEL7 system. I configured the needed repos and installed perl modules file::which, config::simple, capture::tiny. However when I yum install x2goserver x2goserver-xsession I get an error/warning about the GPG keys not being correct, the repo is looking at http://packages.x2go.org/pub.key. If that does not work, where else can I go to get the keys?
# yum install x2goserver x2goserver-xsession Loaded plugins: langpacks, product-id, subscription-manager Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.19-3.el7 will be installed --> Processing Dependency: x2goagent >= 3.5.0.25 for package: x2goserver-4.0.1.19-3.el7.x86_64 --> Processing Dependency: pwgen for package: x2goserver-4.0.1.19-3.el7.x86_64 --> Processing Dependency: perl(File::BaseDir) for package: x2goserver-4.0.1.19-3.el7.x86_64 ---> Package x2goserver-xsession.x86_64 0:4.0.1.19-3.el7 will be installed --> Running transaction check ---> Package perl-File-BaseDir.noarch 0:0.03-14.el7 will be installed ---> Package pwgen.x86_64 0:2.07-1.el7 will be installed ---> Package x2goagent.x86_64 0:3.5.0.32-2.el7 will be installed --> Processing Dependency: nxagent for package: x2goagent-3.5.0.32-2.el7.x86_64 --> Running transaction check ---> Package nxagent.x86_64 0:3.5.0.32-2.el7 will be installed --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libXcompext.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libXcomp.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xtst.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xrender.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xrandr.so.2()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xpm.so.4()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xinerama.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xfixes.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xext.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xdmcp.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xdamage.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xcomposite.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_X11.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Running transaction check ---> Package libNX_X11-6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed --> Processing Dependency: nx-libs(x86-64) >= 3.5.0.29 for package: libNX_X11-6-3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos.x86_64 ---> Package libNX_Xcomposite1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xdamage1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xdmcp6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xext6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xfixes3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xinerama1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xpm4.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xrandr2.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xrender1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xtst6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libXcomp3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libXcompext3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libXcompshad3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed --> Running transaction check ---> Package nx-libs.x86_64 0:3.5.0.32-2.el7 will be installed --> Finished Dependency Resolution
Dependencies Resolved
Installing: x2goserver x86_64 4.0.1.19-3.el7 epel 102 k x2goserver-xsession x86_64 4.0.1.19-3.el7 epel 13 k Installing for dependencies: libNX_X11-6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 516 k libNX_Xcomposite1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 8.1 k libNX_Xdamage1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 8.0 k libNX_Xdmcp6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 13 k libNX_Xext6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 29 k libNX_Xfixes3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 11 k libNX_Xinerama1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 8.2 k libNX_Xpm4 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 35 k libNX_Xrandr2 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 10 k libNX_Xrender1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 21 k libNX_Xtst6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 14 k libXcomp3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 310 k libXcompext3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 35 k libXcompshad3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 33 k nx-libs x86_64 3.5.0.32-2.el7 epel 19 k nxagent x86_64 3.5.0.32-2.el7 epel 1.7 M perl-File-BaseDir noarch 0.03-14.el7 epel 13 k pwgen x86_64 2.07-1.el7 epel 24 k x2goagent x86_64 3.5.0.32-2.el7 epel 16 k
Install 2 Packages (+19 Dependent packages)
Total size: 2.9 M Installed size: 7.6 M Is this ok [y/d/N]: y Downloading packages: warning: /var/cache/yum/x86_64/7Workstation/x2go-release-epel/packages/libNX_Xdamage1-3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 5bfe2b6e: NOKEY Retrieving key from http://packages.x2go.org/pub.key
The GPG keys listed for the "Upstream X2Go EPEL Packages (Release Builds)" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.
Failing package is: libNX_Xdamage1-3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos.x86_64 GPG Keys are configured as: http://packages.x2go.org/pub.key
Thank you, Liz
On 06.10.2015 06:15 PM, Real, Elizabeth (392K) wrote:
I need help to setup x2go server on a RHEL7 system. I configured the needed repos and installed perl modules file::which, config::simple, capture::tiny. However when I yum install x2goserver x2goserver-xsession I get an error/warning about the GPG keys not being correct, the repo is looking at http://packages.x2go.org/pub.key. If that does not work, where else can I go to get the keys?
It looks like I didn't enable a shell feature when I manually re-signed all RPM packages with the appropriate key(s), thus leaving some packages signed with the "wrong" key.
I've re-done this operation for all RPM repositories, including EPEL and Fedora, this time actually catching all packages.
Retrying the operation, maybe after cleaning metadata with yum clean metadata, should succeed this time around.
There's something else that worries me, though...
========================================================================================================================= Package Arch Version
Repository SizeInstalling: x2goserver x86_64 4.0.1.19-3.el7
epel 102 k x2goserver-xsession x86_64 4.0.1.19-3.el7
epel 13 k Installing for dependencies: libNX_X11-6 x86_64
3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 516 k
This means that x2goserver and x2goserver-xsession will be pulled from EPEL, while the NX packages will be installed from x2go-release-epel.
That's probably going to blow up some time or later, especially since the EPEL and our packages aren't exactly the same.
You could probably either drop our repository completely and only use EPEL or play with yum priorities.
Sadly, RHEL 7 seems to have a history of broken yum priorities plugins, c.f., https://access.redhat.com/discussions/1348623
Enable the optional channel, if not already available, and install yum-plugin-priorities via
yum install -y yum-plugin-priorities
Afterwards, yum-config-manager --enable x2go-release-epel --setopt="x2go-release-epel.priority=5" should give x2go-release-epel a higher priority over epel. You should see x2goserver and x2goserver-xsession listed as to-be-installed from x2go-release-epel.
I'm not entirely sure what the default priority of epel is, though. The digit provided to yum-config-manager must be smaller than whatever the epel repository has.
Naturally, not using our repository but epel will be easier on your part - and more difficult for me.
Mihai
On 10/17/2015 09:53 PM, Mihai Moldovan wrote:
On 06.10.2015 06:15 PM, Real, Elizabeth (392K) wrote: There's something else that worries me, though...
========================================================================================================================= Package Arch Version Repository Size
Installing: x2goserver x86_64 4.0.1.19-3.el7 epel 102 k x2goserver-xsession x86_64 4.0.1.19-3.el7 epel 13 k Installing for dependencies: libNX_X11-6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 516 k
This means that x2goserver and x2goserver-xsession will be pulled from EPEL, while the NX packages will be installed from x2go-release-epel.
That's probably going to blow up some time or later, especially since the EPEL and our packages aren't exactly the same.
Definitely
You could probably either drop our repository completely and only use EPEL or play with yum priorities.
Sadly, RHEL 7 seems to have a history of broken yum priorities plugins, c.f., https://access.redhat.com/discussions/1348623
Enable the optional channel, if not already available, and install yum-plugin-priorities via
yum install -y yum-plugin-priorities
Afterwards, yum-config-manager --enable x2go-release-epel --setopt="x2go-release-epel.priority=5" should give x2go-release-epel a higher priority over epel. You should see x2goserver and x2goserver-xsession listed as to-be-installed from x2go-release-epel.
I'm not entirely sure what the default priority of epel is, though. The digit provided to yum-config-manager must be smaller than whatever the epel repository has.
There are no default priorities for any repos other then the overall default for the plugin of 99
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
This worked!
I cleaned the metadata and was able to install x2goserver.
Thank you, Liz
From: Mihai Moldovan <ionic@ionic.de<mailto:ionic@ionic.de>> Date: Saturday, October 17, 2015 at 8:53 PM To: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>>, "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: Re: [X2Go-Dev] Failing package and GPG Keys
On 06.10.2015 06:15 PM, Real, Elizabeth (392K) wrote: I need help to setup x2go server on a RHEL7 system. I configured the needed repos and installed perl modules file::which, config::simple, capture::tiny. However when I yum install x2goserver x2goserver-xsession I get an error/warning about the GPG keys not being correct, the repo is looking at http://packages.x2go.org/pub.key. If that does not work, where else can I go to get the keys?
It looks like I didn't enable a shell feature when I manually re-signed all RPM packages with the appropriate key(s), thus leaving some packages signed with the "wrong" key.
I've re-done this operation for all RPM repositories, including EPEL and Fedora, this time actually catching all packages.
Retrying the operation, maybe after cleaning metadata with yum clean metadata, should succeed this time around.
There's something else that worries me, though...
Installing: x2goserver x86_64 4.0.1.19-3.el7 epel 102 k x2goserver-xsession x86_64 4.0.1.19-3.el7 epel 13 k Installing for dependencies: libNX_X11-6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 516 k
This means that x2goserver and x2goserver-xsession will be pulled from EPEL, while the NX packages will be installed from x2go-release-epel.
That's probably going to blow up some time or later, especially since the EPEL and our packages aren't exactly the same.
You could probably either drop our repository completely and only use EPEL or play with yum priorities.
Sadly, RHEL 7 seems to have a history of broken yum priorities plugins, c.f., https://access.redhat.com/discussions/1348623
Enable the optional channel, if not already available, and install yum-plugin-priorities via
yum install -y yum-plugin-priorities
Afterwards, yum-config-manager --enable x2go-release-epel --setopt="x2go-release-epel.priority=5" should give x2go-release-epel a higher priority over epel. You should see x2goserver and x2goserver-xsession listed as to-be-installed from x2go-release-epel.
I'm not entirely sure what the default priority of epel is, though. The digit provided to yum-config-manager must be smaller than whatever the epel repository has.
Naturally, not using our repository but epel will be easier on your part - and more difficult for me.
Mihai