* On 2/22/23 15:16, Carlos E. R. wrote:
The thing that "zypper dup" does is that what you get has to be the same version as the repo has, no matter if it is upgrade or downgrade. Thank you for bringing that up.
Unfortunately, Tumbleweed rarely contains package downgrades. While I frown upon that whenever I see it happening, they happen nonetheless (mostly to fix issues brought in by a former upgrade, I presume). Package downgrades as such can be valid thing, and there are good reasons for doing them. For instance, sometimes, the versioning scheme of a package changes, and while that syntactically (i.e., vercmp) would a downgrade, it can still be an upgrade (e.g., the upstream developer might have used a date-based versioning scheme in the past and then switched to semantic versioning, resetting the previous version to a much lower number). The proper way to handle such situations is to bump the epoch and thus force a proper syntactic version upgrade, but Tumbleweed seems to forgo this approach at times. Probably because users are expected to dist-upgrade anyway... I don't know how YaST handles this situation, but my gut feeling tells me that it probably skips downgrades unless they are explicitly forced. Yet another way to break (parts of) the system. Mihai