At one point I had the vagrant package installed from the the https://build.opensuse.org/project/show/Virtualization repository and had some problems with it and uninstalled the package. After that I have disabled and removed the repository and then manually installed the vagrant package from their website and everything went smooth until I’ve decided to run zypper dup. At witch point zypper decided that the vagrant package should be removed, and I can’t seem to convince zypper to keep that package. Event after I’ve re-added the repository and set keeppackages=1 and the removed the repository again.
I’ve also manually deleted the /var/cache/zypp and /var/cache/zypper directories and ran zypper refresh -fdb.
Any Ideas on what I can do to convince zypper that I’ve installed the package from a different source and that it should not be removed on dist-upgrade?
# zypper --version
zypper 1.13.14
# zypper info vagrant
Loading repository data...
Reading installed packages...
Information for package vagrant:
--------------------------------
Repository : @System
Name : vagrant
Version : 1:1.9.3-1
Arch : x86_64
Vendor : root@localhost.localdomain
Installed Size : 200.7 MiB
Installed : Yes
Status : up-to-date
Summary : Vagrant is a tool for building and distributing development environments.
Description :
Vagrant is a tool for building and distributing development environments.
Why do you want to run a zypper dup on a running LEAP42.2?
zypper dup is, as you noted, a distribution update. But you are NOT updating to a new distribution. zypper dup can break many things (e.g. when you have one the vendor switch to Packman in order to get full multimedia support, you may partly undo this and thus break your multimedia support).
For getting security and recommended patches from the Update repos belonging to your version of the distribution YaST > Software > Online Update or
zypper patch
.
For getting newer versions from other repos (including Packman)
zypper dup
. But i prefer to do that on a per repository base.
You could try yast. Get the application up via a search. If you installed via an rpm it should show it. Then click package - all in this list and lock.
This may do something different to locking it in zypper which I assume can be done. If not you’ve found a bug.
:’(It should be possible to get the solver info up in yast as well but currently it states that something is missing and a search for it via provides says it’s already installed. cnf can’t find it.