On Wed, Jun 14, 2023 at 10:55:16PM +0200, Christian Boltz wrote:
Hello,
Am Mittwoch, 14. Juni 2023, 21:30:18 CEST schrieb Richard Brown:
On 2023-06-14 21:21, Felix Miata wrote:
<https://bugzilla.opensuse.org/show_bug.cgi?id=854169> 2013-12-06
You do understand what that bug shows right?
Yes, I do - see below.
10 years ago I screwed up a test by doing a zypper up instead of a dup
The solution was to use zypper dup
I was wrong to do an up 10 years ago and anyone is wrong to do it today.
Just because you did something wrong some years ago doesn't mean that *everybody* who uses zypper up is doing it wrong.
Sure, "dup" is the recommended way, and correct in 99% of the cases.
That leaves 1% of special cases where "up" makes sense. For example, if someone really wants to update a specific package without upgrading the whole system - which is a very valid approach if you want to check if this package fixes a specific issue. In this case, you really don't want 142 more packages upgraded that might randomly influence the result.
So you probably wanted zypper in <package> This has nothing to do with dup/up, these are for upgrading *all* packages. The difference between up/dup is that up assumes package version always increases, and can take some shortcuts, and dup does not. Because package version does not always increaso on Tumbleweed taking the shortcut can get you into a bad place. Thanks Michal