Browsing French translation

125.

Force yes; this is a dangerous option that will cause apt to continue without prompting if it is doing something potentially harmful. It should not be used except in very special situations. Using <literal>force-yes</literal> can potentially destroy your system! Configuration Item: <literal>APT::Get::force-yes</literal>. This is deprecated and replaced by <option>--allow-unauthenticated</option> , <option>--allow-downgrades</option> , <option>--allow-remove-essential</option> , <option>--allow-change-held-packages</option> in 1.1.

140.

Allow the update command to continue downloading data from a repository which changed its information of the release contained in the repository indicating e.g a new major release. APT will fail at the update command for such repositories until the change is confirmed to ensure the user is prepared for the change. See also &apt-secure; for details on the concept and configuration.

141.

Specialist options (<literal>--allow-releaseinfo-change-</literal><replaceable>field</replaceable>) exist to allow changes only for certain fields like <literal>origin</literal>, <literal>label</literal>, <literal>codename</literal>, <literal>suite</literal>, <literal>version</literal> and <literal>defaultpin</literal>. See also &apt-preferences;. Configuration Item: <literal>Acquire::AllowReleaseInfoChanges</literal>.

241.

Starting with version 0.6, <command>APT</command> contains code that does signature checking of the Release file for all repositories. This ensures that data like packages in the archive can't be modified by people who have no access to the Release file signing key. Starting with version 1.1 <command>APT</command> requires repositories to provide recent authentication information for unimpeded usage of the repository. Since version 1.5 changes in the information contained in the Release file about the repository need to be confirmed before APT continues to apply updates from this repository.

243.

Unsigned Repositories

247.

Signed Repositories

257.

Information changes

258.

A Release file contains beside the checksums for the files in the repository also general information about the repository like the origin, codename or version number of the release.

259.

This information is shown in various places so a repository owner should always ensure correctness. Further more user configuration like &apt-preferences; can depend and make use of this information. Since version 1.5 the user must therefore explicitly confirm changes to signal that the user is sufficiently prepared e.g. for the new major release of the distribution shipped in the repository (as e.g. indicated by the codename).

264.

Repository Configuration