Sudo Zypper Dup Fails

English Install/Boot/Login
1

So, I haven’t upgraded/updated my system in 1-2 months. Forgot about it.

Now, I tried using KDE Discover (as I usually do) to install updates - fail.

Tried using sudo zypper dup, I am getting a couple of problems that I can’t solve. I tried ignoring, removing, replacing, keeping the obsolete ones - nothing works.

image
image1126×433 90.2 KB

Installation ultimately fails no matter what options I choose, and this is what I get at the very end (will add the picture in the comments, since I can only add one picture to the post).

Here are my repositories, because I heard this might be relevant (again, will add them in the comments).

Just assume I know nothing about Tumbleweed or Linux, in general. So I don’t know to disable repositories or whatnot.

I have also used a combo of zypper up, dup, and KDE Discover throughout the lifespan of this system (about a year) because I couldn’t care about doing enough research to find out zypper dup is actually the healthier, intended way to upgrade/update the system.

I just assumed that, since the Discover GUI was there, it was there for a reason. And I’d rather not use the terminal if I can help it, I guess.

Would really appreciate if someone helped with untangling this frustrating mess I found myself in. I just want a stable, working system, and to keep it up-to-date.

Thanks in advance!

2

This is what I get at the very end no matter what I try.

image

3

And these are my repositories.

image
image1600×589 98 KB

4

libxvidcore4 is no longer available on packman, so you need to switch the vendor of this package back to openSUSE.

For dnf there is a bugreport.

For the bottles problem: You are missing the auto refresh flag for this home repository. YaST->Software Repositories-> mark the home repository (repo #6) and enable auto refresh → apply

Please don’t use screenshots! Copy the terminal output and paste it here in the preformatted text tags </>

1 Like
5

Wait, that actually worked :open_mouth:

As for the dnf, I suppose I should wait until they fix that bug and then try again, if it still pops up in a future dup?

Also, immense gratitude for the speedy answer. Didn’t think I’d solve it this quick (and it was such a silly problem).

And sorry for the screenshots, will deffo send the actual text in the thread going forward.

6

Actually, did another dup and I could install the dnf one, too. So all issues solved :X

7

The usual problem that persists for a long time, Some repositories for one reason or another timeout, and if you are not present the installation aborts or returns a lot of dependencies, this problem exists only for the Repositories related to Opensuse, I have Manjaro and it never happens. Some people here do not like to be told, but it is the reality.

8

Don’t compare apples and pears.

1 Like
9

@enziosavio Standard repositories (oss, non-oss, updates, codecs etc), maybe if there are some infrastructure issues going on but that is few and far between.

Throw $HOME, $DEVEL, third party repos into the mix, that’s all best effort even if they still exist, users are on their own with that…

1 Like
10

@Malcolmlewis I have had Opensuse since before 2000, when I still used the 46k telephone line, and to open a Google page you had time to go to the bathroom… when I started an update I left the computer on for 24 hours for maybe a week before it finished, and Zypper never stopped. Now it is almost impossible not to follow the update, maybe it takes 20 minutes for 5000 rpm and maybe it takes days because it keeps going into timeout and if you don’t follow it after a while it aborts the update. I am used to it by now I use a VPN or if it really doesn’t work I installed an extension that can kill Zypper or Yast with a click, so as not to waste time. The problem to be solved is in Zypper which doesn’t work properly; something must be done to neutralize this timeout. My idea is that zypper takes too long to wait for the repository to download and ask you what you want to do (cancel, abort, try again) if you give retry it often restarts and goes. My idea is that it shouldn’t ask, if I launched the update it’s because I want to do it, so it should retry and retry and retry until it’s finished, I tried to modify the configuration file in /etc/zypper… but I had no results. Taking into account that I use 4 repositories

enziosavio@Matusalem:~> zypper lr

# | Alias                      | Name              | Enabled | GPG Check | Refresh
--+----------------------------+-------------------+---------+-----------+--------
1 | google-chrome              | google-chrome     | No      | ----      | ----
2 | openSUSE:repo-non-oss      | repo-non-oss      | Sì      | (r ) Sì   | Sì
3 | openSUSE:repo-oss          | repo-oss          | Sì      | (r ) Sì   | Sì
4 | openSUSE:update-tumbleweed | update-tumbleweed | Sì      | (r ) Sì   | Sì
5 | packman                    | packman           | Sì      | (r ) Sì   | Sì
11

@enziosavio not using preload? env ZYPP_PCK_PRELOAD=1 zypper -vvv dup new installs use preload by default…

12

No teach me how to do it, I’ll try

13

@enziosavio run the command indicated and see how that goes. See https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/

2 Likes
14

Try a different mirror

15

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.