You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1074 lines
50 KiB

  1. <?xml version="1.0" encoding="utf-8" standalone="no"?>
  2. <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  3. "" [
  4. <!ENTITY % aptent SYSTEM "apt.ent">
  5. %aptent;
  6. ]>
  7. <refentry>
  8. <refentryinfo>
  9. &apt-author.jgunthorpe;
  10. &;
  11. <author>
  12. <firstname>Daniel</firstname>
  13. <surname>Burrows</surname>
  14. <contrib>Initial documentation of Debug::*.</contrib>
  15. <email></email>
  16. </author>
  17. &apt-email;
  18. &apt-product;
  19. <!-- The last update date -->
  20. <date>16 January 2010</date>
  21. </refentryinfo>
  22. <refmeta>
  23. <refentrytitle>apt.conf</refentrytitle>
  24. <manvolnum>5</manvolnum>
  25. <refmiscinfo class="manual">APT</refmiscinfo>
  26. </refmeta>
  27. <!-- Man page title -->
  28. <refnamediv>
  29. <refname>apt.conf</refname>
  30. <refpurpose>Configuration file for APT</refpurpose>
  31. </refnamediv>
  32. <refsect1><title>Description</title>
  33. <para><filename>apt.conf</filename> is the main configuration file for
  34. the APT suite of tools, but by far not the only place changes to options
  35. can be made. All tools therefore share the configuration files and also
  36. use a common command line parser to provide a uniform environment.</para>
  37. <orderedlist>
  38. <para>When an APT tool starts up it will read the configuration files
  39. in the following order:</para>
  40. <listitem><para>the file specified by the <envar>APT_CONFIG</envar>
  41. environment variable (if any)</para></listitem>
  42. <listitem><para>all files in <literal>Dir::Etc::Parts</literal> in
  43. alphanumeric ascending order which have no or "<literal>conf</literal>"
  44. as filename extension and which only contain alphanumeric,
  45. hyphen (-), underscore (_) and period (.) characters -
  46. otherwise they will be silently ignored.</para></listitem>
  47. <listitem><para>the main configuration file specified by
  48. <literal>Dir::Etc::main</literal></para></listitem>
  49. <listitem><para>the command line options are applied to override the
  50. configuration directives or to load even more configuration files.</para></listitem>
  51. </orderedlist>
  52. </refsect1>
  53. <refsect1><title>Syntax</title>
  54. <para>The configuration file is organized in a tree with options organized into
  55. functional groups. Option specification is given with a double colon
  56. notation, for instance <literal>APT::Get::Assume-Yes</literal> is an option within
  57. the APT tool group, for the Get tool. Options do not inherit from their
  58. parent groups.</para>
  59. <para>Syntactically the configuration language is modeled after what the ISC tools
  60. such as bind and dhcp use. Lines starting with
  61. <literal>//</literal> are treated as comments (ignored), as well as all text
  62. between <literal>/*</literal> and <literal>*/</literal>, just like C/C++ comments.
  63. Each line is of the form
  64. <literal>APT::Get::Assume-Yes "true";</literal>. The trailing
  65. semicolon and the quotes are required. The value must be on one line, and
  66. there is no kind of string concatenation. It must not include inside quotes.
  67. The behavior of the backslash "\" and escaped characters inside a value is
  68. undefined and it should not be used. An option name may include
  69. alphanumerical characters and the "/-:._+" characters. A new scope can
  70. be opened with curly braces, like:</para>
  71. <informalexample><programlisting>
  72. APT {
  73. Get {
  74. Assume-Yes "true";
  75. Fix-Broken "true";
  76. };
  77. };
  78. </programlisting></informalexample>
  79. <para>with newlines placed to make it more readable. Lists can be created by
  80. opening a scope and including a single string enclosed in quotes followed by a
  81. semicolon. Multiple entries can be included, each separated by a semicolon.</para>
  82. <informalexample><programlisting>
  83. DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
  84. </programlisting></informalexample>
  85. <para>In general the sample configuration file in
  86. <filename>&docdir;examples/apt.conf</filename> &configureindex;
  87. is a good guide for how it should look.</para>
  88. <para>The names of the configuration items are not case-sensitive. So in the previous example
  89. you could use <literal>dpkg::pre-install-pkgs</literal>.</para>
  90. <para>Names for the configuration items are optional if a list is defined as it can be see in
  91. the <literal>DPkg::Pre-Install-Pkgs</literal> example above. If you don't specify a name a
  92. new entry will simply add a new option to the list. If you specify a name you can override
  93. the option as every other option by reassigning a new value to the option.</para>
  94. <para>Two specials are allowed, <literal>#include</literal> (which is deprecated
  95. and not supported by alternative implementations) and <literal>#clear</literal>:
  96. <literal>#include</literal> will include the given file, unless the filename
  97. ends in a slash, then the whole directory is included.
  98. <literal>#clear</literal> is used to erase a part of the configuration tree. The
  99. specified element and all its descendants are erased.
  100. (Note that these lines also need to end with a semicolon.)</para>
  101. <para>The #clear command is the only way to delete a list or a complete scope.
  102. Reopening a scope or the ::-style described below will <emphasis>not</emphasis>
  103. override previously written entries. Only options can be overridden by addressing a new
  104. value to it - lists and scopes can't be overridden, only cleared.</para>
  105. <para>All of the APT tools take a -o option which allows an arbitrary configuration
  106. directive to be specified on the command line. The syntax is a full option
  107. name (<literal>APT::Get::Assume-Yes</literal> for instance) followed by an equals
  108. sign then the new value of the option. Lists can be appended too by adding
  109. a trailing :: to the list name. (As you might suspect: The scope syntax can't be used
  110. on the command line.)</para>
  111. <para>Note that you can use :: only for appending one item per line to a list and
  112. that you should not use it in combination with the scope syntax.
  113. (The scope syntax implicit insert ::) Using both syntaxes together will trigger a bug
  114. which some users unfortunately relay on: An option with the unusual name "<literal>::</literal>"
  115. which acts like every other option with a name. These introduces many problems
  116. including that a user who writes multiple lines in this <emphasis>wrong</emphasis> syntax in
  117. the hope to append to a list will gain the opposite as only the last assignment for this option
  118. "<literal>::</literal>" will be used. Upcoming APT versions will raise errors and
  119. will stop working if they encounter this misuse, so please correct such statements now
  120. as long as APT doesn't complain explicit about them.</para>
  121. </refsect1>
  122. <refsect1><title>The APT Group</title>
  123. <para>This group of options controls general APT behavior as well as holding the
  124. options for all of the tools.</para>
  125. <variablelist>
  126. <varlistentry><term>Architecture</term>
  127. <listitem><para>System Architecture; sets the architecture to use when fetching files and
  128. parsing package lists. The internal default is the architecture apt was
  129. compiled for.</para></listitem>
  130. </varlistentry>
  131. <varlistentry><term>Default-Release</term>
  132. <listitem><para>Default release to install packages from if more than one
  133. version available. Contains release name, codename or release version. Examples: 'stable', 'testing',
  134. 'unstable', '&stable-codename;', '&testing-codename;', '4.0', '5.0*'. See also &apt-preferences;.</para></listitem>
  135. </varlistentry>
  136. <varlistentry><term>Ignore-Hold</term>
  137. <listitem><para>Ignore Held packages; This global option causes the problem resolver to
  138. ignore held packages in its decision making.</para></listitem>
  139. </varlistentry>
  140. <varlistentry><term>Clean-Installed</term>
  141. <listitem><para>Defaults to on. When turned on the autoclean feature will remove any packages
  142. which can no longer be downloaded from the cache. If turned off then
  143. packages that are locally installed are also excluded from cleaning - but
  144. note that APT provides no direct means to reinstall them.</para></listitem>
  145. </varlistentry>
  146. <varlistentry><term>Immediate-Configure</term>
  147. <listitem><para>Defaults to on which will cause APT to install essential and important packages
  148. as fast as possible in the install/upgrade operation. This is done to limit the effect of a failing
  149. &dpkg; call: If this option is disabled APT does treat an important package in the same way as
  150. an extra package: Between the unpacking of the important package A and his configuration can then
  151. be many other unpack or configuration calls, e.g. for package B which has no relation to A, but
  152. causes the dpkg call to fail (e.g. because maintainer script of package B generates an error) which results
  153. in a system state in which package A is unpacked but unconfigured - each package depending on A is now no
  154. longer guaranteed to work as their dependency on A is not longer satisfied. The immediate configuration marker
  155. is also applied to all dependencies which can generate a problem if the dependencies e.g. form a circle
  156. as a dependency with the immediate flag is comparable with a Pre-Dependency. So in theory it is possible
  157. that APT encounters a situation in which it is unable to perform immediate configuration, errors out and
  158. refers to this option so the user can deactivate the immediate configuration temporarily to be able to perform
  159. an install/upgrade again. Note the use of the word "theory" here as this problem was only encountered by now
  160. in real world a few times in non-stable distribution versions and was caused by wrong dependencies of the package
  161. in question or by a system in an already broken state, so you should not blindly disable this option as
  162. the mentioned scenario above is not the only problem immediate configuration can help to prevent in the first place.
  163. Before a big operation like <literal>dist-upgrade</literal> is run with this option disabled it should be tried to
  164. explicitly <literal>install</literal> the package APT is unable to configure immediately, but please make sure to
  165. report your problem also to your distribution and to the APT team with the buglink below so they can work on
  166. improving or correcting the upgrade process.</para></listitem>
  167. </varlistentry>
  168. <varlistentry><term>Force-LoopBreak</term>
  169. <listitem><para>Never Enable this option unless you -really- know what you are doing. It
  170. permits APT to temporarily remove an essential package to break a
  171. Conflicts/Conflicts or Conflicts/Pre-Depend loop between two essential
  173. will work if the essential packages are not tar, gzip, libc, dpkg, bash or
  174. anything that those packages depend on.</para></listitem>
  175. </varlistentry>
  176. <varlistentry><term>Cache-Limit</term>
  177. <listitem><para>APT uses a fixed size memory mapped cache file to store the 'available'
  178. information. This sets the size of that cache (in bytes).</para></listitem>
  179. </varlistentry>
  180. <varlistentry><term>Build-Essential</term>
  181. <listitem><para>Defines which package(s) are considered essential build dependencies.</para></listitem>
  182. </varlistentry>
  183. <varlistentry><term>Get</term>
  184. <listitem><para>The Get subsection controls the &apt-get; tool, please see its
  185. documentation for more information about the options here.</para></listitem>
  186. </varlistentry>
  187. <varlistentry><term>Cache</term>
  188. <listitem><para>The Cache subsection controls the &apt-cache; tool, please see its
  189. documentation for more information about the options here.</para></listitem>
  190. </varlistentry>
  191. <varlistentry><term>CDROM</term>
  192. <listitem><para>The CDROM subsection controls the &apt-cdrom; tool, please see its
  193. documentation for more information about the options here.</para></listitem>
  194. </varlistentry>
  195. </variablelist>
  196. </refsect1>
  197. <refsect1><title>The Acquire Group</title>
  198. <para>The <literal>Acquire</literal> group of options controls the download of packages
  199. and the URI handlers.
  200. <variablelist>
  201. <varlistentry><term>Check-Valid-Until</term>
  202. <listitem><para>Security related option defaulting to true as an
  203. expiring validation for a Release file prevents longtime replay attacks
  204. and can e.g. also help users to identify no longer updated mirrors -
  205. but the feature depends on the correctness of the time on the user system.
  206. Archive maintainers are encouraged to create Release files with the
  207. <literal>Valid-Until</literal> header, but if they don't or a stricter value
  208. is volitional the following <literal>Max-ValidTime</literal> option can be used.
  209. </para></listitem>
  210. </varlistentry>
  211. <varlistentry><term>Max-ValidTime</term>
  212. <listitem><para>Seconds the Release file should be considered valid after
  213. it was created. The default is "for ever" (0) if the Release file of the
  214. archive doesn't include a <literal>Valid-Until</literal> header.
  215. If it does then this date is the default. The date from the Release file or
  216. the date specified by the creation time of the Release file
  217. (<literal>Date</literal> header) plus the seconds specified with this
  218. options are used to check if the validation of a file has expired by using
  219. the earlier date of the two. Archive specific settings can be made by
  220. appending the label of the archive to the option name.
  221. </para></listitem>
  222. </varlistentry>
  223. <varlistentry><term>PDiffs</term>
  224. <listitem><para>Try to download deltas called <literal>PDiffs</literal> for
  225. Packages or Sources files instead of downloading whole ones. True
  226. by default.</para>
  227. <para>Two sub-options to limit the use of PDiffs are also available:
  228. With <literal>FileLimit</literal> can be specified how many PDiff files
  229. are downloaded at most to patch a file. <literal>SizeLimit</literal>
  230. on the other hand is the maximum precentage of the size of all patches
  231. compared to the size of the targeted file. If one of these limits is
  232. exceeded the complete file is downloaded instead of the patches.
  233. </para></listitem>
  234. </varlistentry>
  235. <varlistentry><term>Queue-Mode</term>
  236. <listitem><para>Queuing mode; <literal>Queue-Mode</literal> can be one of <literal>host</literal> or
  237. <literal>access</literal> which determines how APT parallelizes outgoing
  238. connections. <literal>host</literal> means that one connection per target host
  239. will be opened, <literal>access</literal> means that one connection per URI type
  240. will be opened.</para></listitem>
  241. </varlistentry>
  242. <varlistentry><term>Retries</term>
  243. <listitem><para>Number of retries to perform. If this is non-zero APT will retry failed
  244. files the given number of times.</para></listitem>
  245. </varlistentry>
  246. <varlistentry><term>Source-Symlinks</term>
  247. <listitem><para>Use symlinks for source archives. If set to true then source archives will
  248. be symlinked when possible instead of copying. True is the default.</para></listitem>
  249. </varlistentry>
  250. <varlistentry><term>http</term>
  251. <listitem><para>HTTP URIs; http::Proxy is the default http proxy to use. It is in the
  252. standard form of <literal>http://[[user][:pass]@]host[:port]/</literal>. Per
  253. host proxies can also be specified by using the form
  254. <literal>http::Proxy::&lt;host&gt;</literal> with the special keyword <literal>DIRECT</literal>
  255. meaning to use no proxies. If no one of the above settings is specified,
  256. <envar>http_proxy</envar> environment variable
  257. will be used.</para>
  258. <para>Three settings are provided for cache control with HTTP/1.1 compliant
  259. proxy caches. <literal>No-Cache</literal> tells the proxy to not use its cached
  260. response under any circumstances, <literal>Max-Age</literal> is sent only for
  261. index files and tells the cache to refresh its object if it is older than
  262. the given number of seconds. Debian updates its index files daily so the
  263. default is 1 day. <literal>No-Store</literal> specifies that the cache should never
  264. store this request, it is only set for archive files. This may be useful
  265. to prevent polluting a proxy cache with very large .deb files. Note:
  266. Squid 2.0.2 does not support any of these options.</para>
  267. <para>The option <literal>timeout</literal> sets the timeout timer used by the method,
  268. this applies to all things including connection timeout and data timeout.</para>
  269. <para>One setting is provided to control the pipeline depth in cases where the
  270. remote server is not RFC conforming or buggy (such as Squid 2.0.2).
  271. <literal>Acquire::http::Pipeline-Depth</literal> can be a value from 0 to 5
  272. indicating how many outstanding requests APT should send. A value of
  273. zero MUST be specified if the remote host does not properly linger
  274. on TCP connections - otherwise data corruption will occur. Hosts which
  275. require this are in violation of RFC 2068.</para>
  276. <para>The used bandwidth can be limited with <literal>Acquire::http::Dl-Limit</literal>
  277. which accepts integer values in kilobyte. The default value is 0 which deactivates
  278. the limit and tries uses as much as possible of the bandwidth (Note that this option implicit
  279. deactivates the download from multiple servers at the same time.)</para>
  280. <para><literal>Acquire::http::User-Agent</literal> can be used to set a different
  281. User-Agent for the http download method as some proxies allow access for clients
  282. only if the client uses a known identifier.</para>
  283. </listitem>
  284. </varlistentry>
  285. <varlistentry><term>https</term>
  286. <listitem><para>HTTPS URIs. Cache-control, Timeout, AllowRedirect, Dl-Limit and
  287. proxy options are the same as for <literal>http</literal> method and will also
  288. default to the options from the <literal>http</literal> method if they are not
  289. explicitly set for https. <literal>Pipeline-Depth</literal> option is not
  290. supported yet.</para>
  291. <para><literal>CaInfo</literal> suboption specifies place of file that
  292. holds info about trusted certificates.
  293. <literal>&lt;host&gt;::CaInfo</literal> is corresponding per-host option.
  294. <literal>Verify-Peer</literal> boolean suboption determines whether verify
  295. server's host certificate against trusted certificates or not.
  296. <literal>&lt;host&gt;::Verify-Peer</literal> is corresponding per-host option.
  297. <literal>Verify-Host</literal> boolean suboption determines whether verify
  298. server's hostname or not.
  299. <literal>&lt;host&gt;::Verify-Host</literal> is corresponding per-host option.
  300. <literal>SslCert</literal> determines what certificate to use for client
  301. authentication. <literal>&lt;host&gt;::SslCert</literal> is corresponding per-host option.
  302. <literal>SslKey</literal> determines what private key to use for client
  303. authentication. <literal>&lt;host&gt;::SslKey</literal> is corresponding per-host option.
  304. <literal>SslForceVersion</literal> overrides default SSL version to use.
  305. Can contain 'TLSv1' or 'SSLv3' string.
  306. <literal>&lt;host&gt;::SslForceVersion</literal> is corresponding per-host option.
  307. </para></listitem></varlistentry>
  308. <varlistentry><term>ftp</term>
  309. <listitem><para>FTP URIs; ftp::Proxy is the default ftp proxy to use. It is in the
  310. standard form of <literal>ftp://[[user][:pass]@]host[:port]/</literal>. Per
  311. host proxies can also be specified by using the form
  312. <literal>ftp::Proxy::&lt;host&gt;</literal> with the special keyword <literal>DIRECT</literal>
  313. meaning to use no proxies. If no one of the above settings is specified,
  314. <envar>ftp_proxy</envar> environment variable
  315. will be used. To use a ftp
  316. proxy you will have to set the <literal>ftp::ProxyLogin</literal> script in the
  317. configuration file. This entry specifies the commands to send to tell
  318. the proxy server what to connect to. Please see
  319. &configureindex; for an example of
  320. how to do this. The substitution variables available are
  321. <literal>$(PROXY_USER)</literal> <literal>$(PROXY_PASS)</literal> <literal>$(SITE_USER)</literal>
  322. <literal>$(SITE_PASS)</literal> <literal>$(SITE)</literal> and <literal>$(SITE_PORT)</literal>
  323. Each is taken from it's respective URI component.</para>
  324. <para>The option <literal>timeout</literal> sets the timeout timer used by the method,
  325. this applies to all things including connection timeout and data timeout.</para>
  326. <para>Several settings are provided to control passive mode. Generally it is
  327. safe to leave passive mode on, it works in nearly every environment.
  328. However some situations require that passive mode be disabled and port
  329. mode ftp used instead. This can be done globally, for connections that
  330. go through a proxy or for a specific host (See the sample config file
  331. for examples).</para>
  332. <para>It is possible to proxy FTP over HTTP by setting the <envar>ftp_proxy</envar>
  333. environment variable to a http url - see the discussion of the http method
  334. above for syntax. You cannot set this in the configuration file and it is
  335. not recommended to use FTP over HTTP due to its low efficiency.</para>
  336. <para>The setting <literal>ForceExtended</literal> controls the use of RFC2428
  337. <literal>EPSV</literal> and <literal>EPRT</literal> commands. The default is false, which means
  338. these commands are only used if the control connection is IPv6. Setting this
  339. to true forces their use even on IPv4 connections. Note that most FTP servers
  340. do not support RFC2428.</para></listitem>
  341. </varlistentry>
  342. <varlistentry><term>cdrom</term>
  343. <listitem><para>CDROM URIs; the only setting for CDROM URIs is the mount point,
  344. <literal>cdrom::Mount</literal> which must be the mount point for the CDROM drive
  345. as specified in <filename>/etc/fstab</filename>. It is possible to provide
  346. alternate mount and unmount commands if your mount point cannot be listed
  347. in the fstab (such as an SMB mount and old mount packages). The syntax
  348. is to put <literallayout>/cdrom/::Mount "foo";</literallayout> within
  349. the cdrom block. It is important to have the trailing slash. Unmount
  350. commands can be specified using UMount.</para></listitem>
  351. </varlistentry>
  352. <varlistentry><term>gpgv</term>
  353. <listitem><para>GPGV URIs; the only option for GPGV URIs is the option to pass additional parameters to gpgv.
  354. <literal>gpgv::Options</literal> Additional options passed to gpgv.
  355. </para></listitem>
  356. </varlistentry>
  357. <varlistentry><term>CompressionTypes</term>
  358. <listitem><para>List of compression types which are understood by the acquire methods.
  359. Files like <filename>Packages</filename> can be available in various compression formats.
  360. Per default the acquire methods can decompress <command>bzip2</command>, <command>lzma</command>
  361. and <command>gzip</command> compressed files, with this setting more formats can be added
  362. on the fly or the used method can be changed. The syntax for this is:
  363. <synopsis>Acquire::CompressionTypes::<replaceable>FileExtension</replaceable> "<replaceable>Methodname</replaceable>";</synopsis>
  364. </para><para>Also the <literal>Order</literal> subgroup can be used to define in which order
  365. the acquire system will try to download the compressed files. The acquire system will try the first
  366. and proceed with the next compression type in this list on error, so to prefer one over the other type
  367. simple add the preferred type at first - not already added default types will be added at run time
  368. to the end of the list, so e.g. <synopsis>Acquire::CompressionTypes::Order:: "gz";</synopsis> can
  369. be used to prefer <command>gzip</command> compressed files over <command>bzip2</command> and <command>lzma</command>.
  370. If <command>lzma</command> should be preferred over <command>gzip</command> and <command>bzip2</command> the
  371. configure setting should look like this <synopsis>Acquire::CompressionTypes::Order { "lzma"; "gz"; };</synopsis>
  372. It is not needed to add <literal>bz2</literal> explicit to the list as it will be added automatic.</para>
  373. <para>Note that at run time the <literal>Dir::Bin::<replaceable>Methodname</replaceable></literal> will
  374. be checked: If this setting exists the method will only be used if this file exists, e.g. for
  375. the bzip2 method (the inbuilt) setting is <literallayout>Dir::Bin::bzip2 "/bin/bzip2";</literallayout>
  376. Note also that list entries specified on the command line will be added at the end of the list
  377. specified in the configuration files, but before the default entries. To prefer a type in this case
  378. over the ones specified in in the configuration files you can set the option direct - not in list style.
  379. This will not override the defined list, it will only prefix the list with this type.</para>
  380. <para>While it is possible to add an empty compression type to the order list, but APT in its current
  381. version doesn't understand it correctly and will display many warnings about not downloaded files -
  382. these warnings are most of the time false negatives. Future versions will maybe include a way to
  383. really prefer uncompressed files to support the usage of local mirrors.</para></listitem>
  384. </varlistentry>
  385. <varlistentry><term>Languages</term>
  386. <listitem><para>The Languages subsection controls which <filename>Translation</filename> files are downloaded
  387. and in which order APT tries to display the Description-Translations. APT will try to display the first
  388. available Description in the Language which is listed at first. Languages can be defined with their
  389. short or long Languagecodes. Note that not all archives provide <filename>Translation</filename>
  390. files for every Language - especially the long Languagecodes are rare, so please
  391. inform you which ones are available before you set here impossible values.</para>
  392. <para>The default list includes "environment" and "en". "<literal>environment</literal>" has a special meaning here:
  393. It will be replaced at runtime with the languagecodes extracted from the <literal>LC_MESSAGES</literal> environment variable.
  394. It will also ensure that these codes are not included twice in the list. If <literal>LC_MESSAGES</literal>
  395. is set to "C" only the <filename>Translation-en</filename> file (if available) will be used.
  396. To force apt to use no Translation file use the setting <literal>Acquire::Languages=none</literal>. "<literal>none</literal>"
  397. is another special meaning code which will stop the search for a fitting <filename>Translation</filename> file.
  398. This can be used by the system administrator to let APT know that it should download also this files without
  399. actually use them if the environment doesn't specify this languages. So the following example configuration will
  400. result in the order "en, de" in an english and in "de, en" in a german localization. Note that "fr" is downloaded,
  401. but not used if APT is not used in a french localization, in such an environment the order would be "fr, de, en".
  402. <programlisting>Acquire::Languages { "environment"; "de"; "en"; "none"; "fr"; };</programlisting></para></listitem>
  403. </varlistentry>
  404. </variablelist>
  405. </para>
  406. </refsect1>
  407. <refsect1><title>Directories</title>
  408. <para>The <literal>Dir::State</literal> section has directories that pertain to local
  409. state information. <literal>lists</literal> is the directory to place downloaded
  410. package lists in and <literal>status</literal> is the name of the dpkg status file.
  411. <literal>preferences</literal> is the name of the APT preferences file.
  412. <literal>Dir::State</literal> contains the default directory to prefix on all sub
  413. items if they do not start with <filename>/</filename> or <filename>./</filename>.</para>
  414. <para><literal>Dir::Cache</literal> contains locations pertaining to local cache
  415. information, such as the two package caches <literal>srcpkgcache</literal> and
  416. <literal>pkgcache</literal> as well as the location to place downloaded archives,
  417. <literal>Dir::Cache::archives</literal>. Generation of caches can be turned off
  418. by setting their names to be blank. This will slow down startup but
  419. save disk space. It is probably preferred to turn off the pkgcache rather
  420. than the srcpkgcache. Like <literal>Dir::State</literal> the default
  421. directory is contained in <literal>Dir::Cache</literal></para>
  422. <para><literal>Dir::Etc</literal> contains the location of configuration files,
  423. <literal>sourcelist</literal> gives the location of the sourcelist and
  424. <literal>main</literal> is the default configuration file (setting has no effect,
  425. unless it is done from the config file specified by
  426. <envar>APT_CONFIG</envar>).</para>
  427. <para>The <literal>Dir::Parts</literal> setting reads in all the config fragments in
  428. lexical order from the directory specified. After this is done then the
  429. main config file is loaded.</para>
  430. <para>Binary programs are pointed to by <literal>Dir::Bin</literal>. <literal>Dir::Bin::Methods</literal>
  431. specifies the location of the method handlers and <literal>gzip</literal>,
  432. <literal>bzip2</literal>, <literal>lzma</literal>,
  433. <literal>dpkg</literal>, <literal>apt-get</literal> <literal>dpkg-source</literal>
  434. <literal>dpkg-buildpackage</literal> and <literal>apt-cache</literal> specify the location
  435. of the respective programs.</para>
  436. <para>
  437. The configuration item <literal>RootDir</literal> has a special
  438. meaning. If set, all paths in <literal>Dir::</literal> will be
  439. relative to <literal>RootDir</literal>, <emphasis>even paths that
  440. are specified absolutely</emphasis>. So, for instance, if
  441. <literal>RootDir</literal> is set to
  442. <filename>/tmp/staging</filename> and
  443. <literal>Dir::State::status</literal> is set to
  444. <filename>/var/lib/dpkg/status</filename>, then the status file
  445. will be looked up in
  446. <filename>/tmp/staging/var/lib/dpkg/status</filename>.
  447. </para>
  448. </refsect1>
  449. <refsect1><title>APT in DSelect</title>
  450. <para>
  451. When APT is used as a &dselect; method several configuration directives
  452. control the default behaviour. These are in the <literal>DSelect</literal> section.</para>
  453. <variablelist>
  454. <varlistentry><term>Clean</term>
  455. <listitem><para>Cache Clean mode; this value may be one of always, prompt, auto,
  456. pre-auto and never. always and prompt will remove all packages from
  457. the cache after upgrading, prompt (the default) does so conditionally.
  458. auto removes only those packages which are no longer downloadable
  459. (replaced with a new version for instance). pre-auto performs this
  460. action before downloading new packages.</para></listitem>
  461. </varlistentry>
  462. <varlistentry><term>options</term>
  463. <listitem><para>The contents of this variable is passed to &apt-get; as command line
  464. options when it is run for the install phase.</para></listitem>
  465. </varlistentry>
  466. <varlistentry><term>Updateoptions</term>
  467. <listitem><para>The contents of this variable is passed to &apt-get; as command line
  468. options when it is run for the update phase.</para></listitem>
  469. </varlistentry>
  470. <varlistentry><term>PromptAfterUpdate</term>
  471. <listitem><para>If true the [U]pdate operation in &dselect; will always prompt to continue.
  472. The default is to prompt only on error.</para></listitem>
  473. </varlistentry>
  474. </variablelist>
  475. </refsect1>
  476. <refsect1><title>How APT calls dpkg</title>
  477. <para>Several configuration directives control how APT invokes &dpkg;. These are
  478. in the <literal>DPkg</literal> section.</para>
  479. <variablelist>
  480. <varlistentry><term>options</term>
  481. <listitem><para>This is a list of options to pass to dpkg. The options must be specified
  482. using the list notation and each list item is passed as a single argument
  483. to &dpkg;.</para></listitem>
  484. </varlistentry>
  485. <varlistentry><term>Pre-Invoke</term><term>Post-Invoke</term>
  486. <listitem><para>This is a list of shell commands to run before/after invoking &dpkg;.
  487. Like <literal>options</literal> this must be specified in list notation. The
  488. commands are invoked in order using <filename>/bin/sh</filename>, should any
  489. fail APT will abort.</para></listitem>
  490. </varlistentry>
  491. <varlistentry><term>Pre-Install-Pkgs</term>
  492. <listitem><para>This is a list of shell commands to run before invoking dpkg. Like
  493. <literal>options</literal> this must be specified in list notation. The commands
  494. are invoked in order using <filename>/bin/sh</filename>, should any fail APT
  495. will abort. APT will pass to the commands on standard input the
  496. filenames of all .deb files it is going to install, one per line.</para>
  497. <para>Version 2 of this protocol dumps more information, including the
  498. protocol version, the APT configuration space and the packages, files
  499. and versions being changed. Version 2 is enabled by setting
  500. <literal>DPkg::Tools::options::cmd::Version</literal> to 2. <literal>cmd</literal> is a
  501. command given to <literal>Pre-Install-Pkgs</literal>.</para></listitem>
  502. </varlistentry>
  503. <varlistentry><term>Run-Directory</term>
  504. <listitem><para>APT chdirs to this directory before invoking dpkg, the default is
  505. <filename>/</filename>.</para></listitem>
  506. </varlistentry>
  507. <varlistentry><term>Build-options</term>
  508. <listitem><para>These options are passed to &dpkg-buildpackage; when compiling packages,
  509. the default is to disable signing and produce all binaries.</para></listitem>
  510. </varlistentry>
  511. </variablelist>
  512. <refsect2><title>dpkg trigger usage (and related options)</title>
  513. <para>APT can call dpkg in a way so it can make aggressive use of triggers over
  514. multiply calls of dpkg. Without further options dpkg will use triggers only in between his
  515. own run. Activating these options can therefore decrease the time needed to perform the
  516. install / upgrade. Note that it is intended to activate these options per default in the
  517. future, but as it changes the way APT calling dpkg drastically it needs a lot more testing.
  518. <emphasis>These options are therefore currently experimental and should not be used in
  519. productive environments.</emphasis> Also it breaks the progress reporting so all frontends will
  520. currently stay around half (or more) of the time in the 100% state while it actually configures
  521. all packages.</para>
  522. <para>Note that it is not guaranteed that APT will support these options or that these options will
  523. not cause (big) trouble in the future. If you have understand the current risks and problems with
  524. these options, but are brave enough to help testing them create a new configuration file and test a
  525. combination of options. Please report any bugs, problems and improvements you encounter and make sure
  526. to note which options you have used in your reports. Asking dpkg for help could also be useful for
  527. debugging proposes, see e.g. <command>dpkg --audit</command>. A defensive option combination would be
  528. <literallayout>DPkg::NoTriggers "true";
  529. PackageManager::Configure "smart";
  530. DPkg::ConfigurePending "true";
  531. DPkg::TriggersPending "true";</literallayout></para>
  532. <variablelist>
  533. <varlistentry><term>DPkg::NoTriggers</term>
  534. <listitem><para>Add the no triggers flag to all dpkg calls (except the ConfigurePending call).
  535. See &dpkg; if you are interested in what this actually means. In short: dpkg will not run the
  536. triggers when this flag is present unless it is explicitly called to do so in an extra call.
  537. Note that this option exists (undocumented) also in older apt versions with a slightly different
  538. meaning: Previously these option only append --no-triggers to the configure calls to dpkg -
  539. now apt will add these flag also to the unpack and remove calls.</para></listitem>
  540. </varlistentry>
  541. <varlistentry><term>PackageManager::Configure</term>
  542. <listitem><para>Valid values are "<literal>all</literal>", "<literal>smart</literal>" and "<literal>no</literal>".
  543. "<literal>all</literal>" is the default value and causes APT to configure all packages explicit.
  544. The "<literal>smart</literal>" way is it to configure only packages which need to be configured before
  545. another package can be unpacked (Pre-Depends) and let the rest configure by dpkg with a call generated
  546. by the next option. "<literal>no</literal>" on the other hand will not configure anything and totally
  547. rely on dpkg for configuration (which will at the moment fail if a Pre-Depends is encountered).
  548. Setting this option to another than the all value will implicitly activate also the next option per
  549. default as otherwise the system could end in an unconfigured status which could be unbootable!
  550. </para></listitem>
  551. </varlistentry>
  552. <varlistentry><term>DPkg::ConfigurePending</term>
  553. <listitem><para>If this option is set apt will call <command>dpkg --configure --pending</command>
  554. to let dpkg handle all required configurations and triggers. This option is activated automatic
  555. per default if the previous option is not set to <literal>all</literal>, but deactivating could be useful
  556. if you want to run APT multiple times in a row - e.g. in an installer. In these sceneries you could
  557. deactivate this option in all but the last run.</para></listitem>
  558. </varlistentry>
  559. <varlistentry><term>DPkg::TriggersPending</term>
  560. <listitem><para>Useful for <literal>smart</literal> configuration as a package which has pending
  561. triggers is not considered as <literal>installed</literal> and dpkg treats them as <literal>unpacked</literal>
  562. currently which is a dealbreaker for Pre-Dependencies (see debbugs #526774). Note that this will
  563. process all triggers, not only the triggers needed to configure this package.</para></listitem>
  564. </varlistentry>
  565. <varlistentry><term>PackageManager::UnpackAll</term>
  566. <listitem><para>As the configuration can be deferred to be done at the end by dpkg it can be
  567. tried to order the unpack series only by critical needs, e.g. by Pre-Depends. Default is true
  568. and therefore the "old" method of ordering in various steps by everything. While both method
  569. were present in earlier APT versions the <literal>OrderCritical</literal> method was unused, so
  570. this method is very experimental and needs further improvements before becoming really useful.
  571. </para></listitem>
  572. </varlistentry>
  573. <varlistentry><term>OrderList::Score::Immediate</term>
  574. <listitem><para>Essential packages (and there dependencies) should be configured immediately
  575. after unpacking. It will be a good idea to do this quite early in the upgrade process as these
  576. these configure calls require currently also <literal>DPkg::TriggersPending</literal> which
  577. will run quite a few triggers (which maybe not needed). Essentials get per default a high score
  578. but the immediate flag is relatively low (a package which has a Pre-Depends is higher rated).
  579. These option and the others in the same group can be used to change the scoring. The following
  580. example shows the settings with there default values.
  581. <literallayout>OrderList::Score {
  582. Delete 500;
  583. Essential 200;
  584. Immediate 10;
  585. PreDepends 50;
  586. };</literallayout>
  587. </para></listitem>
  588. </varlistentry>
  589. </variablelist>
  590. </refsect2>
  591. </refsect1>
  592. <refsect1>
  593. <title>Periodic and Archives options</title>
  594. <para><literal>APT::Periodic</literal> and <literal>APT::Archives</literal>
  595. groups of options configure behavior of apt periodic updates, which is
  596. done by <literal>/etc/cron.daily/apt</literal> script. See header of
  597. this script for the brief documentation of these options.
  598. </para>
  599. </refsect1>
  600. <refsect1>
  601. <title>Debug options</title>
  602. <para>
  603. Enabling options in the <literal>Debug::</literal> section will
  604. cause debugging information to be sent to the standard error
  605. stream of the program utilizing the <literal>apt</literal>
  606. libraries, or enable special program modes that are primarily
  607. useful for debugging the behavior of <literal>apt</literal>.
  608. Most of these options are not interesting to a normal user, but a
  609. few may be:
  610. <itemizedlist>
  611. <listitem>
  612. <para>
  613. <literal>Debug::pkgProblemResolver</literal> enables output
  614. about the decisions made by
  615. <literal>dist-upgrade, upgrade, install, remove, purge</literal>.
  616. </para>
  617. </listitem>
  618. <listitem>
  619. <para>
  620. <literal>Debug::NoLocking</literal> disables all file
  621. locking. This can be used to run some operations (for
  622. instance, <literal>apt-get -s install</literal>) as a
  623. non-root user.
  624. </para>
  625. </listitem>
  626. <listitem>
  627. <para>
  628. <literal>Debug::pkgDPkgPM</literal> prints out the actual
  629. command line each time that <literal>apt</literal> invokes
  630. &dpkg;.
  631. </para>
  632. </listitem>
  633. <listitem>
  634. <para>
  635. <literal>Debug::IdentCdrom</literal> disables the inclusion
  636. of statfs data in CDROM IDs. <!-- TODO: provide a
  637. motivating example, except I haven't a clue why you'd want
  638. to do this. -->
  639. </para>
  640. </listitem>
  641. </itemizedlist>
  642. </para>
  643. <para>
  644. A full list of debugging options to apt follows.
  645. </para>
  646. <variablelist>
  647. <varlistentry>
  648. <term><literal>Debug::Acquire::cdrom</literal></term>
  649. <listitem>
  650. <para>
  651. Print information related to accessing
  652. <literal>cdrom://</literal> sources.
  653. </para>
  654. </listitem>
  655. </varlistentry>
  656. <varlistentry>
  657. <term><literal>Debug::Acquire::ftp</literal></term>
  658. <listitem>
  659. <para>
  660. Print information related to downloading packages using
  661. FTP.
  662. </para>
  663. </listitem>
  664. </varlistentry>
  665. <varlistentry>
  666. <term><literal>Debug::Acquire::http</literal></term>
  667. <listitem>
  668. <para>
  669. Print information related to downloading packages using
  670. HTTP.
  671. </para>
  672. </listitem>
  673. </varlistentry>
  674. <varlistentry>
  675. <term><literal>Debug::Acquire::https</literal></term>
  676. <listitem>
  677. <para>
  678. Print information related to downloading packages using
  679. HTTPS.
  680. </para>
  681. </listitem>
  682. </varlistentry>
  683. <varlistentry>
  684. <term><literal>Debug::Acquire::gpgv</literal></term>
  685. <listitem>
  686. <para>
  687. Print information related to verifying cryptographic
  688. signatures using <literal>gpg</literal>.
  689. </para>
  690. </listitem>
  691. </varlistentry>
  692. <varlistentry>
  693. <term><literal>Debug::aptcdrom</literal></term>
  694. <listitem>
  695. <para>
  696. Output information about the process of accessing
  697. collections of packages stored on CD-ROMs.
  698. </para>
  699. </listitem>
  700. </varlistentry>
  701. <varlistentry>
  702. <term><literal>Debug::BuildDeps</literal></term>
  703. <listitem>
  704. <para>
  705. Describes the process of resolving build-dependencies in
  706. &apt-get;.
  707. </para>
  708. </listitem>
  709. </varlistentry>
  710. <varlistentry>
  711. <term><literal>Debug::Hashes</literal></term>
  712. <listitem>
  713. <para>
  714. Output each cryptographic hash that is generated by the
  715. <literal>apt</literal> libraries.
  716. </para>
  717. </listitem>
  718. </varlistentry>
  719. <varlistentry>
  720. <term><literal>Debug::IdentCDROM</literal></term>
  721. <listitem>
  722. <para>
  723. Do not include information from <literal>statfs</literal>,
  724. namely the number of used and free blocks on the CD-ROM
  725. filesystem, when generating an ID for a CD-ROM.
  726. </para>
  727. </listitem>
  728. </varlistentry>
  729. <varlistentry>
  730. <term><literal>Debug::NoLocking</literal></term>
  731. <listitem>
  732. <para>
  733. Disable all file locking. For instance, this will allow
  734. two instances of <quote><literal>apt-get
  735. update</literal></quote> to run at the same time.
  736. </para>
  737. </listitem>
  738. </varlistentry>
  739. <varlistentry>
  740. <term><literal>Debug::pkgAcquire</literal></term>
  741. <listitem>
  742. <para>
  743. Log when items are added to or removed from the global
  744. download queue.
  745. </para>
  746. </listitem>
  747. </varlistentry>
  748. <varlistentry>
  749. <term><literal>Debug::pkgAcquire::Auth</literal></term>
  750. <listitem>
  751. <para>
  752. Output status messages and errors related to verifying
  753. checksums and cryptographic signatures of downloaded files.
  754. </para>
  755. </listitem>
  756. </varlistentry>
  757. <varlistentry>
  758. <term><literal>Debug::pkgAcquire::Diffs</literal></term>
  759. <listitem>
  760. <para>
  761. Output information about downloading and applying package
  762. index list diffs, and errors relating to package index list
  763. diffs.
  764. </para>
  765. </listitem>
  766. </varlistentry>
  767. <varlistentry>
  768. <term><literal>Debug::pkgAcquire::RRed</literal></term>
  769. <listitem>
  770. <para>
  771. Output information related to patching apt package lists
  772. when downloading index diffs instead of full indices.
  773. </para>
  774. </listitem>
  775. </varlistentry>
  776. <varlistentry>
  777. <term><literal>Debug::pkgAcquire::Worker</literal></term>
  778. <listitem>
  779. <para>
  780. Log all interactions with the sub-processes that actually
  781. perform downloads.
  782. </para>
  783. </listitem>
  784. </varlistentry>
  785. <varlistentry>
  786. <term><literal>Debug::pkgAutoRemove</literal></term>
  787. <listitem>
  788. <para>
  789. Log events related to the automatically-installed status of
  790. packages and to the removal of unused packages.
  791. </para>
  792. </listitem>
  793. </varlistentry>
  794. <varlistentry>
  795. <term><literal>Debug::pkgDepCache::AutoInstall</literal></term>
  796. <listitem>
  797. <para>
  798. Generate debug messages describing which packages are being
  799. automatically installed to resolve dependencies. This
  800. corresponds to the initial auto-install pass performed in,
  801. e.g., <literal>apt-get install</literal>, and not to the
  802. full <literal>apt</literal> dependency resolver; see
  803. <literal>Debug::pkgProblemResolver</literal> for that.
  804. </para>
  805. </listitem>
  806. </varlistentry>
  807. <varlistentry>
  808. <term><literal>Debug::pkgDepCache::Marker</literal></term>
  809. <listitem>
  810. <para>
  811. Generate debug messages describing which package is marked
  812. as keep/install/remove while the ProblemResolver does his work.
  813. Each addition or deletion may trigger additional actions;
  814. they are shown indented two additional space under the original entry.
  815. The format for each line is <literal>MarkKeep</literal>,
  816. <literal>MarkDelete</literal> or <literal>MarkInstall</literal> followed by
  817. <literal>package-name &lt;a.b.c -&gt; d.e.f | x.y.z&gt; (section)</literal>
  818. where <literal>a.b.c</literal> is the current version of the package,
  819. <literal>d.e.f</literal> is the version considered for installation and
  820. <literal>x.y.z</literal> is a newer version, but not considered for installation
  821. (because of a low pin score). The later two can be omitted if there is none or if
  822. it is the same version as the installed.
  823. <literal>section</literal> is the name of the section the package appears in.
  824. </para>
  825. </listitem>
  826. </varlistentry>
  827. <!-- Question: why doesn't this do anything? The code says it should. -->
  828. <varlistentry>
  829. <term><literal>Debug::pkgInitConfig</literal></term>
  830. <listitem>
  831. <para>
  832. Dump the default configuration to standard error on
  833. startup.
  834. </para>
  835. </listitem>
  836. </varlistentry>
  837. <varlistentry>
  838. <term><literal>Debug::pkgDPkgPM</literal></term>
  839. <listitem>
  840. <para>
  841. When invoking &dpkg;, output the precise command line with
  842. which it is being invoked, with arguments separated by a
  843. single space character.
  844. </para>
  845. </listitem>
  846. </varlistentry>
  847. <varlistentry>
  848. <term><literal>Debug::pkgDPkgProgressReporting</literal></term>
  849. <listitem>
  850. <para>
  851. Output all the data received from &dpkg; on the status file
  852. descriptor and any errors encountered while parsing it.
  853. </para>
  854. </listitem>
  855. </varlistentry>
  856. <varlistentry>
  857. <term><literal>Debug::pkgOrderList</literal></term>
  858. <listitem>
  859. <para>
  860. Generate a trace of the algorithm that decides the order in
  861. which <literal>apt</literal> should pass packages to
  862. &dpkg;.
  863. </para>
  864. </listitem>
  865. </varlistentry>
  866. <varlistentry>
  867. <term><literal>Debug::pkgPackageManager</literal></term>
  868. <listitem>
  869. <para>
  870. Output status messages tracing the steps performed when
  871. invoking &dpkg;.
  872. </para>
  873. </listitem>
  874. </varlistentry>
  875. <varlistentry>
  876. <term><literal>Debug::pkgPolicy</literal></term>
  877. <listitem>
  878. <para>
  879. Output the priority of each package list on startup.
  880. </para>
  881. </listitem>
  882. </varlistentry>
  883. <varlistentry>
  884. <term><literal>Debug::pkgProblemResolver</literal></term>
  885. <listitem>
  886. <para>
  887. Trace the execution of the dependency resolver (this
  888. applies only to what happens when a complex dependency
  889. problem is encountered).
  890. </para>
  891. </listitem>
  892. </varlistentry>
  893. <varlistentry>
  894. <term><literal>Debug::pkgProblemResolver::ShowScores</literal></term>
  895. <listitem>
  896. <para>
  897. Display a list of all installed packages with their calculated score
  898. used by the pkgProblemResolver. The description of the package
  899. is the same as described in <literal>Debug::pkgDepCache::Marker</literal>
  900. </para>
  901. </listitem>
  902. </varlistentry>
  903. <varlistentry>
  904. <term><literal>Debug::sourceList</literal></term>
  905. <listitem>
  906. <para>
  907. Print information about the vendors read from
  908. <filename>/etc/apt/vendors.list</filename>.
  909. </para>
  910. </listitem>
  911. </varlistentry>
  912. <!-- 2009/07/11 Currently used nowhere. The corresponding code
  913. is commented.
  914. <varlistentry>
  915. <term><literal>Debug::Vendor</literal></term>
  916. <listitem>
  917. <para>
  918. Print information about each vendor.
  919. </para>
  920. </listitem>
  921. </varlistentry>
  922. -->
  923. </variablelist>
  924. </refsect1>
  925. <refsect1><title>Examples</title>
  926. <para>&configureindex; is a
  927. configuration file showing example values for all possible
  928. options.</para>
  929. </refsect1>
  930. <refsect1><title>Files</title>
  931. <variablelist>
  932. &file-aptconf;
  933. </variablelist>
  934. </refsect1>
  935. <refsect1><title>See Also</title>
  936. <para>&apt-cache;, &apt-config;<!-- ? reading apt.conf -->, &apt-preferences;.</para>
  937. </refsect1>
  938. &manbugs;
  939. </refentry>