[opensuse] tumbleweed ruby update problem
I only have a single TW system and it's not used very much. Last time was back in January. Doing a zypper dup today, I got the following: Detected 19 file conflicts: File /usr/bin/erb from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/bin/gem from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/bin/irb from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/bin/ruby from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/lib/libgdbm_compat.so.4.0.0 from install of libgdbm_compat4-1.14.1-1.1.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/de/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/eo/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/fi/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/fr/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/ja/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/pl/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/pt_BR/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/sr/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/uk/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/locale/vi/LC_MESSAGES/gdbm.mo from install of gdbm-lang-1.14.1-1.1.noarch (openSUSE-Tumbleweed-Oss) conflicts with file from package libgdbm4-1.12-1.21.i586 (@System) File /usr/share/man/man1/erb.1.gz from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/share/man/man1/irb.1.gz from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/share/man/man1/ri.1.gz from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System) File /usr/share/man/man1/ruby.1.gz from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@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): Before I just do a new install I was wondering if someone maybe had a better suggestion? -- Per Jessen, Zürich (26.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2018-05-28 at 14:08 +0200, Per Jessen wrote:
I only have a single TW system and it's not used very much. Last time was back in January.
Doing a zypper dup today, I got the following:
Detected 19 file conflicts:
File /usr/bin/erb from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System)
File /usr/bin/gem from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@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):
Before I just do a new install I was wondering if someone maybe had a better suggestion?
I understand it is new package conflicts old package (openSUSE-Tumbleweed-Oss repo vs @System). It happens with TW systems that are not updated often, as a file changes package. I just let the install go ahead with the new version. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlsP3b4ACgkQtTMYHG2NR9XZAwCggzAjChIejdXF90Ncu/D7yGRO MioAn1K81jcK6EBQPsSNWbFfLs6VC7Bt =ri1+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2018-05-28 at 14:08 +0200, Per Jessen wrote:
I only have a single TW system and it's not used very much. Last time was back in January.
Doing a zypper dup today, I got the following:
Detected 19 file conflicts:
File /usr/bin/erb from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System)
File /usr/bin/gem from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@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):
Before I just do a new install I was wondering if someone maybe had a better suggestion?
I understand it is new package conflicts old package (openSUSE-Tumbleweed-Oss repo vs @System). It happens with TW systems that are not updated often, as a file changes package. I just let the install go ahead with the new version.
Sounds like I'll be left with parts of an old version lying around? Judging by the package names, ruby2.5 replaces ruby2.2, but there's no removal of 2.2. I'm just curious, it's not an important system. -- Per Jessen, Zürich (23.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-31 15:48, Per Jessen wrote:
Carlos E. R. wrote:
On Monday, 2018-05-28 at 14:08 +0200, Per Jessen wrote:
I only have a single TW system and it's not used very much. Last time was back in January.
Doing a zypper dup today, I got the following:
Detected 19 file conflicts:
File /usr/bin/erb from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@System)
File /usr/bin/gem from install of ruby2.5-2.5.0-4.2.i586 (openSUSE-Tumbleweed-Oss) conflicts with file from package ruby2.2-2.2.6-1.1.i586 (@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):
Before I just do a new install I was wondering if someone maybe had a better suggestion?
I understand it is new package conflicts old package (openSUSE-Tumbleweed-Oss repo vs @System). It happens with TW systems that are not updated often, as a file changes package. I just let the install go ahead with the new version.
Sounds like I'll be left with parts of an old version lying around? Judging by the package names, ruby2.5 replaces ruby2.2, but there's no removal of 2.2. I'm just curious, it's not an important system.
I thought that 2.2 should be removed, but now I don't know. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
participants (2)
-
Carlos E. R. -
Per Jessen