On 07/13/2017 08:05 PM, Christian Boltz wrote:
Is there a way to force the installation of foo-2.0 and afterwards foo-3.0? I can only think of having foo-3.0 on a different repo and adding this repo after installing foo-2.0, but sounds a bit hacky.
The problem I am trying to address is the case that I have multiple machines with foo-1.0 and need to go to foo-2.0 and then to foo-3.0 because the API or file format may be only compatible between foo-1.0 and foo-2.0, foo-2.0 and foo-3.0, but not between foo-1.0 and foo-3.0.
This sounds like it should be a "typical" problem on a rolling release as Tumbleweed ... right? Not really - jumping from 1.0 to 2.0 to 3.0 within a few days sounds unlikely in Tumbleweed, so if you update often enough, this shouldn't be a problem.
That is what we did in the past. But still you can have the case of someone installing an iso and running the updates.
Any ideas/experience? Does this have to happen as part of "zypper dup"?
zypper in foo-2.0 would be the easiest solution. (Run zypper al foo if you want to run zypper dup afterwards.)
If you really need to enforce a specific version during zypper dup, I'd create and install a dummy package with Requires: foo = 2.0 before running zypper dup.
Yeah but then you need to update this new package to update the foo package, and you have the same problem. Running "zypper install foo-2.0 && zypper al foo" sounds like a good idea but unfortunately we cannot make sure the user won't run "zypper dup" before. Thanks Christian for your suggestions Any other ideas :) ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org