X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/0741daeb7ab870b4dd62a93fa12a1cf6330f9a72..ae2a6be8a2155c136f9535abfbcc750c8c395cd2:/doc/sources.list.5.xml diff --git a/doc/sources.list.5.xml b/doc/sources.list.5.xml index aded8ecef..e6d82b1e7 100644 --- a/doc/sources.list.5.xml +++ b/doc/sources.list.5.xml @@ -14,7 +14,7 @@ &apt-email; &apt-product; - 2014-01-18T00:00:00Z + 2016-06-20T00:00:00Z @@ -31,12 +31,13 @@ Description - The source list /etc/apt/sources.list and the the + The source list /etc/apt/sources.list and the files contained in /etc/apt/sources.list.d/ are designed to support any number of active sources and a variety of source - media. The files list one source per line (one line style) or contain multiline + media. The files list one source per line (one-line style) or contain multiline stanzas defining one or more sources per stanza (deb822 style), with the - most preferred source listed first. The information available from the + most preferred source listed first (in case a single version is + available from more than one source). The information available from the configured sources is acquired by apt-get update (or by an equivalent command from another APT front-end). @@ -55,7 +56,7 @@ configuration list - in which case it will be silently ignored. - one line style format + One-Line-Style Format Files in this format have the extension .list. Each line specifying a source starts with a type (e.g. deb-src) @@ -71,27 +72,27 @@ included in the line after the type separated from it with a space. If an option allows multiple values these are separated from each other with a comma (,). An option name is separated from its - value(s) by a equal sign (=). Multivalue options have - also -= and += as separator which + value(s) by an equals sign (=). Multivalue options also + have -= and += as separators, which instead of replacing the default with the given value(s) modify the default value(s) to remove or include the given values. This is the traditional format and supported by all apt versions. Note that not all options as described below are supported by all apt versions. - Note also that some older applications parsing this format on its own might not + Note also that some older applications parsing this format on their own might not expect to encounter options as they were uncommon before the introduction of multi-architecture support. - deb822 style format + deb822-Style Format Files in this format have the extension .sources. The format is similar in syntax to other files used by Debian and its - derivatives, like the metadata itself apt will download from the configured + derivatives, such as the metadata files that apt will download from the configured sources or the debian/control file in a Debian source package. - Individual entries are separated by an empty line, additional empty + Individual entries are separated by an empty line; additional empty lines are ignored, and a # character at the start of the line marks the entire line as a comment. An entry can hence be disabled by commenting out each line belonging to the stanza, but it is @@ -101,38 +102,38 @@ Options have the same syntax as every other field: A fieldname separated by a colon (:) and optionally spaces from its value(s). Note especially that multiple values are separated by spaces, not by - commas as in the one line format. Multivalue fields like Architectures + commas as in the one-line format. Multivalue fields like Architectures also have Architectures-Add and Architectures-Remove to modify the default value rather than replacing it. This is a new format supported by apt itself since version 1.1. Previous versions ignore such files with a notice message as described earlier. - It is intended to make this format gradually the default format and - deprecating the previously described one line style format as it is - easier to create, extend and modify by humans and machines alike + It is intended to make this format gradually the default format, + deprecating the previously described one-line-style format, as it is + easier to create, extend and modify for humans and machines alike especially if a lot of sources and/or options are involved. Developers who are working with and/or parsing apt sources are highly encouraged to add support for this format and to contact the APT team to coordinate and share this work. Users can freely adopt this format - already, but could encounter problems with software not supporting + already, but may encounter problems with software not supporting the format yet. - The deb and deb-src types: General Format + The deb and deb-src Types: General Format The deb type references a typical two-level Debian archive, distribution/component. The distribution is generally a suite name like stable or testing or a codename like - &stable-codename; or &testing-codename; + &debian-stable-codename; or &debian-testing-codename; while component is one of main, contrib or non-free. The deb-src type references a Debian distribution's source code in the same form as the deb type. A deb-src line is required to fetch source indexes. - The format for two one line style entries using the + The format for two one-line-style entries using the deb and deb-src types is: deb [ option1=value1 option2=value2 ] uri suite [component1] [component2] [...] @@ -163,10 +164,10 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. which expands to the Debian architecture (such as amd64 or armel) used on the system. This permits architecture-independent sources.list files to be used. In general this is only - of interest when specifying an exact path, APT will + of interest when specifying an exact path; APT will automatically generate a URI with the current architecture otherwise. - Especially in the one line style format since only one distribution + Especially in the one-line-style format since only one distribution can be specified per line it may be necessary to have multiple lines for the same URI, if a subset of all available distributions or components at that location is desired. APT will sort the URI list after it has @@ -184,19 +185,19 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. network, followed by distant Internet hosts, for example). As an example, the sources for your distribution could look like this - in one line style format: + in one-line-style format: &sourceslist-list-format; or like this in deb822 style format: &sourceslist-sources-format; The deb and deb-src types: Options - Each source entry can have options specified modifying which and how - the source is accessed and data acquired from it. Format, syntax and names - of the options varies between the two formats one line and deb822 style - as described, but they have both the same options available. For simplicity - we list the deb822 fieldname and provide the one line name in brackets. - Remember that beside setting multivalue options explicitly, there is also + Each source entry can have options specified to modify which source + is accessed and how data is acquired from it. Format, syntax and names + of the options vary between the one-line-style and deb822-style formats + as described, but they both have the same options available. For simplicity + we list the deb822 fieldname and provide the one-line name in brackets. + Remember that besides setting multivalue options explicitly, there is also the option to modify them based on the default, but we aren't listing those names explicitly here. Unsupported options are silently ignored by all APT versions. @@ -211,7 +212,7 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. () is a multivalue option defining for - which languages information like translated package + which languages information such as translated package descriptions should be downloaded. If this option isn't set the default is all languages as defined by the config option. @@ -221,42 +222,102 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. () is a multivalue option defining which download targets apt will try to acquire from this source. If not specified, the default set is defined by the - configuration scope. + configuration scope + (targets are specified by their name in the + Created-By field). + Additionally, targets can be enabled or disabled by using the + Identifier field as an option with a boolean + value instead of using this multivalue option. + + () + is a yes/no value which controls if APT should try to use PDiffs + to update old indexes instead of downloading the new indexes + entirely. The value of this option is ignored if the repository + doesn't announce the availability of PDiffs. Defaults to the + value of the option with the same name for a specific index file + defined in the scope, + which itself defaults to the value of configuration option + which defaults to + yes. + + + () + can have the value yes, no + or force and controls if APT should try to + acquire indexes via a URI constructed from a hashsum of the + expected file instead of using the well-known stable filename + of the index. Using this can avoid hashsum mismatches, but + requires a supporting mirror. A yes or + no value activates/disables the use of this + feature if this source indicates support for it, while + force will enable the feature regardless of + what the source indicates. Defaults to the value of the option + of the same name for a specific index file defined in the + scope, which itself + defaults to the value of configuration option + which defaults to + yes. + + - Further more, there are options which if set effect + Furthermore, there are options which if set affect all sources with the same URI and Suite, so they have to be set on all such entries and can not be varied between different components. APT will try to detect and error out on such anomalies. + (), + () and + () + are boolean values which all default to no. + If set to yes they circumvent parts of &apt-secure; + and should therefore not be used lightly! + + () is a tri-state value which defaults to APT deciding if a source is considered trusted or if warnings should be raised before e.g. packages are installed from this source. This option can be used - to override this decision either with the value yes, - which lets APT consider this source always as a trusted source - even if it has no or fails authentication checks by disabling parts - of &apt-secure; and should therefore only be used in a local and trusted - context (if at all) as otherwise security is breached. The opposite - can be achieved with the value no, which causes the source to be handled - as untrusted even if the authentication checks passed successfully. - The default value can't be set explicitly. + to override that decision. The value yes tells APT + always to consider this source as trusted, even if it doesn't pass + authentication checks. It disables parts of &apt-secure;, and should + therefore only be used in a local and trusted context (if at all) as + otherwise security is breached. The value no does + the opposite, causing the source to be handled as untrusted even if + the authentication checks passed successfully. The default value can't + be set explicitly. + + + () + is either an absolute path to a keyring file (has to be + accessible and readable for the _apt user, + so ensure everyone has read-permissions on the file) or one or + more fingerprints of keys either in the + trusted.gpg keyring or in the + keyrings in the trusted.gpg.d/ directory + (see apt-key fingerprint). If the option is + set, only the key(s) in this keyring or only the keys with these + fingerprints are used for the &apt-secure; verification of this + repository. Defaults to the value of the option with the same name + if set in the previously acquired Release file. + Otherwise all keys in the trusted keyrings are considered valid + signers for this repository. () is a yes/no value which controls if APT should try to detect - replay attacks. A repository creator can declare until then the - data provided in the repository should be considered valid and - if this time is reached, but no new data is provided the data - is considered expired and an error is raised. Beside - increasing security as a malicious attacker can't sent old data - forever denying a user to be able to upgrade to a new version, + replay attacks. A repository creator can declare a time until + which the data provided in the repository should be considered valid, + and if this time is reached, but no new data is provided, the data + is considered expired and an error is raised. Besides + increasing security, as a malicious attacker can't send old data + forever to prevent a user from upgrading to a new version, this also helps users identify mirrors which are no longer - updated. Some repositories like historic archives aren't - updated anymore by design through, so this check can be + updated. However, some repositories such as historic archives + are not updated any more by design, so this check can be disabled by setting this option to no. Defaults to the value of configuration option which itself @@ -264,14 +325,14 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. - () and + () and () can be used to raise or lower the time period in seconds in which the data from this repository is considered valid. -Max can be especially useful if the repository provides no Valid-Until field on its Release file to set your own value, while -Min can be used to increase - the valid time on seldomly updated (local) mirrors of a more + the valid time on seldom updated (local) mirrors of a more frequently updated but less accessible archive (which is in the sources.list as well) instead of disabling the check entirely. Default to the value of the configuration options @@ -285,7 +346,7 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. - URI specification + URI Specification The currently recognized URI types are: @@ -354,7 +415,7 @@ deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [. - + Examples Uses the archive stored locally (or NFS mounted) at /home/apt/debian for stable/main, stable/contrib, and stable/non-free. @@ -371,26 +432,25 @@ URIs: file:/home/apt/debian Suites: unstable Components: main contrib non-free - Source line for the above + Sources specification for the above. deb-src file:/home/apt/debian unstable main contrib non-free Types: deb-src URIs: file:/home/apt/debian Suites: unstable Components: main contrib non-free - The first line gets package information for the architectures in APT::Architectures while the second always retrieves amd64 and armel. - deb http://httpredir.debian.org/debian &stable-codename; main -deb [ arch=amd64,armel ] http://httpredir.debian.org/debian &stable-codename; main + deb http://httpredir.debian.org/debian &debian-stable-codename; main +deb [ arch=amd64,armel ] http://httpredir.debian.org/debian &debian-stable-codename; main Types: deb URIs: http://httpredir.debian.org/debian -Suites: &stable-codename; +Suites: &debian-stable-codename; Components: main Types: deb URIs: http://httpredir.debian.org/debian -Suites: &stable-codename; +Suites: &debian-stable-codename; Components: main Architectures: amd64 armel @@ -404,11 +464,11 @@ Suites: hamm Components: main Uses FTP to access the archive at ftp.debian.org, under the debian - directory, and uses only the &stable-codename;/contrib area. - deb ftp://ftp.debian.org/debian &stable-codename; contrib + directory, and uses only the &debian-stable-codename;/contrib area. + deb ftp://ftp.debian.org/debian &debian-stable-codename; contrib Types: deb URIs: ftp://ftp.debian.org/debian -Suites: &stable-codename; +Suites: &debian-stable-codename; Components: contrib Uses FTP to access the archive at ftp.debian.org, under the debian @@ -451,8 +511,7 @@ Components: main contrib See Also - &apt-get;, &apt-conf; - + &apt-get;, &apt-conf;, &apt-acquire-additional-files; &manbugs;