Operation Manual
Choose the repository from which to update as described in Section 3.2.1,
“Views for Searching Packages or Patterns” (page 64) .
2a
2b
On the right hand side of the window, click Switch system packages to the
versions in this repository. This explicitly allows YaST to change the package
vendor when replacing the packages.
As soon as you proceed with Accept, all installed packages will be replaced
by packages deriving from this repository, if available. This may lead to
changes in vendor and architecture and even to downgrading some packages.
2c
To refrain from this, click Cancel switching system packages to the versions
in this repository. Note that you can only cancel this until you press the Accept
button.
3
Before applying your changes, you can review or modify them by clicking View
> Installation Summary. By default, all packages that will change status, are
listed.
4
If all options are set according to your wishes, conrm your changes with Accept
to start the mass update.
3.2.4 Checking Software Dependencies
Most packages are dependent on other packages. If a package, for example, uses a
shared library, it is dependent on the package providing this library. On the other hand
some packages cannot coexist with each other, causing a conict (for example, you
can only install one mail transfer agent: sendmail or postx). When installing or remov-
ing software, the Software Manager makes sure no dependencies or conicts remain
unsolved to ensure system integrity.
In case there exists only one solution to resolve a dependency or a conict, it is resolved
automatically. Multiple solutions always cause a conict which needs to be resolved
manually. If solving a conict involves a vendor or architecture change, it also needs
to be solved manually. When clicking Accept to apply any changes in the Software
Manager, you get an overview of all actions triggered by the automatic resolver which
you need to conrm.
68 Reference