Chapter 9. Installing or Removing Software

Contents

9.1. Definition of Terms
9.2. Using the Qt Interface
9.3. Managing Software Repositories and Services
9.4. Keeping the System Up-to-date

Abstract

In YaST's software management tool search for software components you want to add or remove. YaST resolves all dependencies for you. Add additional software repositories to your setup to install packages not shipped with the installation media and let YaST manage them. Keep your system up-to-date by managing software updates with the update applet.

Change the software collection of your system using YaST. This YaST module is available in two toolkit flavors: Qt and ncurses; the Qt flavor is described here.

9.1. Definition of Terms

Repository

A local or remote directory containing packages, plus additional information about these packages (package meta-data).

(Repository) Alias

A short name for a repository used by various zypper commands. The alias can be chosen by the user when adding a repository and must be unique.

Product

Represents a whole product, for example SUSE Linux Enterprise Server.

Pattern

A pattern is an installable list of packages needed for a special purpose. Examples are Base System, providing the openSUSE basic system, or GNOME Base System, containing all packages needed to run the GNOME Desktop environment.

Package

A package is a compressed file in rpm format that contains the files for a particular program.

Patch

A patch consists of one or more packages—either full packages or patchrpm or deltarpm packages— and may also introduce dependencies to packages that are not installed yet.

Resolvable

An generic term for product, pattern, package or patch. The most commonly used type of resolvable is a package or a patch.

patchrpm

A patchrpm consists only of files that have been updated since it was first released for SUSE Linux Enterprise Server 11 SP1. Its download size is usually considerably smaller than the size of a package.

deltarpm

A deltarpm consists only of the binary diff between two defined versions of a package, and therefore has the smallest download size. Before being installed, the rpm package must be rebuilt on the local machine.

9.2. Using the Qt Interface

The YaST Qt interface is started by default when using the desktops KDE, icewm, and others. It is also used when invoking YaST from a remote terminal. Start the software manager from the YaST Control Center by choosing Software+Software Manager

9.2.1. Searching Packages or Patterns

The YaST software manager can install packages or patterns from all currently enabled repositories. It offers different views and filters to make it easier to find the software you are searching for. Change the view by clicking View and selecting a view listed below. The selected view opens in a new tab.

Search

The package search interface is the default view of the software manager. Enter a search term and press Enter. Refine your search by specifying where to Search In and changing the Search Mode.

Patterns

Lists all patterns available for installation on your system.

Package Groups

Lists all packages sorted by groups such as Graphics, Programming, or Security.

RPM Groups

Lists all packages sorted by groups and subgroups, for example Productivity+Graphics+Viewers.

Repositories

Filter to list packages by repository. In order to select more than one repository, hold the Ctrl key while clicking on repository names. The pseudo repository @System lists all packages currently installed.

Languages

Filter to list all packages needed to add a new system language.

[Tip]Finding Packages Not Belonging to an Active Repository

To list all packages that do not belong to an active repository, choose View+Repositories+@System and then choose Secondary Filter+Unmaintained Packages. This is useful, for example, if you have deleted a repository and would like to make sure no packages from that repository remain installed.

9.2.2. Installing and Removing Packages or Patterns

  1. Search for packages as described in Section 9.2.1, “Searching Packages or Patterns”.

  2. The packages found are listed in the right pane. To install a package or remove it, right-click it and choose Install or Delete. If the relevant option is not available, check the package status indicated by the symbol in front of the package name—hit Shift+F1 for help.

    [Tip]Applying an Action to All Packages Listed

    To apply an action to all packages listed in the right pane, choose an action from Package+All in This List.

    To install a pattern, right-click the pattern name and choose Install. It is not possible to delete patterns.

  3. If your choice results in a dependency conflict that cannot be automatically solved, you need to manually solve this conflict as described in Section 9.2.3, “Checking Software Dependencies”.

  4. In order to select more packages, repeat the steps mentioned above. Once you are finished click Accept to start the installation.

    [Tip]Reviewing the Package Selection

    YaST maintains a list with all actions that are carried out when starting the installation. To review this list, choose View+Installation Summary. By default, all packages that will change status, are listed. Use the check boxes under Show Packages with Status to filter this list. Hit Shift+F1 for details on the status flags.

    In order to revert the status for a package, right-click it and select Keep if the package was scheduled to be deleted or updated, or Do Not Install if it was scheduled for installation. To abandon all changes and close the Software Manager, click Cancel and Abandon

  5. Certain packages are dependent on other packages, such as shared libraries. YaST automatically resolves these dependencies. On the other hand, some packages cannot co-exist with others on the system. In these cases, a list of packages that have automatically been chosen for installation, update or removal is presented. Click Continue to accept them.

  6. Once all selected packages are installed or removed, the YaST Package Manager automatically terminates.

[Note]Installing Sources

Installing source packages with YaST Software Manager is not possible at the moment. Use the command line tool zypper for this purpose. For more information, see Section “Installing Source Packages” (Chapter 4, Managing Software with Command Line Tools, ↑Administration Guide).

[Tip]Updating Packages

To update all packages from a certain repository, choose the repository as described in Section 9.2.1, “Searching Packages or Patterns” and then click Package+All in This List+Update if Newer Version Available.

To update all installed packages, choose Package+All Packages+Update if Newer Version Available.

Choosing Update Unconditionally instead of Update if Newer Version Available will update all selected packages to the version from the repository with the highest priority, even if this means actually downgrading the package. This option is useful, for example, to ensure that the package selection originates from a certain repository.

9.2.3. 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 (for example, you can only install one mail transfer agent, sendmail or postfix), causing a conflict. When installing or removing software, the Software Manager makes sure no dependencies or conflicts remain unsolved to ensure system integrity.

In case there exists only one solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved manually. If solving a conflict involves a vendor or architecture change, it also needs to be solved manually. When click Accept to start the installation, you get an overview of all actions triggered by the automatic resolver which you need to confirm.

By default, dependencies are automatically checked. A check is performed every time you change a package status (for example, by marking a package for installation or removal). This is generally useful, but can become exhausting when manually resolving a dependency conflict. To disable it, uncheck Dependencies+Autocheck. Manually perform a dependency check with Dependencies+Check Now. A consistency check is always performed when you confirm your selection with Accept.

To review a package's dependencies, right-click it and choose Show Solver Information. A map showing the dependencies opens. Packages that are already installed are displayed in a green frame.

[Note]Manually Solving Package Conflicts

Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens, Cancel the Software Manger, Abandon all your changes and start again.

Figure 9.1. Conflict Management of the Package Manager

Conflict Management of the Package Manager

9.3. Managing Software Repositories and Services

Add additional software repositories to your system to install third-party software. By default, the product repositories such as SUSE Linux Enterprise Server-DVD 11 SP1 and a matching update repository are automatically configured once you have registered your system; for more information about registration, see Section 6.15.1.4, “Novell Customer Center Configuration”. Depending on the initially selected product, a separate language add-on repository with translations, dictionaries, etc. might also be configured.

Here also manage subscriptions to so-called Services. A Service in this context is a Repository Index Service (RIS) that can offer one or more software repositories. Such a Service can be changed dynamically by its administrator or vendor.

[Warning]Trusting External Software Sources

Before adding external software repositories to your list of repositories, make sure this repository can be trusted. SUSE Linux Enterprise Server is not responsible for any potential problems arising from software installed from third-party software repositories.

9.3.1. Adding Software Repositories

To add product repositories, open YaST Control Center and in the Software pane click Software Repositories. Proceed as follows:

  1. Click Add.

  2. Select the repository type. Normally you will want to stick with the default Specify URL.... For add-on CDs or DVDs choose the relevant option. Each repository provides files describing content of the repository. Check Download Repository Description Files to download these files now. If the option is unchecked, YaST will automatically download the files if needed them later. Click Next.

  3. Either provide the necessary data or insert the medium. Confirm with Continue. It will take some time until YaST has downloaded and parsed the metadata of the repository. Once done you can install software from this repository as described in Section 9.2, “Using the Qt Interface”.

9.3.2. Managing Repository Properties

The Configured Software Repositories overview of the Software Repositories lets you change the following repository properties:

Status

The repository status can either be Enabled or Disabled. You can only install packages from repositories that are enabled. To turn a repository off temporarily click Disable. If you want to remove a repository completely, click Delete.

[Tip]

Double-click on a repository name to toggles its status.

Refresh

When refreshing a repository, its content description (package names, versions, etc.) is downloaded to a local cache that is used by YaST. It is sufficient to do this once for static repositories such as CDs or DVDs, whereas repositories whose content changes often should be refreshed frequently. The easiest way to keep a repositorie's cache up-to-date is to choose Automatically Refresh. To do a manual refresh click Refresh.

Priority

The Priority of a repository is a value between 0 and 200, where 0 is the highest priority. If a package is available in more than one repository, then the repository with the highest priority takes precedence. This is useful if you want to give a local repository (for example, a DVD) a higher priority to avoid downloading packages unnecessarily from the Internet, although they have the same or a higher version number.

[Important]Priority vs. Version

The repository with the highest priority takes precedence in any case. Therefore, make sure that the update repository always has the highest priority (20 by default), otherwise you might install an outdated version that will not get updated until the next online update.

Name and URL

To change a repository name or its URL, select it from the list with a single-click and then click Edit.

9.3.3. Managing Repository Keys

To ensure their integrity, software repositories can be signed with the GPG Key of the repository maintainer. Whenever you add a new repository, YaST offers the ability to import its key. Verify it as any other GPG key and make sure it does not change. If you detect a key change, something might be wrong with the repository. Disable the repository as an installation source until you know the cause of the key change.

To manage all imported keys, click GPG Keys... in the Software Repositories module. Select an entry with the mouse to see the key properties. Add, Edit or Delete keys with a click on the respective buttons.

9.4. Keeping the System Up-to-date

Novell offers a continuous stream of software security patches for your product. The updater applet informs you about the availability of patches and lets you easily install them with just a few clicks.

9.4.1. Using the KDE Updater Applet

The updater applet resides in the system tray of your panel depicting the head of the SUSE mascot (Geeko), which changes depending on the availability and relevance of patches and the status of the updater. Whenever the icon changes, a tool tip displaying the current status is shown, too. The applet is started by default. Choose Applications+System+Desktop Applet+Online Update Applet from the main menu to manually start it.

Online Update Applet Icon Status

Green Geeko Head with Green Arrows

No patches available.

Green Geeko Head with Yellow Arrows

The updater applet is busy (for example checking for updates, installing software).

Red Triangle with Exclamation Mark

Security patches available.

Orange Star with Arrow

Recommended patches are available.

Blue square with Arrow

Optional patches are available.

Yellow Triangle with Exclamation Mark

An error has occurred.

Blue Circle with Question Mark

No update repository is defined. When you click the updater applet in this state, you are asked if you want to check for updates. If you agree, the YaST Online Update Configuration module is started.

9.4.1.1. Installing Patches

The Online Update Applet offers two modes for installing patches: the simple installation mode will automatically install all security and recommended patches, while the detailed mode lets you choose which patches to install.

Procedure 9.1. Installing Patches: Simple Mode

  1. Whenever the update applet shows the availability of patches, left-click to open the software installation window.

  2. Choose whether to skip the installation of patches that are recommended and those that require a restart. It is recommended to install both.

  3. Click Install to start the patch installation.

  4. In case you have started the patch installation for the first time, you will be asked to enter the root password in order to proceed. If you also check Remember authorization you will never be asked again to provide the password.

  5. You can monitor the installation status by hovering the mouse over the update applet icon.

Figure 9.2. KDE Updater Applet: Simple Update View

KDE Updater Applet: Simple Update View

Procedure 9.2. Installing Patches: Detailed Mode

  1. Whenever the update applet shows the availability of patches, left-click to open the software installation window.

  2. A detailed list of all patches is shown. Click on a patch name for more information. Select or de-select a patch by clicking its checkbox. By default, security and recommended patches are pre-selected.

  3. Click Install to start the patch installation.

  4. In case you have started the patch installation for the first time, you will be asked to enter the root password in order to proceed. If you also check Remember authorization you will never be asked again to provide the password.

  5. You can monitor the installation status by hovering the mouse over the update applet icon.

Figure 9.3. KDE Updater Applet: Detailed Update View

KDE Updater Applet: Detailed Update View

You will be prompted for the root password after having proceeded with Install. The updater performs the installation of the patches. See the system tray (KDE) or the notification area (GNOME) for status messages and a progress meter.

The YaST Online Update offers advanced features to customize the patch installation. Please refer to Chapter YaST Online Update (↑Administration Guide) for more information.

9.4.1.2. Installing New Software Versions

New software versions are available from software repositories provided by the openSUSE community. By default, no such repositories are preconfigured. To add a repository, right-click on the updater icon and choose Add/Remove Update Sources. You need to enter the root password to start the Configured Software Repositories module. .

[Warning]Trusting External Software Sources

Before adding external software repositories to your list of repositories make sure this repository can be trusted. SUSE Linux Enterprise Server is not responsible for any potential problems arising from software installed from third party software repositories.

The updater applet does not monitor repositories for new software versions by default. To enable this feature, open the configuration window as described in Section 9.4.1.3, “Configuring the Updater Applet” and tick the check box Show Available Upgrades When Back-End Provides Them check box. When the updater icon indicates the availability of updates, click on the icon to launch the software installation window. Click on Details and then on the Upgrade tab to open the list with new software versions. Either select single packages by checking the box in front of an entry, or click Select All Packages. Install starts the installation of the selected software packages. You will be prompted for the root password. See the system tray (KDE) or the notification area (GNOME) for status messages and a progress meter.

9.4.1.3. Configuring the Updater Applet

By default the updater is started on login, checks for updates every 24 hours, shows recurring notifications every 60 minutes and monitors the availability of patches. To change this behavior, right-click the applet icon and choose Configure Applet.

Figure 9.4. KDE Updater Applet: Configuration

KDE Updater Applet: Configuration

The configuration dialog also offers to change the following settings:

Check for Updates Every

Choose the interval between checks for updates in hours.

Show Recurring Notification...

Choose the interval between notifications in minutes.

Automatically Start Updater on Login

Start the applet automatically when the user logs in. Active by default.

Back-End

Choose between different back-ends. The Zypp Plugin is used by default. If you prefer the Package Kit Plugin, make sure the package kde4-kupdateapplet-packagekit is installed.

Always Show Detailed View

Activate this option when you prefer the detailed patch view that lists all patches available with short summaries rather than the simple view.

Check for Updates only When System Is Connected to Charger

Prohibits checking for updates when running on batteries in order to save power. This option is activated by default but only affects mobile computers.

Check for Updates only When System Is under Low Load

Prohibits checking for updates when the system is under heavy load. This option is activated by default.

Search for Drivers When New Hardware is Attached

Provided a repository offering appropriate drivers, the updater can automatically install drivers for hardware such as USB devices.

9.4.2. Using the GNOME Updater Applet

The updater applet resides in the notification area of your panel. Its icon changes depending on the availability and relevance of patches and the status of the updater. The applet is started by default, choose Computer+More Applications+System+Update System.

[Note]Icon visibility

By default, the updater applet icon is only visible in the notification area, if patches are available.

Open box with a globe

The updater is busy (for example checking for updates or installing software).

Red Star with Exclamation Mark

Security patches are available.

Orange Star with an Up Arrow

Important patches are available.

Yellow Star with a Down Arrow

Trivial patches are available.

Yellow Triangle with Exclamation Mark

An error has occurred.

9.4.2.1. Installing Patches

The Software Update Applet offers two modes for installing patches: the simple installation mode will automatically install all security patches. Important or trivial patches can be installed with the detailed mode, which lets you also choose which patches to install.

Procedure 9.3. Installing Patches: Simple Mode

  1. Whenever new patches are available, a notification message listing the updates available will appear. Click on Install only security updates to start the installation of all security patches available.

  2. Enter the root password in the authentication screen and proceed with Authenticate.

Procedure 9.4. Installing Patches: Detailed Mode

  1. Whenever new patches are available, a notification message listing the updates available will appear. Click on Install all updates to open the Software Update window. If you have already closed the notification message, you can also left click the Software Update icon and choose Show Updates.

  2. An overview of number of patches in different categories is shown. To see a detailed list of all patches with descriptions, click Review. A description, version number, repository, and (if available) a link to bugzilla, the Novell bug tracking system. Select or de-select a patch by clicking its checkbox. By default, all patches are pre-selected.

  3. Click Install to start the patch installation.

  4. Enter the root password in the authentication screen and proceed with Authenticate.

Figure 9.5. GNOME Software Update Viewer: Detailed Update View

GNOME Software Update Viewer: Detailed Update View

You will be prompted for the root password after having proceeded with Apply Updates or Update System. The updater performs the installation of the patches. After having finished the installation, choose whether to Install More Updates or Close the Software Update Viewer.

The YaST Online Update offers advanced features to customize the patch installation. Please refer to Chapter YaST Online Update (↑Administration Guide) for more information.

9.4.2.2. Configuring the Updater Applet

To configure the updater applet, right-click the updater icon in the panel and choose Preferences. The configuration dialog lets you modify the following settings:

Check for Updates

Choose how often a check for updates is performed: Hourly, Daily, Weekly, or Never.

Automatically Install

Configure whether patches are installed automatically or not (default). Automatic installation can be chosen for either security patches only or for all patches.

Display Notification When Updates Are Available

Display a notification when updates are available. Active by default.

Figure 9.6. GNOME Updater Applet: Configuration

GNOME Updater Applet: Configuration