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