Leap 15.6 dup brings "29 problem" questions, blacklisted nouveau, and non-revival from suspend?

English Applications
1

Folks:

Running zypper dup this morning again showed error in repo, or repos, which I think might have been happening for a while, but then shows 29 dependency issues with tough questions to address . . . too many to deal with this morning . . . but, that seems like a lot?

And, again seemingly my selection for nouveau seems to have been blacklisted, which seems to be a recurring problem . . . that problem then interferes with “reviving from suspend.” Lsmod does not show any listing for “nouveau” at all. Had to shut down with power button . . . now typing this in TW.

https://forums.opensuse.org/t/how-to-unblacklist-nouveau-in-leap-15-6/172170/8

https://bugzilla.suse.com/show_bug.cgi?id=1217613

2

And where is the output?

3

It’s over in the Leap 15.6 partition . . . recurring problems with non-revival from suspend means no time to reboot to it and reboot out of it . . . . Time crunch today.

Just reporting the problems as they are happening . . . from recent posts on the Factory list-serve it does seem like “repo” problems are going around???

The two linked threads likely contain all of the recurring issues . . . except for the “29 problems” data from today . . . have to get back to it and post it here when I get it.

4

Here you go, “Nvidia” repo was supposed to be disabled . . . no time to re-check it this am.

