How to evaluate the damaged of doing "zypper up" a few times?

Hello everybody,

After installing Tumbleweed, i used zypper up sometimes, instead of zypper dup. Now i’m worried if that can cause any problems in my machine in the future snapshots. There is anyway to evaluate if if did any damage by running this command, so i can reinstall before anything important is corrupted in my installation.

Hi, welcome.

You might think about providing us with a little more info ( Desktop, graphics card ), but the title already has the culprit in it, if you post here because of issues:

On Tumbleweed, never use ‘zypper up’, use ‘zypper dup’ !!!

So, before you start explaining, first run the appropriate command, reboot and be so kind to let us know the results.

Now i am aware that i must use “zypper dup”.

I have a Nvidia 920M with optimus support, with X11:Bumblebee repository enabled and using the proprietary driver.

I installed tumbleweed 3 days ago and updated with “zypper up” a few times before knowing that i could not do it.

Now i want to know if there is anyway to evaluate if my system is damaged by using “zypper up” command instead of “zypper dup”

OK, that’s something we can reply to. Why not ‘up’ instead of ‘dup’?

To understand, you need to know how Tw is built and released. The ‘updates’ are not really updates of just some packages that have a newer version, like in ‘up’, the whole Tw distro is released over and over again, after openQA testing, so downgrades, architecture changes etc may be included. ‘dup’ will precess these, ‘up’ won’t.
If you want to see proof of this, take a look at /etc/os-release and https://download.opensuse.org/tumbleweed/iso
Evaluating what would be damaged? Run ‘dup’ after ‘up’ and see which packages ‘dup’ wants to change. Those are not the tested distro ones and might fail some day.

So if i have no errors when running “zypper dup” my system is not corrupted?

I remember running “zypper up” after the os installation, when the updated ended a post install message recommended me to run “zypper dup”

So the latest snapshot is installed. But after some research i was worried that my unaware use of zypper broke anything on my installation, i created this topic

because i could not find a way to check if my system has any inconsistency compared to the latest available snapshot.

Thank you for your help

Run ‘zypper dup’ and report back if you encounter package conflicts or dependency issues you’re not certain about.

Yes, you may find you get a ‘clean’ upgrade experience without any issues to resolve.

There is no package conflict or dependency issue, just the usual lock on nouveau package.

So if there is nothing wrong in ‘zypper dup’ , my machine is fine?

I moved from Arch, i understood how tumbleweed rolling release model works after running ‘zypper up’ a couple of times

The following can be helpful with that (and —dry-run option useful for testing too)…

zypper ve

Ok, thanks for your time and help!

Yes, likely all is ok. For the most part zypper is good at resolving most inconsistencies, provided the appropriate repos configured.

It is probably fine.

However: I suggest Yast –> Software Manager

Click “View” near the top left, and select “Package Groups”.

Scroll down to the line for “Orphaned packages”. If there are any orphaned packages, consider removing them.

An orphaned package is one that is not in any enabled repo. There might be some that are orphaned for reasons that you know. But others might be left over because you used “up” rather than “dup” at some time.

You might get a conflict for some removals. Usually the conflict is with other orphaned packages. But you may have to sort that out, or just keep the ones that can’t be removed because of a conflict.

Zypper up hurts nothing, creates no “damage”. It simply leaves the upgrade incomplete. I do it nearly always, but I follow up with dup. That way the minor updates are distinguishable by being grouped separately from more significant upgrades when asked for confirmation. The latter I’m more likely to reject by aborting and locking. I might not notice any I’d wish to reject with minors and majors all mixed together by only doing dup.

That is correct. Doing zypper dup after you (may heve corruptes somtehing by) doing zypper up, it is now repaired.

As long as the system boots, and zypper runs, nothing should be broken. At worst, some packages simply need to be updated.