Changes between Version 32 and Version 33 of Doc/SCDB/Usage


Ignore:
Timestamp:
Mar 22, 2010, 8:43:53 AM (14 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/SCDB/Usage

    v32 v33  
    172172=== Checking Package Dependencies ===
    173173
    174 Profile compilation cannot check if all the dependencies for all packages present in the profile can be satisfied. By default, this is checked by SPMA on the client before trying to deploy de RPM changes. A tool can be used to check dependencies after compilation but before deployment. This is done by analyzing the profile and checking the metadata for each RPM present, using YUM as a source for the dependency metadata (this requires each RPM repository to be configured as a YUM repository). The tool is `utils/checkdeps/checkdeps`. Its usage and requirements are described in a [https://sourceforge.net/apps/mediawiki/quattor/index.php?title=Client_dependencies_check dedicated page].
     174Profile compilation cannot check if all the dependencies for all packages present in the profile can be satisfied. By default, this is checked by SPMA on the client before trying to deploy de RPM changes. A tool can be used to check dependencies after compilation but before deployment. This is done by analyzing the profile and checking the metadata for each RPM present, using YUM as a source for the dependency metadata (this requires each RPM repository to be configured as a YUM repository). The tool is `utils/checkdeps/checkdeps`. Its usage and requirements are described in [wiki:Web/CheckDeps#Runningcheckdeps Quattor Tool Catalog].
    175175
    176176One nice feature of `checkdeps` is that it can report missing packages are Pan lines to add to the configuration. This is done with option -p. A typical calling sequence for `checkdeps` is: