Package conflicts running zypper dup

English Install/Boot/Login
1

I have been attempting to update Tumbleweed with zypper dup and keep getting package conflicts.

linux-q5lf:~ # zypper dup
Retrieving repository 'Packman' metadata ........................................................................................[done]
Building repository 'Packman' cache .............................................................................................[done]
Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ....................................................................[done]
Building repository 'openSUSE-Tumbleweed-Non-Oss' cache .........................................................................[done]
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ........................................................................[done]
Building repository 'openSUSE-Tumbleweed-Oss' cache .............................................................................[done]
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
15 Problems:
Problem: ruby2.6-rubygem-asciidoctor-1.5.8-1.3.i586 requires /usr/bin/ruby.ruby2.6, but this requirement cannot be provided
Problem: perl-checkbot-1.80-18.8.noarch requires perl(:MODULE_COMPAT_5.28.1), but this requirement cannot be provided
Problem: ruby2.5-2.5.3-2.2.i586 requires libruby2_5-2_5 = 2.5.3, but this requirement cannot be provided
Problem: ruby2.5-2.5.3-2.2.i586 requires ruby2.5-stdlib = 2.5.3, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.1.2-1.1.i586 requires libowcrypt.so.1, but this requirement cannot be provided

Problem: ruby2.6-rubygem-asciidoctor-1.5.8-1.3.i586 requires /usr/bin/ruby.ruby2.6, but this requirement cannot be provided
  not installable providers: ruby2.6-2.6.1-2.1.i586[repo-oss]
 Solution 1: deinstallation of daps-3.0.0-2.1.noarch
 Solution 2: deinstallation of ruby2.5-2.5.3-2.2.i586
 Solution 3: keep obsolete daps-3.0.0-2.1.noarch
 Solution 4: break ruby2.6-rubygem-asciidoctor-1.5.8-1.3.i586 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c):
2

Solution 2

3

[LEFT]What are the ramifications of deleting ruby2.5-2.5.3-2.2.i586? What is causing this in the first place?
[/LEFT]

4

ruby has recently been up-dated to 2.6 hence the conflict.