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.
 
 
 
 
 
 

675 lines
36 KiB

  1. <?xml version="1.0" encoding="utf-8" standalone="no"?>
  2. <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  4. <!ENTITY % aptent SYSTEM "apt.ent"> %aptent;
  5. <!ENTITY % aptverbatiment SYSTEM "apt-verbatim.ent"> %aptverbatiment;
  6. <!ENTITY % aptvendor SYSTEM "apt-vendor.ent"> %aptvendor;
  7. ]>
  8. <refentry>
  9. <refentryinfo>
  10. &apt-author.jgunthorpe;
  11. &apt-author.team;
  12. &apt-email;
  13. &apt-product;
  14. <!-- The last update date -->
  15. <date>2020-02-27T00:00:00Z</date>
  16. </refentryinfo>
  17. <refmeta>
  18. <refentrytitle>apt-get</refentrytitle>
  19. <manvolnum>8</manvolnum>
  20. <refmiscinfo class="manual">APT</refmiscinfo>
  21. </refmeta>
  22. <!-- Man page title -->
  23. <refnamediv>
  24. <refname>apt-get</refname>
  25. <refpurpose>APT package handling utility -- command-line interface</refpurpose>
  26. </refnamediv>
  27. &synopsis-command-apt-get;
  28. <refsect1><title>Description</title>
  29. <para><command>apt-get</command> is the command-line tool for handling packages, and may be
  30. considered the user's "back-end" to other tools using the APT
  31. library. Several "front-end" interfaces exist, such as
  32. &aptitude;, &synaptic; and &wajig;.</para>
  33. <para>Unless the <option>-h</option>, or <option>--help</option> option is given, one of the
  34. commands below must be present.</para>
  35. <variablelist>
  36. <varlistentry><term><option>update</option></term>
  37. <listitem><para><literal>update</literal> is used to resynchronize the package index files from
  38. their sources. The indexes of available packages are fetched from the
  39. location(s) specified in <filename>/etc/apt/sources.list</filename>.
  40. For example, when using a Debian archive, this command retrieves and
  41. scans the <filename>Packages.gz</filename> files, so that information about new
  42. and updated packages is available. An <literal>update</literal> should always be
  43. performed before an <literal>upgrade</literal> or <literal>dist-upgrade</literal>. Please
  44. be aware that the overall progress meter will be incorrect as the size
  45. of the package files cannot be known in advance.</para></listitem>
  46. </varlistentry>
  47. <varlistentry><term><option>upgrade</option></term>
  48. <listitem><para><literal>upgrade</literal> is used to install the newest versions of all packages
  49. currently installed on the system from the sources enumerated in
  50. <filename>/etc/apt/sources.list</filename>. Packages currently installed with
  51. new versions available are retrieved and upgraded; under no circumstances
  52. are currently installed packages removed, or packages not already installed
  53. retrieved and installed. New versions of currently installed packages that
  54. cannot be upgraded without changing the install status of another package
  55. will be left at their current version. An <literal>update</literal> must be
  56. performed first so that <command>apt-get</command> knows that new versions of packages are
  57. available.</para></listitem>
  58. </varlistentry>
  59. <varlistentry><term><option>dist-upgrade</option></term>
  60. <listitem><para><literal>dist-upgrade</literal> in addition to performing the function of
  61. <literal>upgrade</literal>, also intelligently handles changing dependencies
  62. with new versions of packages; <command>apt-get</command> has a "smart" conflict
  63. resolution system, and it will attempt to upgrade the most important
  64. packages at the expense of less important ones if necessary.
  65. The <literal>dist-upgrade</literal> command may therefore remove some packages.
  66. The <filename>/etc/apt/sources.list</filename> file contains a list of locations
  67. from which to retrieve desired package files.
  68. See also &apt-preferences; for a mechanism for
  69. overriding the general settings for individual packages.</para></listitem>
  70. </varlistentry>
  71. <varlistentry><term><option>dselect-upgrade</option></term>
  72. <listitem><para><literal>dselect-upgrade</literal>
  73. is used in conjunction with the traditional Debian packaging
  74. front-end, &dselect;. <literal>dselect-upgrade</literal>
  75. follows the changes made by &dselect; to the <literal>Status</literal>
  76. field of available packages, and performs the actions necessary to realize
  77. that state (for instance, the removal of old and the installation of new
  78. packages).</para></listitem>
  79. </varlistentry>
  80. <varlistentry><term><option>install</option></term>
  81. <listitem>
  82. <para><literal>install</literal> is followed by one or more
  83. packages desired for installation or upgrading.
  84. Each package is a package name, not a fully qualified
  85. filename (for instance, in a Debian system,
  86. <package>apt-utils</package> would be the argument provided, not
  87. <filename>apt-utils_&apt-product-version;_amd64.deb</filename>). All packages required
  88. by the package(s) specified for installation will also
  89. be retrieved and installed.
  90. The <filename>/etc/apt/sources.list</filename> file is
  91. used to locate the desired packages. If a hyphen is
  92. appended to the package name (with no intervening space),
  93. the identified package will be removed if it is installed.
  94. Similarly a plus sign can be used to designate a
  95. package to install. These latter features may be used
  96. to override decisions made by apt-get's conflict
  97. resolution system.
  98. </para>
  99. <para>A specific version of a package can be selected for installation by
  100. following the package name with an equals and the version of the package
  101. to select. This will cause that version to be located and selected for
  102. install. Alternatively a specific distribution can be selected by
  103. following the package name with a slash and the version of the
  104. distribution or the Archive name (stable, testing, unstable).</para>
  105. <para>Both of the version selection mechanisms can downgrade packages and must
  106. be used with care.</para>
  107. <para>This is also the target to use if you want to upgrade one or
  108. more already-installed packages without upgrading every package
  109. you have on your system. Unlike the "upgrade" target, which
  110. installs the newest version of all currently installed packages,
  111. "install" will install the newest version of only the package(s)
  112. specified. Simply provide the name of the package(s) you wish
  113. to upgrade, and if a newer version is available, it (and its
  114. dependencies, as described above) will be downloaded and
  115. installed.
  116. </para>
  117. <para>Finally, the &apt-preferences; mechanism allows you to
  118. create an alternative installation policy for
  119. individual packages.</para>
  120. <para>If no package matches the given expression and the expression contains one
  121. of '.', '?' or '*' then it is assumed to be a POSIX regular expression,
  122. and it is applied
  123. to all package names in the database. Any matches are then installed (or
  124. removed). Note that matching is done by substring so 'lo.*' matches 'how-lo'
  125. and 'lowest'. If this is undesired, anchor the regular expression
  126. with a '^' or '$' character, or create a more specific regular expression.</para>
  127. <para>Fallback to regular expressions is deprecated in APT 2.0, has been removed in
  128. &apt;, except for anchored expressions, and will be removed from &apt-get;
  129. in a future version. Use &apt-patterns; instead.</para></listitem>
  130. </varlistentry>
  131. <varlistentry><term><option>reinstall</option></term>
  132. <listitem><para><literal>reinstall</literal> is an alias for <literal>install --reinstall</literal>.</para></listitem>
  133. </varlistentry>
  134. <varlistentry><term><option>remove</option></term>
  135. <listitem><para><literal>remove</literal> is identical to <literal>install</literal> except that packages are
  136. removed instead of installed. Note that removing a package leaves its
  137. configuration files on the system. If a plus sign is appended to the package
  138. name (with no intervening space), the identified package will be
  139. installed instead of removed.</para></listitem>
  140. </varlistentry>
  141. <varlistentry><term><option>purge</option></term>
  142. <listitem><para><literal>purge</literal> is identical to <literal>remove</literal> except that packages are
  143. removed and purged (any configuration files are deleted too).</para></listitem>
  144. </varlistentry>
  145. <varlistentry><term><option>source</option></term>
  146. <listitem><para><literal>source</literal> causes <command>apt-get</command> to fetch source packages. APT
  147. will examine the available packages to decide which source package to
  148. fetch. It will then find and download into the current directory the
  149. newest available version of that source package while respecting the
  150. default release, set with the option <literal>APT::Default-Release</literal>,
  151. the <option>-t</option> option or per package with the
  152. <literal>pkg/release</literal> syntax, if possible.</para>
  153. <para>The arguments are interpreted as binary and source package names.
  154. See the <option>--only-source</option> option if you want to change that.</para>
  155. <para>Source packages are tracked separately
  156. from binary packages via <literal>deb-src</literal> lines
  157. in the &sources-list; file. This means that you will need to add such a line
  158. for each repository you want to get sources from; otherwise you will probably
  159. get either the wrong (too old/too new) source versions or none at all.</para>
  160. <para>If the <option>--compile</option> option is specified
  161. then the package will be compiled to a binary .deb using
  162. <command>dpkg-buildpackage</command> for the architecture as
  163. defined by the <command>--host-architecture</command> option.
  164. If <option>--download-only</option> is specified then the source package
  165. will not be unpacked.</para>
  166. <para>A specific source version can be retrieved by postfixing the source name
  167. with an equals and then the version to fetch, similar to the mechanism
  168. used for the package files. This enables exact matching of the source
  169. package name and version, implicitly enabling the
  170. <literal>APT::Get::Only-Source</literal> option.</para>
  171. <para>Note that source packages are not installed and tracked in the
  172. <command>dpkg</command> database like binary packages; they are simply downloaded
  173. to the current directory, like source tarballs.</para></listitem>
  174. </varlistentry>
  175. <varlistentry><term><option>build-dep</option></term>
  176. <listitem><para><literal>build-dep</literal> causes apt-get to install/remove packages in an
  177. attempt to satisfy the build dependencies for a source package. By default the dependencies are
  178. satisfied to build the package natively. If desired a host-architecture can be specified
  179. with the <option>--host-architecture</option> option instead.</para><para>The arguments are
  180. interpreted as binary or source package names. See the <option>--only-source</option>
  181. option if you want to change that.</para></listitem>
  182. </varlistentry>
  183. <varlistentry><term><option>satisfy</option></term>
  184. <listitem><para><literal>satisfy</literal> causes apt-get to satisfy the given dependency strings. The
  185. dependency strings may have build profiles and architecture restriction list as in build dependencies. They
  186. may optionally be prefixed with <literal>"Conflicts: "</literal> to unsatisfy the dependency string. Multiple strings of the same type can be specified.</para>
  187. <para>Example: <literal>apt-get satisfy "foo" "Conflicts: bar" "baz (&gt;&gt; 1.0) | bar (= 2.0), moo"</literal></para>
  188. <para>The legacy operator '&lt;/&gt;' is not supported, use '&lt;=/&gt;=' instead.</para>
  189. </listitem>
  190. </varlistentry>
  191. <varlistentry><term><option>check</option></term>
  192. <listitem><para><literal>check</literal> is a diagnostic tool; it updates the package cache and checks
  193. for broken dependencies.</para></listitem>
  194. </varlistentry>
  195. <varlistentry><term><option>download</option></term>
  196. <listitem><para><literal>download</literal> will download the given
  197. binary package into the current directory.
  198. </para></listitem>
  199. </varlistentry>
  200. <varlistentry><term><option>clean</option></term>
  201. <listitem><para><literal>clean</literal> clears out the local repository of retrieved package
  202. files. It removes everything but the lock file from
  203. <filename>&cachedir;/archives/</filename> and
  204. <filename>&cachedir;/archives/partial/</filename>.</para></listitem>
  205. </varlistentry>
  206. <varlistentry><term><option>autoclean</option> (and the <option>auto-clean</option> alias since 1.1)</term>
  207. <listitem><para>Like <literal>clean</literal>, <literal>autoclean</literal> clears out the local
  208. repository of retrieved package files. The difference is that it only
  209. removes package files that can no longer be downloaded, and are largely
  210. useless. This allows a cache to be maintained over a long period without
  211. it growing out of control. The configuration option
  212. <literal>APT::Clean-Installed</literal> will prevent installed packages from being
  213. erased if it is set to off.</para></listitem>
  214. </varlistentry>
  215. <varlistentry><term><option>autoremove</option> (and the <option>auto-remove</option> alias since 1.1)</term>
  216. <listitem><para><literal>autoremove</literal> is used to remove packages that were automatically
  217. installed to satisfy dependencies for other packages and are now no longer needed.</para></listitem>
  218. </varlistentry>
  219. <varlistentry><term><option>changelog</option></term>
  220. <listitem><para><literal>changelog</literal> tries to download the
  221. changelog of a package and displays it through
  222. <command>sensible-pager</command>. By default it
  223. displays the changelog for the version that is installed.
  224. However, you can specify the same options as for the
  225. <option>install</option> command.</para>
  226. </listitem>
  227. </varlistentry>
  228. <varlistentry><term><option>indextargets</option></term>
  229. <listitem><para>Displays by default a deb822 formatted listing of
  230. information about all data files (aka index targets) <command>apt-get
  231. update</command> would download. Supports a
  232. <option>--format</option> option to modify the output format as
  233. well as accepts lines of the default output to filter the records
  234. by. The command is mainly used as an interface for external tools
  235. working with APT to get information as well as filenames for
  236. downloaded files so they can use them as well instead of
  237. downloading them again on their own. Detailed documentation is
  238. omitted here and can instead be found in the file
  239. &apt-acquire-additional-files; shipped by the <package>apt-doc</package> package.
  240. </para>
  241. </listitem>
  242. </varlistentry>
  243. </variablelist>
  244. </refsect1>
  245. <refsect1><title>options</title>
  246. &apt-cmdblurb;
  247. <variablelist>
  248. <varlistentry><term><option>--no-install-recommends</option></term>
  249. <listitem><para>Do not consider recommended packages as a dependency for installing.
  250. Configuration Item: <literal>APT::Install-Recommends</literal>.</para></listitem>
  251. </varlistentry>
  252. <varlistentry><term><option>--install-suggests</option></term>
  253. <listitem><para>Consider suggested packages as a dependency for installing.
  254. Configuration Item: <literal>APT::Install-Suggests</literal>.</para></listitem>
  255. </varlistentry>
  256. <varlistentry><term><option>-d</option></term><term><option>--download-only</option></term>
  257. <listitem><para>Download only; package files are only retrieved, not unpacked or installed.
  258. Configuration Item: <literal>APT::Get::Download-Only</literal>.</para></listitem>
  259. </varlistentry>
  260. <varlistentry><term><option>-f</option></term><term><option>--fix-broken</option></term>
  261. <listitem><para>Fix; attempt to correct a system with broken dependencies in
  262. place. This option, when used with install/remove, can omit any packages
  263. to permit APT to deduce a likely solution. If packages are specified,
  264. these have to completely correct the problem. The option is sometimes necessary when
  265. running APT for the first time; APT itself does not allow broken package
  266. dependencies to exist on a system. It is possible that a system's
  267. dependency structure can be so corrupt as to require manual intervention
  268. (which usually means using <command>dpkg --remove</command> to eliminate some of
  269. the offending packages). Use of this option together with <option>-m</option> may produce an
  270. error in some situations.
  271. Configuration Item: <literal>APT::Get::Fix-Broken</literal>.</para></listitem>
  272. </varlistentry>
  273. <varlistentry><term><option>-m</option></term><term><option>--ignore-missing</option></term>
  274. <term><option>--fix-missing</option></term>
  275. <listitem><para>Ignore missing packages; if packages cannot be retrieved or fail the
  276. integrity check after retrieval (corrupted package files), hold back
  277. those packages and handle the result. Use of this option together with
  278. <option>-f</option> may produce an error in some situations. If a package is
  279. selected for installation (particularly if it is mentioned on the
  280. command line) and it could not be downloaded then it will be silently
  281. held back.
  282. Configuration Item: <literal>APT::Get::Fix-Missing</literal>.</para></listitem>
  283. </varlistentry>
  284. <varlistentry><term><option>--no-download</option></term>
  285. <listitem><para>Disables downloading of packages. This is best used with
  286. <option>--ignore-missing</option> to force APT to use only the .debs it has
  287. already downloaded.
  288. Configuration Item: <literal>APT::Get::Download</literal>.</para></listitem>
  289. </varlistentry>
  290. <varlistentry><term><option>-q</option></term><term><option>--quiet</option></term>
  291. <listitem><para>Quiet; produces output suitable for logging, omitting progress indicators.
  292. More q's will produce more quiet up to a maximum of 2. You can also use
  293. <option>-q=#</option> to set the quiet level, overriding the configuration file.
  294. Note that quiet level 2 implies <option>-y</option>; you should never use -qq
  295. without a no-action modifier such as -d, --print-uris or -s as APT may
  296. decide to do something you did not expect.
  297. Configuration Item: <literal>quiet</literal>.</para></listitem>
  298. </varlistentry>
  299. <varlistentry><term><option>-s</option></term>
  300. <term><option>--simulate</option></term>
  301. <term><option>--just-print</option></term>
  302. <term><option>--dry-run</option></term>
  303. <term><option>--recon</option></term>
  304. <term><option>--no-act</option></term>
  305. <listitem><para>No action; perform a simulation of events that would occur
  306. based on the current system state but do not actually change the
  307. system. Locking will be disabled (<option>Debug::NoLocking</option>)
  308. so the system state could change while <command>apt-get</command> is
  309. running. Simulations can also be executed by non-root users which might
  310. not have read access to all apt configuration distorting the simulation.
  311. A notice expressing this warning is also shown by default for non-root
  312. users (<option>APT::Get::Show-User-Simulation-Note</option>).
  313. Configuration Item: <literal>APT::Get::Simulate</literal>.</para>
  314. <para>Simulated runs print out a series of lines, each representing a <command>dpkg</command>
  315. operation: configure (<literal>Conf</literal>), remove (<literal>Remv</literal>)
  316. or unpack (<literal>Inst</literal>). Square brackets indicate broken packages, and
  317. empty square brackets indicate breaks that are of no consequence (rare).</para></listitem>
  318. </varlistentry>
  319. <varlistentry><term><option>-y</option></term><term><option>--yes</option></term>
  320. <term><option>--assume-yes</option></term>
  321. <listitem><para>Automatic yes to prompts; assume "yes" as answer to all prompts and run
  322. non-interactively. If an undesirable situation, such as changing a held
  323. package, trying to install an unauthenticated package or removing an essential package
  324. occurs then <literal>apt-get</literal> will abort.
  325. Configuration Item: <literal>APT::Get::Assume-Yes</literal>.</para></listitem>
  326. </varlistentry>
  327. <varlistentry><term><option>--assume-no</option></term>
  328. <listitem><para>Automatic "no" to all prompts.
  329. Configuration Item: <literal>APT::Get::Assume-No</literal>.</para></listitem>
  330. </varlistentry>
  331. <varlistentry><term><option>--no-show-upgraded</option></term>
  332. <listitem><para>Do not show a list of all packages that are to be upgraded.
  333. Configuration Item: <literal>APT::Get::Show-Upgraded</literal>.</para></listitem>
  334. </varlistentry>
  335. <varlistentry><term><option>-V</option></term><term><option>--verbose-versions</option></term>
  336. <listitem><para>Show full versions for upgraded and installed packages.
  337. Configuration Item: <literal>APT::Get::Show-Versions</literal>.</para></listitem>
  338. </varlistentry>
  339. <varlistentry><term><option>-a</option></term>
  340. <term><option>--host-architecture</option></term>
  341. <listitem><para>This option controls the architecture packages are built for
  342. by <command>apt-get source --compile</command> and how cross-builddependencies
  343. are satisfied. By default is it not set which means that the host architecture
  344. is the same as the build architecture (which is defined by <literal>APT::Architecture</literal>).
  345. Configuration Item: <literal>APT::Get::Host-Architecture</literal>.
  346. </para></listitem>
  347. </varlistentry>
  348. <varlistentry><term><option>-P</option></term>
  349. <term><option>--build-profiles</option></term>
  350. <listitem><para>This option controls the activated build profiles for which
  351. a source package is built by <command>apt-get source --compile</command> and
  352. how build dependencies are satisfied. By default no build profile is active.
  353. More than one build profile can be activated at a time by concatenating them
  354. with a comma.
  355. Configuration Item: <literal>APT::Build-Profiles</literal>.
  356. </para></listitem>
  357. </varlistentry>
  358. <varlistentry><term><option>-b</option></term><term><option>--compile</option></term>
  359. <term><option>--build</option></term>
  360. <listitem><para>Compile source packages after downloading them.
  361. Configuration Item: <literal>APT::Get::Compile</literal>.</para></listitem>
  362. </varlistentry>
  363. <varlistentry><term><option>--ignore-hold</option></term>
  364. <listitem><para>Ignore package holds; this causes <command>apt-get</command> to ignore a hold
  365. placed on a package. This may be useful in conjunction with
  366. <literal>dist-upgrade</literal> to override a large number of undesired holds.
  367. Configuration Item: <literal>APT::Ignore-Hold</literal>.</para></listitem>
  368. </varlistentry>
  369. <varlistentry><term><option>--with-new-pkgs</option></term>
  370. <listitem><para>Allow installing new packages when used in
  371. conjunction with <literal>upgrade</literal>. This is useful if
  372. the update of an installed package requires new dependencies to be
  373. installed. Instead of holding the package back <literal>upgrade</literal>
  374. will upgrade the package and install the new dependencies. Note that
  375. <literal>upgrade</literal> with this option will never remove packages,
  376. only allow adding new ones.
  377. Configuration Item: <literal>APT::Get::Upgrade-Allow-New</literal>.
  378. </para></listitem>
  379. </varlistentry>
  380. <varlistentry><term><option>--no-upgrade</option></term>
  381. <listitem><para>Do not upgrade packages; when used in conjunction with <literal>install</literal>,
  382. <literal>no-upgrade</literal> will prevent packages on the command line
  383. from being upgraded if they are already installed.
  384. Configuration Item: <literal>APT::Get::Upgrade</literal>.</para></listitem>
  385. </varlistentry>
  386. <varlistentry><term><option>--only-upgrade</option></term>
  387. <listitem><para>Do not install new packages; when used in conjunction
  388. with <literal>install</literal>, <literal>only-upgrade</literal> will
  389. install upgrades for already installed packages only and ignore requests
  390. to install new packages.
  391. Configuration Item: <literal>APT::Get::Only-Upgrade</literal>.</para></listitem>
  392. </varlistentry>
  393. <varlistentry><term><option>--allow-downgrades</option></term>
  394. <listitem><para>This is a dangerous option that will cause apt to continue
  395. without prompting if it is doing downgrades. It
  396. should not be used except in very special situations. Using
  397. it can potentially destroy your system!
  398. Configuration Item: <literal>APT::Get::allow-downgrades</literal>. Introduced in APT 1.1.</para></listitem>
  399. </varlistentry>
  400. <varlistentry><term><option>--allow-remove-essential</option></term>
  401. <listitem><para>Force yes; this is a dangerous option that will cause apt to continue
  402. without prompting if it is removing essentials. It
  403. should not be used except in very special situations. Using
  404. it can potentially destroy your system!
  405. Configuration Item: <literal>APT::Get::allow-remove-essential</literal>. Introduced in APT 1.1.</para></listitem>
  406. </varlistentry>
  407. <varlistentry><term><option>--allow-change-held-packages</option></term>
  408. <listitem><para>Force yes; this is a dangerous option that will cause apt to continue
  409. without prompting if it is changing held packages. It
  410. should not be used except in very special situations. Using
  411. it can potentially destroy your system!
  412. Configuration Item: <literal>APT::Get::allow-change-held-packages</literal>. Introduced in APT 1.1.</para></listitem>
  413. </varlistentry>
  414. <varlistentry><term><option>--force-yes</option></term>
  415. <listitem><para>Force yes; this is a dangerous option that will cause apt to continue
  416. without prompting if it is doing something potentially harmful. It
  417. should not be used except in very special situations. Using
  418. <literal>force-yes</literal> can potentially destroy your system!
  419. Configuration Item: <literal>APT::Get::force-yes</literal>. This is deprecated and replaced by
  420. <option>--allow-unauthenticated</option>
  421. , <option>--allow-downgrades</option>
  422. , <option>--allow-remove-essential</option>
  423. , <option>--allow-change-held-packages</option> in 1.1. </para></listitem>
  424. </varlistentry>
  425. <varlistentry><term><option>--print-uris</option></term>
  426. <listitem><para>Instead of fetching the files to install their URIs are printed. Each
  427. URI will have the path, the destination file name, the size and the expected
  428. MD5 hash. Note that the file name to write to will not always match
  429. the file name on the remote site! This also works with the
  430. <literal>source</literal> and <literal>update</literal> commands. When used with the
  431. <literal>update</literal> command the MD5 and size are not included, and it is
  432. up to the user to decompress any compressed files.
  433. Configuration Item: <literal>APT::Get::Print-URIs</literal>.</para></listitem>
  434. </varlistentry>
  435. <varlistentry><term><option>--purge</option></term>
  436. <listitem><para>Use purge instead of remove for anything that would be removed.
  437. An asterisk ("*") will be displayed next to packages which are
  438. scheduled to be purged. <option>remove --purge</option> is equivalent to the
  439. <option>purge</option> command.
  440. Configuration Item: <literal>APT::Get::Purge</literal>.</para></listitem>
  441. </varlistentry>
  442. <varlistentry><term><option>--reinstall</option></term>
  443. <listitem><para>Re-install packages that are already installed and at the newest version.
  444. Configuration Item: <literal>APT::Get::ReInstall</literal>.</para></listitem>
  445. </varlistentry>
  446. <varlistentry><term><option>--list-cleanup</option></term>
  447. <listitem><para>This option is on by default; use <literal>--no-list-cleanup</literal> to turn
  448. it off. When it is on, <command>apt-get</command> will automatically manage the contents
  449. of <filename>&statedir;/lists</filename> to ensure that obsolete files are erased.
  450. The only reason to turn it off is if you frequently change your sources list.
  451. Configuration Item: <literal>APT::Get::List-Cleanup</literal>.</para></listitem>
  452. </varlistentry>
  453. <varlistentry><term><option>-t</option></term>
  454. <term><option>--target-release</option></term>
  455. <term><option>--default-release</option></term>
  456. <listitem><para>This option controls the default input to the policy engine; it creates
  457. a default pin at priority 990 using the specified release string.
  458. This overrides the general settings in <filename>/etc/apt/preferences</filename>.
  459. Specifically pinned packages are not affected by the value
  460. of this option. In short, this option
  461. lets you have simple control over which distribution packages will be
  462. retrieved from. Some common examples might be
  463. <option>-t '2.1*'</option>, <option>-t unstable</option>
  464. or <option>-t sid</option>.
  465. Configuration Item: <literal>APT::Default-Release</literal>;
  466. see also the &apt-preferences; manual page.</para></listitem>
  467. </varlistentry>
  468. <varlistentry><term><option>--trivial-only</option></term>
  469. <listitem><para>
  470. Only perform operations that are 'trivial'. Logically this can be considered
  471. related to <option>--assume-yes</option>; where <option>--assume-yes</option> will answer
  472. yes to any prompt, <option>--trivial-only</option> will answer no.
  473. Configuration Item: <literal>APT::Get::Trivial-Only</literal>.</para></listitem>
  474. </varlistentry>
  475. <varlistentry><term><option>--mark-auto</option></term>
  476. <listitem><para>
  477. After successful installation, mark all freshly installed packages as
  478. automatically installed, which will cause each of the packages to be
  479. removed when no more manually installed packages depend on this package.
  480. This is equally to running <command>apt-mark auto</command> for all
  481. installed packages.
  482. Configuration Item: <literal>APT::Get::Mark-Auto</literal>.</para></listitem>
  483. </varlistentry>
  484. <varlistentry><term><option>--no-remove</option></term>
  485. <listitem><para>If any packages are to be removed apt-get immediately aborts without
  486. prompting.
  487. Configuration Item: <literal>APT::Get::Remove</literal>.</para></listitem>
  488. </varlistentry>
  489. <varlistentry><term><option>--auto-remove</option></term><term><option>--autoremove</option></term>
  490. <listitem><para>If the command is either <literal>install</literal> or <literal>remove</literal>,
  491. then this option acts like running the <literal>autoremove</literal> command, removing unused
  492. dependency packages. Configuration Item: <literal>APT::Get::AutomaticRemove</literal>.
  493. </para></listitem>
  494. </varlistentry>
  495. <varlistentry><term><option>--only-source</option></term>
  496. <listitem><para>Only has meaning for the
  497. <literal>source</literal> and <literal>build-dep</literal>
  498. commands. Indicates that the given source names are not to be
  499. mapped through the binary table. This means that if this option
  500. is specified, these commands will only accept source package
  501. names as arguments, rather than accepting binary package names
  502. and looking up the corresponding source package. Configuration
  503. Item: <literal>APT::Get::Only-Source</literal>.</para></listitem>
  504. </varlistentry>
  505. <varlistentry><term><option>--diff-only</option></term><term><option>--dsc-only</option></term><term><option>--tar-only</option></term>
  506. <listitem><para>Download only the diff, dsc, or tar file of a source archive.
  507. Configuration Item: <literal>APT::Get::Diff-Only</literal>, <literal>APT::Get::Dsc-Only</literal>, and
  508. <literal>APT::Get::Tar-Only</literal>.</para></listitem>
  509. </varlistentry>
  510. <varlistentry><term><option>--arch-only</option></term>
  511. <listitem><para>Only process architecture-dependent build-dependencies.
  512. Configuration Item: <literal>APT::Get::Arch-Only</literal>.</para></listitem>
  513. </varlistentry>
  514. <varlistentry><term><option>--indep-only</option></term>
  515. <listitem><para>Only process architecture-independent build-dependencies.
  516. Configuration Item: <literal>APT::Get::Indep-Only</literal>.</para></listitem>
  517. </varlistentry>
  518. <varlistentry><term><option>--allow-unauthenticated</option></term>
  519. <listitem><para>Ignore if packages can't be authenticated and don't prompt
  520. about it. This can be useful while working with local repositories,
  521. but is a huge security risk if data authenticity isn't ensured in
  522. another way by the user itself. The usage of the
  523. <option>Trusted</option> option for &sources-list; entries should
  524. usually be preferred over this global override. Configuration Item:
  525. <literal>APT::Get::AllowUnauthenticated</literal>.</para></listitem>
  526. </varlistentry>
  527. <varlistentry><term><option>--no-allow-insecure-repositories</option></term>
  528. <listitem><para>Forbid the update command to acquire unverifiable
  529. data from configured sources. APT will fail at the update command
  530. for repositories without valid cryptographically signatures. See
  531. also &apt-secure; for details on the concept and the implications.
  532. Configuration Item: <literal>Acquire::AllowInsecureRepositories</literal>.</para></listitem>
  533. </varlistentry>
  534. <varlistentry><term><option>--allow-releaseinfo-change</option></term>
  535. <listitem><para>Allow the update command to continue downloading
  536. data from a repository which changed its information of the release
  537. contained in the repository indicating e.g a new major release.
  538. APT will fail at the update command for such repositories until the
  539. change is confirmed to ensure the user is prepared for the change.
  540. See also &apt-secure; for details on the concept and configuration.
  541. </para><para>
  542. Specialist options
  543. (<literal>--allow-releaseinfo-change-</literal><replaceable>field</replaceable>)
  544. exist to allow changes only for certain fields like <literal>origin</literal>,
  545. <literal>label</literal>, <literal>codename</literal>, <literal>suite</literal>,
  546. <literal>version</literal> and <literal>defaultpin</literal>. See also &apt-preferences;.
  547. Configuration Item: <literal>Acquire::AllowReleaseInfoChange</literal>.</para></listitem>
  548. </varlistentry>
  549. <varlistentry><term><option>--show-progress</option></term>
  550. <listitem><para>Show user friendly progress information in the
  551. terminal window when packages are installed, upgraded or
  552. removed. For a machine parsable version of this data see
  553. README.progress-reporting in the apt doc directory.
  554. Configuration Items: <literal>Dpkg::Progress</literal> and <literal>Dpkg::Progress-Fancy</literal>.</para></listitem>
  555. </varlistentry>
  556. <varlistentry><term><option>--with-source</option> <option>&synopsis-param-filename;</option></term>
  557. <listitem><para>
  558. Adds the given file as a source for metadata. Can be repeated to add multiple files.
  559. See <option>--with-source</option> description in &apt-cache; for further details.
  560. </para></listitem>
  561. </varlistentry>
  562. &apt-commonoptions;
  563. </variablelist>
  564. </refsect1>
  565. <refsect1><title>Files</title>
  566. <variablelist>
  567. &file-sourceslist;
  568. &file-aptconf;
  569. &file-preferences;
  570. &file-cachearchives;
  571. &file-statelists;
  572. </variablelist>
  573. </refsect1>
  574. <refsect1><title>See Also</title>
  575. <para>&apt-cache;, &apt-cdrom;, &dpkg;, &sources-list;,
  576. &apt-conf;, &apt-config;, &apt-secure;,
  577. The APT User's guide in &guidesdir;, &apt-preferences;, the APT Howto.</para>
  578. </refsect1>
  579. <refsect1><title>Diagnostics</title>
  580. <para><command>apt-get</command> returns zero on normal operation, decimal 100 on error.</para>
  581. </refsect1>
  582. &manbugs;
  583. </refentry>