sudo zypper ref && sudo zypper dup
[sudo] password for root: 
Retrieving repository 'repo-non-free (15.6)' metadata ...................[error]
Repository 'repo-non-free (15.6)' is invalid.
[NVIDIA:repo-non-free|https://download.nvidia.com/opensuse/leap15.6] Valid metadata not found at specified URL
History:
 - [NVIDIA:repo-non-free|https://download.nvidia.com/opensuse/leap15.6] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'repo-non-free (15.6)' because of the above error.
Retrieving repository 'Packman Repository' metadata ......................[done]
Building repository 'Packman Repository' cache ...........................[done]
Retrieving repository 'repo-non-oss (15.6)' metadata ....................[error]
Repository 'repo-non-oss (15.6)' is invalid.
[openSUSE:repo-non-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/non-oss] Valid metadata not found at specified URL
History:
 - [openSUSE:repo-non-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/non-oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'repo-non-oss (15.6)' because of the above error.
Repository 'repo-openh264 (15.6)' is up to date.                                
Retrieving repository 'repo-oss (15.6)' metadata ........................[error]
Repository 'repo-oss (15.6)' is invalid.
[openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/oss] Valid metadata not found at specified URL
History:
 - [openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'repo-oss (15.6)' because of the above error.
Retrieving repository 'update-backports (15.6)' metadata ................[error]
Repository 'update-backports (15.6)' is invalid.
[openSUSE:update-backports|http://cdn.opensuse.org/update/leap15.6/backports] Valid metadata not found at specified URL
History:
 - [openSUSE:update-backports|http://cdn.opensuse.org/update/leap15.6/backports] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'update-backports (15.6)' because of the above error.
Retrieving repository 'update-non-oss (15.6)' metadata ..................[error]
Repository 'update-non-oss (15.6)' is invalid.
[openSUSE:update-non-oss|http://cdn.opensuse.org/update/leap15.6/non-oss] Valid metadata not found at specified URL
History:
 - [openSUSE:update-non-oss|http://cdn.opensuse.org/update/leap15.6/non-oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'update-non-oss (15.6)' because of the above error.
Retrieving repository 'update-oss (15.6)' metadata ......................[error]
Repository 'update-oss (15.6)' is invalid.
[openSUSE:update-oss|http://cdn.opensuse.org/update/leap15.6/oss] Valid metadata not found at specified URL
History:
 - [openSUSE:update-oss|http://cdn.opensuse.org/update/leap15.6/oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'update-oss (15.6)' because of the above error.
Retrieving repository 'update-sle (15.6)' metadata ......................[error]
Repository 'update-sle (15.6)' is invalid.
[openSUSE:update-sle|http://cdn.opensuse.org/update/leap15.6/sle] Valid metadata not found at specified URL
History:
 - [openSUSE:update-sle|http://cdn.opensuse.org/update/leap15.6/sle] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'update-sle (15.6)' because of the above error.
Repository 'Update repository of openSUSE Backports' is up to date.             
Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up
to date.
                                                                                
Repository 'repositories/Kernel:/stable:/Backport/standard/x86_64/' is up to
date.
                                                                                
Some of the repositories have not been refreshed because of an error.

macpro02:~> sudo zypper dup -l
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Retrieving repository 'repo-non-free (15.6)' metadata ...................[error]
Repository 'repo-non-free (15.6)' is invalid.
[NVIDIA:repo-non-free|https://download.nvidia.com/opensuse/leap15.6] Valid metadata not found at specified URL
History:
 - [NVIDIA:repo-non-free|https://download.nvidia.com/opensuse/leap15.6] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'repo-non-free (15.6)' because of the above error.
Retrieving repository 'repo-non-oss (15.6)' metadata ....................[error]
Repository 'repo-non-oss (15.6)' is invalid.
[openSUSE:repo-non-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/non-oss] Valid metadata not found at specified URL
History:
 - [openSUSE:repo-non-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/non-oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'repo-non-oss (15.6)' because of the above error.
Retrieving repository 'repo-oss (15.6)' metadata ........................[error]
Repository 'repo-oss (15.6)' is invalid.
[openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/oss] Valid metadata not found at specified URL
History:
 - [openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap15.6/repo/oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'repo-oss (15.6)' because of the above error.
Retrieving repository 'update-backports (15.6)' metadata ................[error]
Repository 'update-backports (15.6)' is invalid.
[openSUSE:update-backports|http://cdn.opensuse.org/update/leap15.6/backports] Valid metadata not found at specified URL
History:
 - [openSUSE:update-backports|http://cdn.opensuse.org/update/leap15.6/backports] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-backports (15.6)' because of the above error.
Retrieving repository 'update-non-oss (15.6)' metadata ..................[error]
Repository 'update-non-oss (15.6)' is invalid.
[openSUSE:update-non-oss|http://cdn.opensuse.org/update/leap15.6/non-oss] Valid metadata not found at specified URL
History:
 - [openSUSE:update-non-oss|http://cdn.opensuse.org/update/leap15.6/non-oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-non-oss (15.6)' because of the above error.
Retrieving repository 'update-oss (15.6)' metadata ......................[error]
Repository 'update-oss (15.6)' is invalid.
[openSUSE:update-oss|http://cdn.opensuse.org/update/leap15.6/oss] Valid metadata not found at specified URL
History:
 - [openSUSE:update-oss|http://cdn.opensuse.org/update/leap15.6/oss] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-oss (15.6)' because of the above error.
Retrieving repository 'update-sle (15.6)' metadata ......................[error]
Repository 'update-sle (15.6)' is invalid.
[openSUSE:update-sle|http://cdn.opensuse.org/update/leap15.6/sle] Valid metadata not found at specified URL
History:
 - [openSUSE:update-sle|http://cdn.opensuse.org/update/leap15.6/sle] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-sle (15.6)' because of the above error.
Some of the repositories have not been refreshed because of an error.
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...
29 Problems:
Problem: 1: problem with the installed libass9-0.14.0-150000.3.13.1.x86_64
Problem: 2: problem with the installed libvdpau_nouveau-23.3.4-150600.81.3.x86_64
Problem: 3: problem with the installed Mesa-libEGL1-23.3.4-150600.81.2.x86_64
Problem: 4: problem with the installed libavresample4_0-4.4-150600.10.1.x86_64
Problem: 5: problem with the installed pipewire-tools-1.0.4-150600.1.14.x86_64
Problem: 6: problem with the installed libpostproc55_9-4.4-150600.10.1.x86_64
Problem: 7: problem with the installed libswscale5_9-4.4-150600.10.1.x86_64
Problem: 8: problem with the installed libavcodec58_134-4.4-150600.10.1.x86_64
Problem: 9: problem with the installed pipewire-1.0.4-150600.1.14.x86_64
Problem: 10: problem with the installed pipewire-spa-tools-1.0.4-150600.1.14.x86_64
Problem: 11: problem with the installed libavutil56_70-4.4-150600.10.1.x86_64
Problem: 12: problem with the installed libavformat58_76-4.4-150600.10.1.x86_64
Problem: 13: problem with the installed Mesa-23.3.4-150600.81.2.x86_64
Problem: 14: problem with the installed Mesa-libva-23.3.4-150600.81.3.x86_64
Problem: 15: problem with the installed Mesa-libGL1-23.3.4-150600.81.2.x86_64
Problem: 16: problem with the installed Mesa-dri-23.3.4-150600.81.3.x86_64
Problem: 17: problem with the installed libgbm1-23.3.4-150600.81.2.x86_64
Problem: 18: problem with the installed vlc-codec-gstreamer-3.0.20-bp156.1.10.x86_64
Problem: 19: problem with the installed Mesa-gallium-23.3.4-150600.81.3.x86_64
Problem: 20: problem with the installed libswresample3_9-4.4-150600.10.1.x86_64
Problem: 21: problem with the installed libpipewire-0_3-0-1.0.4-150600.1.14.x86_64
Problem: 22: problem with the installed Mesa-libglapi0-23.3.4-150600.81.2.x86_64
Problem: 23: problem with the installed pipewire-spa-plugins-0_2-1.0.4-150600.1.14.x86_64
Problem: 24: problem with the installed pipewire-modules-0_3-1.0.4-150600.1.14.x86_64
Problem: 25: problem with the installed libavfilter7_110-4.4-150600.10.1.x86_64
Problem: 26: problem with the installed pipewire-lang-1.0.4-150600.1.14.noarch
Problem: 27: problem with the installed dwarves-1.25-150600.1.3.x86_64
Problem: 28: problem with the installed kernel-default-6.4.0-150600.17.2.x86_64
Problem: 29: problem with the installed libdwarves1-1.25-150600.1.3.x86_64

Problem: 1: problem with the installed libass9-0.14.0-150000.3.13.1.x86_64
 Solution 1: install libass9-0.17.1-150600.2.pm.1.x86_64 from vendor http://packman.links2linux.de
  replacing libass9-0.14.0-150000.3.13.1.x86_64 from vendor SUSE LLC <https://www.suse.com/>
 Solution 2: keep obsolete libass9-0.14.0-150000.3.13.1.x86_64
5

All your repository URLs are wrong. This can’t work. No clue how they got broken in this way…you are missing a slash between leap and 15.6 in all URLs…
Wrong example:

https://download.nvidia.com/opensuse/leap15.6

Correct example:

https://download.nvidia.com/opensuse/leap/15.6

Correct all your repo URLs and the upgrade issues are gone…

But this tip was already given in the terminal output:

Please check if the URIs defined for this repository are pointing to a valid repository.

6

Have had ZERO issues with Leap 15.6 zypper dups for a long time - last dup was 3 browser updates. Check the repo URLs.

7

Alrighty . . . thanks for that reply . . . . Indeed, “no idea” how that happened, I didn’t edit them . . . other than unchecking nvidia in YaSt GUI repos . . . .

Out of time on it for today . . . I’ll post back on it when I get it adjusted.

8

It is reported and several ways for fixes mentioned…
https://bugzilla.opensuse.org/show_bug.cgi?id=1224185

Also mentioned on the factory mailing list…

9

I went through the YaSt GUI repos and added the / in front of the {releasever} data and for each line YaSt went through the “refresh” . . . then I went to terminal and ran the zypper and got the same errors on the URL’s as before??

I logged out and back in and again got the same problem . . . 29 questions to answer, etc.

Do I have to reboot to get the zypper to get the upgraded repos??

Or, how would I edit the repos in say nano?? Like in Lubuntu I can “sudo nano /etc/apt/sources.list” . . . would I just change “apt” to “zypper”???

10

Unlike Debian and derivatives, where standard repos are all enumerated via one line in /etc/apt/sources.list, with others in /etc/apt/sources.list.d/, each openSUSE repo is configured by one file in /etc/zypp/repos.d/. Edits to any openSUSE repo file take effect immediately following the later of saving of the edit(s), or the completion of any zypper command initiated before saving an edit.

Here are the most important parts of my 15.6 repos:

/etc/zypp/repos.d/ # grep baseu *.repo
NonOSS.repo:baseurl=http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/
OSS.repo:baseurl=http://download.opensuse.org/distribution/leap/15.6/repo/oss/
PackmanE.repo:baseurl=http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.6/Essentials
Update.repo:baseurl=http://download.opensuse.org/update/leap/15.6/oss/
UpdateBP.repo:baseurl=http://download.opensuse.org/update/leap/15.6/backports/
UpdateNonOSS.repo:baseurl=http://download.opensuse.org/update/leap/15.6/non-oss/
UpdateSLE.repo:baseurl=http://download.opensuse.org/update/leap/15.6/sle/
openh264.repo:baseurl=http://codecs.opensuse.org/openh264/openSUSE_Leap/
#
1 Like
11

Mr M:

Thanks kindly for the details, I will try to check into it when I get a free moment. I’ve shut the desktop down for the day. It’s just a continuation of the “oddness” . . . like, the why of the repos changing their configuration, “on their own,” with only running zypper . . . when somehow I had a running Leap 15.6 system for months, and then not . . . and then, I have also edited the repos in YaSt previously in either my TW, now defunct Slow Roll, or in a number of Leap iterations, and the edits “worked” . . . easily. Today, seemingly it did not, even on reboot.

So, I don’t know if this is similar to what happened with my Slow Roll install, where for some reason the system just “imploded” on itself, and was gone. OR, if I can figure out how to nano into the repos.d directory I can try to edit again, and that time it will work??

Back atcha when I’ve found the time to play with it.

12

I’m not a fan of surprises. When repos began appearing that I didn’t create, I did several things:

1-zypper rm openSUSE-repo*

2-zypper al openSUSE-repo*

3-I altered some of my zypper scriptlets, such the following used as a prequel to zypper up & zypper dup:

# cat /usr/local/bin/zypstart
#!/bin/bash
# /usr/local/zypstart
[ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null
zypper -v in --download-in-advance rpm zypper libzypp libsolv-tools openSUSE-release coreutils filesystem
[ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null

None of my repos’ names begin with “repo”, so when any appear with such a name, it’s disposed of as a matter of routine, usually without me knowing such ever occurred.

1 Like
13

That is very advanced . . . not sure if that is something that I should do . . . ?? This problem of “mutating” repos is somewhat new??

Too many problems going on right now to dig into my Leap system . . . .

14

So far nothing has worked to fix the repos . . . .

Posted on the bug report: `(In reply to Christian Goll from comment #1)

As work around, one can delete the package openSUSE-repos-Leap

I tried to edit the repos in YaSt and then this morning I tried to remove this package . . . .

Running zypper still brings 29 questions to answer before the zyppering can take place.`

Unfortunately don’t have time to dig into Mr Mazdas suggestion . . . .

And, the repeat of the “nvidia” problem isn’t letting system revive from suspend. . . . mash up in action . . . .

15

What “digging”? Time to run #1 & #2 combined would be about 6 seconds. For you, #3 probably isn’t applicable.

1 Like
16

6 seconds?? I might have time for 6 seconds, but I type slowly.

I did check and see your #1 & #2 suggested commands . . . which yes, should be quick to run. Since I did already try a similar “remove package” suggested in the bug report . . . it removed two packages, including an “nvidia” dependency . . . . But, that didn’t clear the 29 questions problem.

My life has been like a 3D Chess game lately . . . moves coming in from all asymmetricals . . . .

But, Leap seems to be revisiting problems, like with this wiping nouveau and so forth . . . . Won’t be today but I’ll ppost back on it . . . .

17

Couldn’t seem to remove the /etc/modprobe.d/nvidia-default-conf file which contains the words “blacklist nouveau” in it . . . as root. “Move to trash” is greyed out. I can see it in Thunar in the GUI directory . . . but zypper says “file not found”??

Running zypper dup -l still shows the 29 questions to answer . . . .

# zypper rm /etc/modprobe.d/nvidia-default.conf
Reading installed packages...
'/etc/modprobe.d/nvidia-default.conf' not found in package names. Trying capabilities.
No provider of '/etc/modprobe.d/nvidia-default.conf' found.
Resolving package dependencies...
Nothing to do.

no # zypper rm openSUSE-repo*
Reading installed packages...
'openSUSE-repo*' not found in package names. Trying capabilities.
No provider of 'openSUSE-repo*' found.
Resolving package dependencies...
Nothing to do.

no # zypper al openSUSE-repo*
Specified lock has been successfully added.


# ls /etc/zypp/repos.d/
ftp.gwdg.de-openSUSE_Leap_$releasever.repo  repo-oss.repo.rpmsave
repo-backports-debug-update.repo            repositoriesKernel:stable:Backportstandardx86_64.repo
repo-backports-debug-update.repo_1          repo-sle-debug-update.repo
repo-backports-debug-update.repo.rpmsave    repo-sle-debug-update.repo_1
repo-backports-update.repo                  repo-sle-debug-update.repo.rpmsave
repo-backports-update.repo_1                repo-sle-update.repo
repo-backports-update.repo.rpmsave          repo-sle-update.repo_1
repo-debug-non-oss.repo.rpmsave             repo-sle-update.repo.rpmsave
repo-debug.repo.rpmsave                     repo-source.repo.rpmsave
repo-debug-update-non-oss.repo.rpmsave      repo-update-non-oss.repo.rpmsave
repo-debug-update.repo.rpmsave              repo-update.repo.rpmsave
repo-non-oss.repo.rpmsave
18

Unfortunately you are mixing to much topics…

But lets start. You sucessfully added a package lock for openSUSE-repo*. Thats good.
Your last output shows that you have no longer repos setup. That is also correct. You need to activate them again as described here:

As root:

# ls -la /etc/zypp/repos.d/*.rpmsave
# for file in /etc/zypp/repos.d/*.rpmsave; do echo mv $file `echo $file | sed -s "s/\.rpmsave//"`; done
# zypper ref

After that you can show again the output of zypper lr -d and we can help you to do some minor cleanup…

1 Like
19

Thanks for the assist on it. I “bulk” pasted the commands, so I don’t know if it “worked” that way??? I did manage to figure out how to rm the nvidia-default-conf file . . . but that still didn’t bring “nouveau” back into lsmod.

Does this look like it went according to plan?

# zypper lr -d
# | Alias                                            | Name                                                                                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                          | Service
--+--------------------------------------------------+---------------------------------------------------------------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------------+--------
1 | ftp.gwdg.de-openSUSE_Leap_$releasever            | Packman Repository                                                                          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.6/           | 
2 | repo-backports-debug-update                      | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No      | ----      | ----    |   99     | N/A    | http://download.opensuse.org/update/leap/15.6/backports_debug/               | 
3 | repo-backports-update                            | Update repository of openSUSE Backports                                                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.6/backports/                     | 
4 | repo-sle-debug-update                            | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | No      | ----      | ----    |   99     | N/A    | http://download.opensuse.org/debug/update/leap/15.6/sle/                     | 
5 | repo-sle-update                                  | Update repository with updates from SUSE Linux Enterprise 15                                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.6/sle/                           | 
6 | repositoriesKernel:stable:Backportstandardx86_64 | repositories/Kernel:/stable:/Backport/standard/x86_64/                                      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ |

Seems like it’s the same?? I ran the commands again one at a time . . . not sure if that worked either??

# zypper lr -d
# | Alias                                            | Name                                                                                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                          | Service
--+--------------------------------------------------+---------------------------------------------------------------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------------+--------
1 | ftp.gwdg.de-openSUSE_Leap_$releasever            | Packman Repository                                                                          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.6/           | 
2 | repo-backports-debug-update                      | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No      | ----      | ----    |   99     | N/A    | http://download.opensuse.org/update/leap/15.6/backports_debug/               | 
3 | repo-backports-update                            | Update repository of openSUSE Backports                                                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.6/backports/                     | 
4 | repo-sle-debug-update                            | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | No      | ----      | ----    |   99     | N/A    | http://download.opensuse.org/debug/update/leap/15.6/sle/                     | 
5 | repo-sle-update                                  | Update repository with updates from SUSE Linux Enterprise 15                                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.6/sle/                           | 
6 | repositoriesKernel:stable:Backportstandardx86_64 | repositories/Kernel:/stable:/Backport/standard/x86_64/                                      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ |
20

It did not work. So lets add the important repos one by one as root again (leaving out the debug and source repos):

su -
cd /etc/zypp/repos.d/
mv repo-oss.repo.rpmsave repo-oss.repo
mv repo-non-oss.repo.rpmsave epo-non-oss.repo
mv repo-update.repo.rpmsave repo-update.repo
mv repo-update-non-oss.repo.rpmsave repo-update-non-oss.repo

zypper ref

zypper dup
1 Like