apt-get.8.xml 29 KB

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