Results 1 to 8 of 8

Thread: Yast2-Ruby-bindings conflict in zypper

  1. #1

    Default Yast2-Ruby-bindings conflict in zypper

    Hi all,

    Wondering if anyone can provide advice on this issue. I was trying to install thunderbird from Zypper and found there is a conflict in my yast2-ruby-bindings.

    Code:
    #: sudo zypper install thunderbird
    [sudo] password for root:  
    Retrieving repository 'google-chrome' metadata .....................................[done]
    Building repository 'google-chrome' 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]
    Retrieving repository 'openSUSE-Tumbleweed-Update' metadata ........................[done]
    Building repository 'openSUSE-Tumbleweed-Update' cache .............................[done]
    Retrieving repository 'snappy' metadata ............................................[done]
    Building repository 'snappy' cache .................................................[done]
    Loading repository data...
    Reading installed packages...
    'thunderbird' not found in package names. Trying capabilities.
    Resolving package dependencies...
    
    Problem: yast2-ruby-bindings-4.1.2-1.1.x86_64 requires libowcrypt.so.1()(64bit), but this 
    requirement cannot be provided
      deleted providers: glibc-2.27-6.1.x86_64
     Solution 1: Following actions will be done:
      deinstallation of yast2-ruby-bindings-4.1.2-1.1.x86_64
      deinstallation of yast2-ntp-client-4.1.7-1.1.noarch
      deinstallation of yast2-packager-4.1.24-1.1.x86_64
      deinstallation of yast2-tftp-server-4.1.6-1.1.noarch
      deinstallation of yast2-snapper-4.1.0-1.1.x86_64
      deinstallation of yast2-installation-4.1.34-1.1.noarch
      deinstallation of autoyast2-installation-4.0.70-1.1.noarch
      deinstallation of yast2-add-on-4.1.10-1.1.noarch
      deinstallation of yast2-apparmor-4.1.5-1.1.noarch
      deinstallation of yast2-auth-client-4.1.0-1.1.noarch
      deinstallation of yast2-auth-server-4.1.0-1.1.noarch
      deinstallation of yast2-country-data-4.1.7-1.1.x86_64
      deinstallation of yast2-firewall-4.1.10-1.1.noarch
      deinstallation of yast2-fonts-4.1.0-1.1.x86_64
      deinstallation of yast2-hardware-detection-4.0.0-1.4.x86_64
      deinstallation of yast2-iscsi-client-4.1.4-1.1.noarch
      deinstallation of yast2-journal-4.1.5-1.1.noarch
      deinstallation of yast2-mail-4.1.0-1.1.noarch
      deinstallation of yast2-metapackage-handler-4.0.0-1.2.noarch
      deinstallation of yast2-nfs-client-4.1.4-1.1.noarch
      deinstallation of yast2-nis-client-4.1.0-1.1.x86_64
      deinstallation of yast2-online-update-4.0.2-1.1.noarch
      deinstallation of yast2-pam-4.0.0-1.2.noarch
      deinstallation of yast2-printer-4.0.3-1.1.x86_64
      deinstallation of yast2-proxy-4.1.0-1.1.noarch
      deinstallation of yast2-samba-server-4.1.3-1.1.noarch
      deinstallation of yast2-scanner-4.0.3-1.1.x86_64
      deinstallation of yast2-security-4.1.2-1.1.noarch
      deinstallation of yast2-services-manager-4.1.11-1.1.noarch
      deinstallation of yast2-slp-4.0.0-1.3.x86_64
      deinstallation of yast2-sound-4.1.1-1.1.x86_64
      deinstallation of yast2-storage-ng-4.1.48-1.1.x86_64
      deinstallation of yast2-sudo-4.0.1-1.1.noarch
      deinstallation of yast2-support-4.1.0-1.1.noarch
      deinstallation of yast2-sysconfig-4.1.2-1.1.noarch
      deinstallation of yast2-transfer-4.0.0-1.3.x86_64
      deinstallation of yast2-tune-4.0.2-1.1.x86_64
      deinstallation of yast2-update-4.1.8-1.1.x86_64
      deinstallation of yast2-users-4.1.6-1.1.x86_64
      deinstallation of yast2-vpn-4.0.1-1.1.noarch
      deinstallation of yast2-control-center-4.1.4-1.1.x86_64
      deinstallation of yast2-ldap-4.0.0-1.4.x86_64
      deinstallation of yast2-online-update-frontend-4.0.2-1.1.noarch
      deinstallation of libksuseinstall1-4.14.38-6.2.x86_64
      deinstallation of yast2-control-center-qt-4.1.4-1.1.x86_64
      deinstallation of libkde4-4.14.38-6.2.x86_64
      deinstallation of patterns-kde-kde_yast-20180709-5.1.noarch
      deinstallation of breeze4-style-5.14.5-1.1.x86_64
      deinstallation of kdebase4-runtime-17.08.3-6.2.x86_64
      deinstallation of kdebase4-workspace-libs-4.11.22-16.1.x86_64
      deinstallation of kdelibs4-4.14.38-6.2.x86_64
      deinstallation of kdelibs4-core-4.14.38-6.2.x86_64
     Solution 2: Following actions will be done:
      deinstallation of ruby2.5-2.5.3-2.1.x86_64
      deinstallation of ruby2.5-rubygem-abstract_method-1.2.1-2.10.x86_64
      deinstallation of ruby2.5-rubygem-cfa-0.7.0-1.1.x86_64
      deinstallation of ruby2.5-rubygem-cfa_grub2-1.0.1-1.1.x86_64
      deinstallation of ruby2.5-rubygem-cheetah-0.5.0-1.10.x86_64
      deinstallation of ruby2.5-rubygem-fast_gettext-2.0.0-1.1.x86_64
      deinstallation of ruby2.5-rubygem-gem2rpm-0.10.1-13.6.x86_64
      deinstallation of ruby2.5-rubygem-ruby-augeas-0.5.0-3.9.x86_64
      deinstallation of ruby2.5-rubygem-ruby-dbus-0.15.0-1.1.x86_64
      deinstallation of ruby2.5-rubygem-simpleidn-0.1.1-1.1.x86_64
      deinstallation of ruby2.5-rubygem-unf-0.1.4-1.9.x86_64
      deinstallation of ruby2.5-rubygem-unf_ext-0.0.7.5-1.2.x86_64
      deinstallation of ruby2.5-stdlib-2.5.3-2.1.x86_64
     Solution 3: install MozillaThunderbird-60.5.1-1.1.i586 despite the inferior architecture
     Solution 4: do not ask to install a solvable providing thunderbird
     Solution 5: break yast2-ruby-bindings-4.1.2-1.1.x86_64 by ignoring some of its dependenci
    es
    
    Choose from above solutions by number or cancel [1/2/3/4/5/c] (c):
    
    Which option would be best if any?

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,311
    Blog Entries
    15

    Default Re: Yast2-Ruby-bindings conflict in zypper

    Hi
    When was the last time you did a dup?

    Code:
    cat /etc/os-release | grep VERSION_ID
    VERSION_ID="20190226" <== current
    
    su -
    zypper ref
    zypper -vvv dup
    Then should be able to install...

    Code:
    su -
    zypper in MozillaThunderbird
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Default Re: Yast2-Ruby-bindings conflict in zypper

    I think I did a few times since I installed rather recently. Then I started running into this issue but ignored it till I had more time.

    Code:
    #: cat /etc/os-release | grep VERSION_ID
    VERSION_ID="20190126"
    
    Code:
    # zypper ref
    Repository 'google-chrome' is up to date.                                                  
    Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date.                                    
    Repository 'openSUSE-Tumbleweed-Oss' is up to date.                                        
    Repository 'openSUSE-Tumbleweed-Update' is up to date.                                     
    Repository 'snappy' is up to date.                                                         
    All repositories have been refreshed.
    
    Then ran the dup and had 1.6gb of updates. So quite a few. Didn't know about zypper dup, will look into that.

  4. #4

    Default Re: Yast2-Ruby-bindings conflict in zypper

    I see now, dup is the distro upgrade.

    Any advice on when to run that vs std zypper update like I had been running?
    I also saw this command, zypper up -t patch, maybe a good inbetween?

    I typically try to do an update every few weeks but I hesitate to do the distro update unless a problem exists. Baseless fears of big leaps?

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,311
    Blog Entries
    15

    Default Re: Yast2-Ruby-bindings conflict in zypper

    Quote Originally Posted by PeterChz View Post
    I see now, dup is the distro upgrade.

    Any advice on when to run that vs std zypper update like I had been running?
    I also saw this command, zypper up -t patch, maybe a good inbetween?

    I typically try to do an update every few weeks but I hesitate to do the distro update unless a problem exists. Baseless fears of big leaps?
    Hi
    For Tumbleweed, you must use 'dup' every time, this is the only way to move to the next snapshot (or in your case could/would be multiple) since it is a distribution upgrade... You should keep an eye on the Factory Mailing list archive so can follow on what's being updated as well;

    https://lists.opensuse.org/opensuse-factory/
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6

    Default Re: Yast2-Ruby-bindings conflict in zypper

    Quote Originally Posted by PeterChz View Post
    Hi all,

    Wondering if anyone can provide advice on this issue. I was trying to install thunderbird from Zypper and found there is a conflict in my yast2-ruby-bindings.

    Code:
    #: sudo zypper install thunderbird
    [sudo] password for root:  
    Retrieving repository 'google-chrome' metadata .....................................[done]
    Building repository 'google-chrome' 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]
    Retrieving repository 'openSUSE-Tumbleweed-Update' metadata ........................[done]
    Building repository 'openSUSE-Tumbleweed-Update' cache .............................[done]
    Retrieving repository 'snappy' metadata ............................................[done]
    Building repository 'snappy' cache .................................................[done]
    Loading repository data...
    Reading installed packages...
    'thunderbird' not found in package names. Trying capabilities.
    Resolving package dependencies...
    
    Problem: yast2-ruby-bindings-4.1.2-1.1.x86_64 requires libowcrypt.so.1()(64bit), but this 
    requirement cannot be provided
      deleted providers: glibc-2.27-6.1.x86_64
     Solution 1: Following actions will be done:
      deinstallation of yast2-ruby-bindings-4.1.2-1.1.x86_64
      deinstallation of yast2-ntp-client-4.1.7-1.1.noarch
      deinstallation of yast2-packager-4.1.24-1.1.x86_64
      deinstallation of yast2-tftp-server-4.1.6-1.1.noarch
      deinstallation of yast2-snapper-4.1.0-1.1.x86_64
      deinstallation of yast2-installation-4.1.34-1.1.noarch
      deinstallation of autoyast2-installation-4.0.70-1.1.noarch
      deinstallation of yast2-add-on-4.1.10-1.1.noarch
      deinstallation of yast2-apparmor-4.1.5-1.1.noarch
      deinstallation of yast2-auth-client-4.1.0-1.1.noarch
      deinstallation of yast2-auth-server-4.1.0-1.1.noarch
      deinstallation of yast2-country-data-4.1.7-1.1.x86_64
      deinstallation of yast2-firewall-4.1.10-1.1.noarch
      deinstallation of yast2-fonts-4.1.0-1.1.x86_64
      deinstallation of yast2-hardware-detection-4.0.0-1.4.x86_64
      deinstallation of yast2-iscsi-client-4.1.4-1.1.noarch
      deinstallation of yast2-journal-4.1.5-1.1.noarch
      deinstallation of yast2-mail-4.1.0-1.1.noarch
      deinstallation of yast2-metapackage-handler-4.0.0-1.2.noarch
      deinstallation of yast2-nfs-client-4.1.4-1.1.noarch
      deinstallation of yast2-nis-client-4.1.0-1.1.x86_64
      deinstallation of yast2-online-update-4.0.2-1.1.noarch
      deinstallation of yast2-pam-4.0.0-1.2.noarch
      deinstallation of yast2-printer-4.0.3-1.1.x86_64
      deinstallation of yast2-proxy-4.1.0-1.1.noarch
      deinstallation of yast2-samba-server-4.1.3-1.1.noarch
      deinstallation of yast2-scanner-4.0.3-1.1.x86_64
      deinstallation of yast2-security-4.1.2-1.1.noarch
      deinstallation of yast2-services-manager-4.1.11-1.1.noarch
      deinstallation of yast2-slp-4.0.0-1.3.x86_64
      deinstallation of yast2-sound-4.1.1-1.1.x86_64
      deinstallation of yast2-storage-ng-4.1.48-1.1.x86_64
      deinstallation of yast2-sudo-4.0.1-1.1.noarch
      deinstallation of yast2-support-4.1.0-1.1.noarch
      deinstallation of yast2-sysconfig-4.1.2-1.1.noarch
      deinstallation of yast2-transfer-4.0.0-1.3.x86_64
      deinstallation of yast2-tune-4.0.2-1.1.x86_64
      deinstallation of yast2-update-4.1.8-1.1.x86_64
      deinstallation of yast2-users-4.1.6-1.1.x86_64
      deinstallation of yast2-vpn-4.0.1-1.1.noarch
      deinstallation of yast2-control-center-4.1.4-1.1.x86_64
      deinstallation of yast2-ldap-4.0.0-1.4.x86_64
      deinstallation of yast2-online-update-frontend-4.0.2-1.1.noarch
      deinstallation of libksuseinstall1-4.14.38-6.2.x86_64
      deinstallation of yast2-control-center-qt-4.1.4-1.1.x86_64
      deinstallation of libkde4-4.14.38-6.2.x86_64
      deinstallation of patterns-kde-kde_yast-20180709-5.1.noarch
      deinstallation of breeze4-style-5.14.5-1.1.x86_64
      deinstallation of kdebase4-runtime-17.08.3-6.2.x86_64
      deinstallation of kdebase4-workspace-libs-4.11.22-16.1.x86_64
      deinstallation of kdelibs4-4.14.38-6.2.x86_64
      deinstallation of kdelibs4-core-4.14.38-6.2.x86_64
     Solution 2: Following actions will be done:
      deinstallation of ruby2.5-2.5.3-2.1.x86_64
      deinstallation of ruby2.5-rubygem-abstract_method-1.2.1-2.10.x86_64
      deinstallation of ruby2.5-rubygem-cfa-0.7.0-1.1.x86_64
      deinstallation of ruby2.5-rubygem-cfa_grub2-1.0.1-1.1.x86_64
      deinstallation of ruby2.5-rubygem-cheetah-0.5.0-1.10.x86_64
      deinstallation of ruby2.5-rubygem-fast_gettext-2.0.0-1.1.x86_64
      deinstallation of ruby2.5-rubygem-gem2rpm-0.10.1-13.6.x86_64
      deinstallation of ruby2.5-rubygem-ruby-augeas-0.5.0-3.9.x86_64
      deinstallation of ruby2.5-rubygem-ruby-dbus-0.15.0-1.1.x86_64
      deinstallation of ruby2.5-rubygem-simpleidn-0.1.1-1.1.x86_64
      deinstallation of ruby2.5-rubygem-unf-0.1.4-1.9.x86_64
      deinstallation of ruby2.5-rubygem-unf_ext-0.0.7.5-1.2.x86_64
      deinstallation of ruby2.5-stdlib-2.5.3-2.1.x86_64
     Solution 3: install MozillaThunderbird-60.5.1-1.1.i586 despite the inferior architecture
     Solution 4: do not ask to install a solvable providing thunderbird
     Solution 5: break yast2-ruby-bindings-4.1.2-1.1.x86_64 by ignoring some of its dependenci
    es
    
    Choose from above solutions by number or cancel [1/2/3/4/5/c] (c):
    
    Which option would be best if any?
    Solution n 2
    ------------------------------------
    Correct me if I'm wrong .
    ------------------------------------

  7. #7

    Default Re: Yast2-Ruby-bindings conflict in zypper

    Thanks all for your guidance. worked like a charm after running zypper dup. I was able to install Thunderbird and not get any zypper conflicts. I'll have to read more about the rolling release best practices, and join the recommended mailing list.

    Thanks again

  8. #8

    Default Re: Yast2-Ruby-bindings conflict in zypper

    I have the same problem - with zypper dup. So I can't just use zypper dup to fix it.
    Code:
    linux-q5lf:~ # zypper dup
    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):
    I have a Broadcom chip and for legal reasons the support is not in the ISO, so I have to download it from packman and manually install.I'm currently running 32 bit Tumbleweed, have replaced the 32 bit processor with a 64 bit processor and was planning to eventually install 64 bit LEAP 15.1. Is there any easy fix for the time being, or should I just reinstall with the 64 bit build and add back the b43 packages?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •