UCS 2.4 - Univention

11 Software maintenance
as standard. To update these packages, univention-actualise must be run with the command line
option −−dist-upgrade. These packages can thus not be updated via a package maintenance policy.
Updating is possible if the package is checked in advance in a package list for installation (see following
section).
Attention:
When packages are updated, a check is performed for whether any changes have been made to the
configuration files. If configuration files are no longer there in the form in which they were delivered,
they will not be overwritten. Instead a new version will be created in the same directory with the
ending .dpkg-new or .dpkg-dist. If changes should be made to Univention Configuration Reg-
istry templates, these templates are also not overwritten. Messages relating to this are written in the
/var/log/univention/actualise.log log file.
The messages created by univention-actualise during the update are also written on the updated
system in /var/log/univention/actualise.log except for the standard display. If messages to the
standard display are suppressed, univention-actualise can be run with the option −−silent.
If a package is not found, it may be the case that it is available in a repository which is not configured for
this system. The unmaintained section is a repository section with numerous, further packages, which is
available for every UCS version. If this area should be mounted on a system, this can be done by setting
the Univention Configuration Registry variable repository/online/unmaintained to yes. If local
repository servers are set, it must be observed that the unmaintained section will also be synchronised in
this case and the repository thus requires more memory space on the hard drive.
11.3.3 Adding component repositories
In addition to the standard repositories, additional software components can also be integrated. There
are two possible variations to use these. On the one hand, the Univention Management Console module
Online updates can be used. Alternatively this can be performed using the following Univention Configu-
ration Registry variables:
repository/online/component//server The repository server on which the components are
available. If this variable is not set, the server from the Univention Configuration Registry variable
repository/online/server uses
repository/online/component/ This variable must be set to enabled if the components are to
be mounted.
repository/online/component//localmirror This variable can be used to configure whether the
component is mirrored locally. In combination with the Univention Configuration Registry variable
repository/online/component//server, a configuration can be set up so that the
component is mirrored, but not activated, or that it is activated, but not mirrored.
repository/online/component//description A descriptive name for the repository.
repository/online/component//prefix Defines the URL prefix which is used on the repository
server. This variable is usually not set.
repository/online/component//username If the repository server requires authentication, the
242
user name can be entered in this variable.