[X2Go-Dev] Bug#1354: Auto-update on CentOS did not work for nx-libs.x86_64 0:3.5.99.16-1.el7

[Franz Lückl]

Package: nx-libs
Version: 3.5.99.16-1.el7.x86_64

On this system auto-update for CentOS is enabled.  The system is CentOS Linux release 7.5.1804.
For some unknown reason auto-update did not work on this system.  It worked on other systems.

Here are the errors when updating with yum:
---> Package nx-libs.x86_64 0:3.5.99.16-1.el7 will be updated
--> Processing Dependency: nx-libs(x86-64) = 3.5.99.16-1.el7 for package: libNX_X11-3.5.99.16-1.el7.x86_64
--> Processing Dependency: nx-libs(x86-64) = 3.5.99.16-1.el7 for package: libXcomp-3.5.99.16-1.el7.x86_64
--> Processing Dependency: nx-libs(x86-64) = 3.5.99.16-1.el7 for package: libXcompshad-3.5.99.16-1.el7.x86_64
--> Finished Dependency Resolution
Error: Package: libXcompshad-3.5.99.16-1.el7.x86_64 (@epel)
           Requires: nx-libs(x86-64) = 3.5.99.16-1.el7
           Removing: nx-libs-3.5.99.16-1.el7.x86_64 (@epel)
               nx-libs(x86-64) = 3.5.99.16-1.el7
           Updated By: nx-libs-3.5.99.17-0.0build1.1.git20181127.3188.main.el7.x86_64 (x2go-release-epel)
               nx-libs(x86-64) = 3.5.99.17-0.0build1.1.git20181127.3188.main.el7
Error: Package: libXcomp-3.5.99.16-1.el7.x86_64 (@epel)
           Requires: nx-libs(x86-64) = 3.5.99.16-1.el7
           Removing: nx-libs-3.5.99.16-1.el7.x86_64 (@epel)
               nx-libs(x86-64) = 3.5.99.16-1.el7
           Updated By: nx-libs-3.5.99.17-0.0build1.1.git20181127.3188.main.el7.x86_64 (x2go-release-epel)
               nx-libs(x86-64) = 3.5.99.17-0.0build1.1.git20181127.3188.main.el7
Error: Package: libNX_X11-3.5.99.16-1.el7.x86_64 (@epel)
           Requires: nx-libs(x86-64) = 3.5.99.16-1.el7
           Removing: nx-libs-3.5.99.16-1.el7.x86_64 (@epel)
               nx-libs(x86-64) = 3.5.99.16-1.el7
           Updated By: nx-libs-3.5.99.17-0.0build1.1.git20181127.3188.main.el7.x86_64 (x2go-release-epel)
               nx-libs(x86-64) = 3.5.99.17-0.0build1.1.git20181127.3188.main.el7

The solution to this is to uninstall all of x2go and then reinstalling the x2go-server.

Have a nice day,
Franz Lückl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20181211/64a2b897/attachment.html>