On Sun, 2020-07-05 at 06:56 -0400, ksusup(a)trixtar.org wrote:
From 'man zypper':
Whether to allow downgrading installed resolvables.
To me '--no-allow-downgrade' means that a downgrade is NOT to be
considered an option
This is correct, but...
But when I issue the following:
zypper dup --no-allow-downgrade
I get a couple of dozen 'problems' like:
Problem: problem with installed package libply-boot-client5-
with a list of possible solutions:
Solution 1: downgrade of libply-boot-client5-
0.9.5+git20200418+14e91cc-1.1.x86_64 to libply-boot-client5-
Solution 2: keep obsolete libply-boot-client5-
...This specific package (rpm pkgs from source package plymouth) was
downgraded (i.e. reverted to the lower version) in the official TW
repos after an issue was found in an updated version that was -- at
least immediately -- difficult to fix.
I'm a little confused...
First of all how does a downgrade come up at all given the initial
command switch? Seems to me that ignoring any repo package that
requires a downgrade would be the zypper behavior. In the above case
it would mean an automatic 'keeping' of the installed version.
Second, how does a newer version become obsolete in favor of an older
one? Which version is presently on the repo, was it backleveled to
the 'downgrade' version??
When a package is downgraded in the repository, the updated version is
cleared off. This isn't surprising in itself, even when newer versions
of packages are published, the older versions are cleaned from the
repository. However, it is critical for downgrades to be applied -- and
therefore mitigate problems with the newer installed version --
automatically when you do a `sudo zypper dup` that the newer versions
are not available in the repo too.
Now, when you ask zypper to `no-allow-downgrade`, it forbids version
downgrades but doesn't find any source (any repository) which provides
either the same version (compared to installed) or a newer one, so it
asks you what you do (either keep the installed version or allow a
downgrade despite `no-allow-downgrade`). Note that "installed in
system" is not a repository in itself.
To work around this, you can lock certain packages temporarily or
download working packages into a local dir and add it as a zypper
`sudo zypper addrepo /path/to/local/dir localpkgs`.
Or better yet, on TW just do not use `no-allow-downgrade` and let the
zypper take care of version upgrades and downgrades as best it can.
Hope that helps.
Sun 5 Jul 16:22:17 CEST 2020
Sent from openSUSE Tumbleweed on my laptop.
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org