Chdslv
December 29, 2020, 6:44pm
21
^^
It is posted above
zypper se -si ruby
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+-------------------------------------+---------+-------------+--------+------------------------
i | libruby2_7-2_7 | package | 2.7.2-2.1 | x86_64 | openSUSE-20201214-0
i | libruby2_7-2_7 | package | 2.7.2-2.1 | x86_64 | openSUSE-Tumbleweed-Oss
i | libstorage-ng-ruby | package | 4.3.75-1.1 | x86_64 | openSUSE-20201214-0
i | libstorage-ng-ruby | package | 4.3.75-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby | package | 2.7-1.2 | x86_64 | openSUSE-20201214-0
i | ruby | package | 2.7-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby-common | package | 2.6-3.3 | noarch | openSUSE-20201214-0
i | ruby-common | package | 2.6-3.3 | noarch | openSUSE-Tumbleweed-Oss
i | ruby-solv | package | 0.7.16-1.2 | x86_64 | openSUSE-20201214-0
i | ruby-solv | package | 0.7.16-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7 | package | 2.7.2-2.1 | x86_64 | openSUSE-20201214-0
i | ruby2.7 | package | 2.7.2-2.1 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-abstract_method | package | 1.2.1-2.18 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-abstract_method | package | 1.2.1-2.18 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-archive-tar-minitar | package | 0.5.2-9.19 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-archive-tar-minitar | package | 0.5.2-9.19 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-bundler | package | 2.1.4-1.6 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-bundler | package | 2.1.4-1.6 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-cfa | package | 1.0.2-1.5 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-cfa | package | 1.0.2-1.5 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-cfa_grub2 | package | 2.0.0-1.5 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-cfa_grub2 | package | 2.0.0-1.5 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-cheetah | package | 0.5.2-1.5 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-cheetah | package | 0.5.2-1.5 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-excon | package | 0.76.0-1.2 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-excon | package | 0.76.0-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-fast_gettext | package | 2.0.3-1.2 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-fast_gettext | package | 2.0.3-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-ffi | package | 1.14.2-1.1 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-ffi | package | 1.14.2-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-gem2rpm | package | 0.10.1-17.2 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-gem2rpm | package | 0.10.1-17.2 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-nokogiri | package | 1.10.10-1.3 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-nokogiri | package | 1.10.10-1.3 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-ruby-augeas | package | 0.5.0-3.19 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-ruby-augeas | package | 0.5.0-3.19 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-ruby-dbus | package | 0.15.0-1.8 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-ruby-dbus | package | 0.15.0-1.8 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-simpleidn | package | 0.1.1-1.9 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-simpleidn | package | 0.1.1-1.9 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-unf | package | 0.1.4-1.17 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-unf | package | 0.1.4-1.17 | x86_64 | openSUSE-Tumbleweed-Oss
i | ruby2.7-rubygem-unf_ext | package | 0.0.7.7-1.4 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-unf_ext | package | 0.0.7.7-1.4 | x86_64 | openSUSE-Tumbleweed-Oss
i | rubygem-docker-api | package | 1.13.2-1.17 | x86_64 | openSUSE-20201214-0
i | rubygem-docker-api | package | 1.13.2-1.17 | x86_64 | openSUSE-Tumbleweed-Oss
i | yast2-ruby-bindings | package | 4.3.11-1.1 | x86_64 | openSUSE-20201214-0
i | yast2-ruby-bindings | package | 4.3.11-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
Chdslv
December 29, 2020, 6:56pm
22
Just now there was a new update. Rebooted and started Yast, clicked on Software Management and got this.
https://ibb.co/0J11KJhhttps://i.ibb.co/f0ZZ904/Screenshot-20201229-185055.png
I compared that to what I have.
Note that these packages show up twice in your output, because you have duplicate repos (not really a problem, though you might consider removing one of them).
My list is similar to yours. A few have different versions, but I think that’s because I just did an update, and today’s update included some ruby updates.
You have some ruby packages that I don’t have. And I have one that you don’t have. But those might be needed by some other software, so not necessarily a problem.
Does:
zypper verify
report any problems?
Chdslv
December 29, 2020, 7:07pm
24
zypper se -si nokogiri
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+--------------------------+---------+-------------+--------+------------------------
i | ruby2.7-rubygem-nokogiri | package | 1.10.10-1.3 | x86_64 | openSUSE-20201214-0
i | ruby2.7-rubygem-nokogiri | package | 1.10.10-1.3 | x86_64 | openSUSE-Tumbleweed-Oss
Chdslv
December 29, 2020, 7:10pm
25
sudo zypper verify
[sudo] password for root:
Retrieving repository 'packman' metadata .............................................................[done]
Building repository 'packman' cache ..................................................................[done]
Loading repository data...
Reading installed packages...
Dependencies of all installed packages are satisfied.
Shall I disable openSUSE-20201214-0 repo?
Chdslv
December 29, 2020, 7:19pm
26
Which repos should I delete?
ypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI
| Service
---+----------------------------------+-----------------------------+---------+-----------+---------+----------+--------+--------------------
-------------------------------------------------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | No | ---- | ---- | 99 | rpm-md | http://download.ope
nsuse.org/tumbleweed/repo/non-oss/ |
2 | download.opensuse.org-oss | Main Repository (OSS) | No | ---- | ---- | 99 | rpm-md | http://download.ope
nsuse.org/tumbleweed/repo/oss/ |
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope
nsuse.org/update/tumbleweed/ |
4 | microsoft-edge-dev | microsoft-edge-dev | Yes | (r ) Yes | Yes | 99 | rpm-md | https://packages.mi
crosoft.com/yumrepos/edge/ |
5 | openSUSE-20201214-0 | openSUSE-20201214-0 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope
nsuse.org/tumbleweed/repo/oss |
6 | packman | packman | Yes | (r ) Yes | Yes | 90 | rpm-md | http://ftp.gwdg.de/
pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
7 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.ope
nsuse.org/debug/tumbleweed/repo/oss/ |
8 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope
nsuse.org/tumbleweed/repo/non-oss/ |
9 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope
nsuse.org/tumbleweed/repo/oss/ |
10 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.ope
nsuse.org/source/tumbleweed/repo/oss/ |
11 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope
nsuse.org/update/tumbleweed/ |
12 | skype-stable | skype (stable) | Yes | (r ) Yes | Yes | 99 | rpm-md | https://repo.skype.
com/rpm/stable/
hcvv
December 29, 2020, 7:38pm
27
When they are disabled, there is no need to delete them except for having a clean list. Thus IMHO you can do that later.
And the zypper dup should already have switched all packages that were possibly installed from the now disabled repos to those of the enabled ones. Which should not result in differences, as the URIs and thus the repos were the same.
Chdslv
December 29, 2020, 8:04pm
28
What might be the reason of this?
Failed to load Module 'PackageCallbacks' due to: Failed to load Module 'CommandLine' due to: Failed to load Module 'XML' due to: cannot load such file -- nokogiri
But, nokogiri is there.
I would suggest that. It is repo #5 in your latest list, and it duplicates #9 .
The duplicate is not the cause of your problem. However, having duplicates does slowdown updating, because the system has to read the repo twice.
At this stage, maybe my best advice is that you open a bug report on your Yast issues. That will get the attention of the Yast maintainers, who know more about the internals of Yast than I do.
hcvv
December 29, 2020, 8:26pm
30
Oh boy, I missed that one. That means three (3!) times the OSS repo.
After this is resolved, maybe the OP should try to find out why and how he is duplicating repos. It looks at not being a glitch one time done, but more consistent
Chdslv
December 29, 2020, 8:44pm
31
nrickert:
I would suggest that. It is repo #5 in your latest list, and it duplicates #9 .
The duplicate is not the cause of your problem. However, having duplicates does slowdown updating, because the system has to read the repo twice.
At this stage, maybe my best advice is that you open a bug report on your Yast issues. That will get the attention of the Yast maintainers, who know more about the internals of Yast than I do.
How do I make a bug report with this?
Chdslv
December 29, 2020, 9:02pm
32
hcvv
December 29, 2020, 9:08pm
33
Very good. Now we have to wait.
I do not know what you wanted to do when you found out this problem and how important it is, but you can do all software management using zypper.
Chdslv
December 29, 2020, 9:26pm
34
Yes, I know and I like to do everything through the terminal. But, I don’t like something going wrong in a distro. I rarely click on it, but…
hcvv
December 29, 2020, 9:29pm
35
Chdslv:
Yes, I know and I like to do everything through the terminal. But, I don’t like something going wrong in a distro. I rarely click on it, but…
Of course it should work (and it does for most). I only asked because you might need help for something that is to be done asap.
Chdslv
December 30, 2020, 7:27pm
37
The solution.
Yast is working again!
Chdslv
December 30, 2020, 7:39pm
38
How do I make this thread as solved so, others can benefit from this?
hcvv
December 30, 2020, 7:51pm
39
No need do do that, your joyful post #37 above is enough to tell everybody you are satisfied.
Congratulations. It will probably stay a riddle why that gem was broken. In any case you had fruitful cooperation with Josef Reidinger. Well done.