[QUOTE=AAEBHolding;59837]I am sorry for the misunderstanding. I was never talking I am running it on a SLES 12.5 - I was talking about the fact I upgraded SLES 12.5 to 15.1 and therefore 15.1 is the system I have.
Below the results for your question. Also, another 8 new conflicts appear. I don’t know but it looks like SUSE has an issue in their repositories. Should I continue as asked at the end?
[CODE]
2020-04-15 14:55:29 root@AAEB-DEV203LD:~ => uname -a
Linux AAEB-DEV203LD 4.12.14-197.37-default #1 SMP Fri Mar 20 14:56:51 UTC 2020 (e98f980) x86_64 x86_64 x86_64 GNU/Linux
2020-04-15 14:55:33 root@AAEB-DEV203LD:~ => zypper ref -f
Forcing raw metadata refresh
Retrieving repository ‘sle-module-basesystem’ metadata …[done]
Forcing building of repository cache
Building repository ‘sle-module-basesystem’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Basesystem15-SP1-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Basesystem15-SP1-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Basesystem15-SP1-Updates’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Basesystem15-SP1-Updates’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘sle-module-desktop-applications’ metadata …[done]
Forcing building of repository cache
Building repository ‘sle-module-desktop-applications’ cache [done]
Forcing raw metadata refresh
Retrieving repository ‘sle-module-development-tools’ metadata …[done]
Forcing building of repository cache
Building repository ‘sle-module-development-tools’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Public-Cloud15-SP1-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Public-Cloud15-SP1-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Public-Cloud15-SP1-Updates’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Public-Cloud15-SP1-Updates’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Product-SLES15-SP1-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Product-SLES15-SP1-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Product-SLES15-SP1-Updates’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Product-SLES15-SP1-Updates’ cache .[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Packagehub-Subpackages15-SP1-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Packagehub-Subpackages15-SP1-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Packagehub-Subpackages15-SP1-Updates’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Packagehub-Subpackages15-SP1-Updates’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SUSE-PackageHub-15-SP1-Backports-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SUSE-PackageHub-15-SP1-Backports-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SUSE-PackageHub-15-SP1-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SUSE-PackageHub-15-SP1-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘sle-module-server-applications’ metadata …[done]
Forcing building of repository cache
Building repository ‘sle-module-server-applications’ cache .[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Server-Applications15-SP1-Pool’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Server-Applications15-SP1-Pool’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘SLE-Module-Server-Applications15-SP1-Updates’ metadata …[done]
Forcing building of repository cache
Building repository ‘SLE-Module-Server-Applications15-SP1-Updates’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘sle-module-web-scripting’ metadata …[done]
Forcing building of repository cache
Building repository ‘sle-module-web-scripting’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘MySQL Connectors Community’ metadata [done]
Forcing building of repository cache
Building repository ‘MySQL Connectors Community’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘MySQL Tools Community’ metadata …[done]
Forcing building of repository cache
Building repository ‘MySQL Tools Community’ cache …[done]
Forcing raw metadata refresh
Retrieving repository ‘MySQL 8.0 Community Server’ metadata [done]
Forcing building of repository cache
Building repository ‘MySQL 8.0 Community Server’ cache …[done]
All repositories have been refreshed.
2020-04-15 14:55:56 root@AAEB-DEV203LD:~ => zypper up -t patch
Refreshing service ‘Basesystem_Module_15_SP1_x86_64’.
Refreshing service ‘Public_Cloud_Module_15_SP1_x86_64’.
Refreshing service ‘SUSE_Linux_Enterprise_Server_15_SP1_x86_64’.
Refreshing service ‘SUSE_Package_Hub_15_SP1_x86_64’.
Refreshing service ‘Server_Applications_Module_15_SP1_x86_64’.
Loading repository data…
Reading installed packages…
Resolving package dependencies…
The following NEW patch is going to be installed:
SUSE-SLE-Module-Basesystem-15-SP1-2020-995
The following 3 packages are going to be upgraded:
libruby2_5-2_5 ruby2.5 ruby2.5-stdlib
3 packages to upgrade.
Overall download size: 4.1 MiB. Already cached: 0 B. After the operation, additional 19.9 KiB will be used.
Continue? [y/n/v/…? shows all options] (y): y
Retrieving package libruby2_5-2_5-2.5.8-4.11.1.x86_64 (1/3), 939.0 KiB ( 2.7 MiB unpacked)
Retrieving delta: ./x86_64/libruby2_5-2_5-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm, 76.7 KiB
Retrieving: libruby2_5-2_5-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm …[done]
Applying delta: ./libruby2_5-2_5-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm …[done]
Retrieving package ruby2.5-2.5.8-4.11.1.x86_64 (2/3), 309.1 KiB ( 1.4 MiB unpacked)
Retrieving delta: ./x86_64/ruby2.5-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm, 26.3 KiB
Retrieving: ruby2.5-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm …[done]
Applying delta: ./ruby2.5-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm …[done]
Retrieving package ruby2.5-stdlib-2.5.8-4.11.1.x86_64 (3/3), 2.9 MiB ( 11.9 MiB unpacked)
Retrieving delta: ./x86_64/ruby2.5-stdlib-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm, 326.1 KiB
Retrieving: ruby2.5-stdlib-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm …[done]
Applying delta: ./ruby2.5-stdlib-2.5.7_2.5.8-4.8.1_4.11.1.x86_64.drpm …[done]
Checking for file conflicts: …[error]
Detected 8 file conflicts:
File /usr/bin/erb
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/bin/gem
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/bin/irb
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/bin/ruby
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/share/man/man1/erb.1.gz
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/share/man/man1/irb.1.gz
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/share/man/man1/ri.1.gz
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File /usr/share/man/man1/ruby.1.gz
from install of
ruby2.5-2.5.8-4.11.1.x86_64 (SLE-Module-Basesystem15-SP1-Updates)
conflicts with file from package
ruby2.1-2.1.9-18.1.x86_64 (@System)
File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no):
[/CODE][/QUOTE]
Hi
Likely leftovers from the upgrade since they are all @System (No active or repository present), be interesting to see what the output from a zypper -vvv dup generates. In any case it should be fine to let them over write and get back to having an active repository.