File Manager

Editing File: /usr/share/doc/aptitude/html/en/rn01re01.html

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>aptitude</title><link rel="stylesheet" type="text/css" href="aptitude.css" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="home" href="index.html" title="aptitude user's manual" /><link rel="up" href="rn01.html" title="Command-line reference" /><link rel="prev" href="rn01.html" title="Command-line reference" /><link rel="next" href="rn01re02.html" title="aptitude-create-state-bundle" /><link rel="preface" href="pr01.html" title="Introduction" /><link rel="chapter" href="ch01.html" title="Chapter 1. Getting started" /><link rel="chapter" href="ch02.html" title="Chapter 2. aptitude reference guide" /><link rel="chapter" href="ch03.html" title="Chapter 3. aptitude frequently asked questions" /><link rel="chapter" href="ch04.html" title="Chapter 4. Credits" /><link rel="reference" href="rn01.html" title="Command-line reference" /><link rel="refentry" href="rn01re01.html" title="aptitude" /><link rel="refentry" href="rn01re02.html" title="aptitude-create-state-bundle" /><link rel="refentry" href="rn01re03.html" title="aptitude-run-state-bundle" /><link rel="section" href="rn01re01.html#idm8352" title="Description" /><link rel="section" href="rn01re01.html#idm8357" title="Command-line actions" /><link rel="section" href="rn01re01.html#idm8899" title="Options" /><link rel="section" href="rn01re01.html#idm9679" title="Environment" /><link rel="section" href="rn01re01.html#idm9722" title="Files" /><link rel="section" href="rn01re01.html#idm9744" title="See also" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">aptitude</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rn01.html"><img src="images/prev.gif" alt="Prev" /></a> </td><th width="60%" align="center">Command-line reference</th><td width="20%" align="right"> <a accesskey="n" href="rn01re02.html"><img src="images/next.gif" alt="Next" /></a></td></tr></table><hr /></div><div class="refentry"><a id="idm8243"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2>aptitude — high-level interface to the package manager</div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><code class="command">aptitude</code> [<code>options</code>...] { autoclean | clean | forget-new | keep-all | update }</div><div class="cmdsynopsis"><code class="command">aptitude</code> [<code>options</code>...] { full-upgrade | safe-upgrade } [<code>packages</code>...]</div><div class="cmdsynopsis"><code class="command">aptitude</code> [<code>options</code>...] { build-dep | build-depends | changelog | download | forbid-version | hold | install | markauto | purge | reinstall | remove | show | showsrc | source | unhold | unmarkauto | versions } <code>packages</code>... </div><div class="cmdsynopsis"><code class="command">aptitude</code> extract-cache-subset <code>output-directory</code> <code>packages</code>... </div><div class="cmdsynopsis"><code class="command">aptitude</code> [<code>options</code>...] search <code>patterns</code>... </div><div class="cmdsynopsis"><code class="command">aptitude</code> [<code>options</code>...] { add-user-tag | remove-user-tag } <code>tag</code> <code>packages</code>... </div><div class="cmdsynopsis"><code class="command">aptitude</code> [<code>options</code>...] { why | why-not } [<code>patterns</code>...] <code>package</code> </div><div class="cmdsynopsis"><code class="command">aptitude</code> [-S <code>fname</code>] [ --autoclean-on-startup | --clean-on-startup | -i | -u ]</div><div class="cmdsynopsis"><code class="command">aptitude</code> help </div></div><div class="refsect1"><a id="idm8352"></a><h2>Description</h2>
 aptitude is a text-based interface to the Debian GNU/Linux
 package system.
 
 It allows the user to view the list of packages and to
 perform package management tasks such as installing,
 upgrading, and removing packages. Actions may be performed
 from a visual interface or from the command-line.
 </div><div class="refsect1"><a id="idm8357"></a><h2>Command-line actions</h2>
 The first argument which does not begin with a hyphen (“<code class="literal">-</code>”)
 is considered to be an action that the program should
 perform. If an action is not specified on the command-line,
 aptitude will start up in visual mode.
 
 The following actions are available:
 <div class="variablelist"><dl class="variablelist"><dt><a id="cmdlineInstall"></a><code class="literal">install</code></dt><dd>
	 Install one or more packages. The packages should be
	 listed after the “install” command; if a
	 package name contains a tilde character
	 (“<code class="literal">~</code>”) or a question mark
	 (“<code class="literal">?</code>”), it will be treated
	 as a search pattern and every package matching the pattern
	 will be installed (see the section <a class="link" href="ch02s04.html" title="Search patterns">“Search
	 Patterns”</a> in the aptitude reference
	 manual).
	 
	 To select a particular version of the package, append “<code class="literal">=<code>version</code></code>”
	 to the package name: for instance, “<code class="literal">aptitude install
	 apt=0.3.1</code>”. Similarly, to select a
	 package from a particular archive, append “<code class="literal">/<code>archive</code></code>”
	 to the package name: for instance, “<code class="literal">aptitude install
	 apt/experimental</code>”. You cannot specify both an archive and a version for a package.
	 <a id="parOverrideSpecifiers"></a>
	 Not every package listed on the command line has to be
	 installed; you can tell aptitude to do something
	 different with a package by appending an “override
	 specifier” to the name of the package. For
	 example, <code class="literal">aptitude remove wesnoth+</code> will
	 install <code class="literal">wesnoth</code>, not remove it. The
	 following override specifiers are available:
	 <div class="variablelist"><dl class="variablelist"><dt><code>package</code><code class="literal">+</code></dt><dd>
		 Install <code>package</code>.
		
		 If the package was not installed, it is marked as manually
		 installed, and the dependencies newly installed are marked
		 with the automatic flag. If the package or the dependencies
		 were already installed, the automatic flag is preserved. See
		 the <a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">section about automatic
		 installations</a> in the documentation for more
		 information.
		</dd><dt><code>package</code><code class="literal">+M</code></dt><dd>
		 Install <code>package</code> and
		 immediately mark it as <a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">automatically
		 installed</a> (note that if nothing depends on
		 <code>package</code>, this will cause
		 it to be immediately removed).
		</dd><dt><code>package</code><code class="literal">-</code></dt><dd>
		 Remove <code>package</code>.
		</dd><dt><code>package</code><code class="literal">_</code></dt><dd>
		 Purge <code>package</code>: remove it
		 and all its associated configuration and data files.
		</dd><dt><code>package</code><code class="literal">=</code></dt><dd>
		 Place <code>package</code> on hold:
		 cancel any active installation, upgrade, or removal,
		 and prevent this package from being automatically
		 upgraded in the future.
		</dd><dt><code>package</code><code class="literal">:</code></dt><dd>
		 Keep <code>package</code> at its
		 current version: cancel any installation, removal,
		 or upgrade. Unlike “hold” (above) this
		 does not prevent automatic upgrades in the future.
		</dd><dt><code>package</code><code class="literal">&amp;M</code></dt><dd>
		 Mark <code>package</code> as having
		 been <a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">automatically installed</a>.
		</dd><dt><code>package</code><code class="literal">&amp;m</code></dt><dd>
		 Mark <code>package</code> as having
		 been <a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">manually installed</a>.
		</dd><dt><code>package</code><code class="literal">&amp;BD</code></dt><dd>
		 Install the build-dependencies of a
		 <code>package</code>.
		</dd></dl></div>
	 As a special case, “<code class="literal">install</code>” with no
	 arguments will act on any stored/pending actions.
	 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top">
	 Once you enter <code>Y</code> at the final
	 confirmation prompt, the
	 “<code class="literal">install</code>” command will
	 modify aptitude's stored information about what
	 actions to perform. Therefore, if you issue (e.g.) the
	 command “<code class="literal">aptitude install foo
	 bar</code>” on packages previously uninstalled,
	 and then the installation fails once aptitude has started
	 downloading and installing packages, you will need to run
	 “<code class="literal">aptitude remove foo bar</code>” to go
	 back to the previous state (and possibly undo installations or
	 upgrades to other packages that were affected by the
	 “<code class="literal">install</code>” action).
	 </td></tr></table></div></dd><dt><code class="literal">remove</code>, <code class="literal">purge</code>, <code class="literal">reinstall</code></dt><dd>
	 These commands are the same as
	 “<code class="literal">install</code>”, but apply the
	 named action to all packages given on the command line for
	 which it is not <a class="link" href="rn01re01.html#parOverrideSpecifiers">overridden</a>.
	 
	 For instance, “<code class="literal">aptitude remove
	 '~ndeity'</code>” will remove all packages
	 whose name contains “<code class="literal">deity</code>”.
	 </dd><dt><code class="literal">build-depends</code>, <code class="literal">build-dep</code></dt><dd>
	 Satisfy the build-dependencies of a package. Each package
	 name may be a source package, in which case the build
	 dependencies of that source package are installed;
	 otherwise, binary packages are found in the same way as
	 for the “<code class="literal">install</code>” command,
	 and the build-dependencies of the source packages that
	 build those binary packages are satisfied.
	 
	 If the command-line parameter
	 <code class="literal">--arch-only</code> is present, only
	 architecture-dependent build dependencies (i.e., not
	 <code class="literal">Build-Depends-Indep</code> or
	 <code class="literal">Build-Conflicts-Indep</code>) will be
	 obeyed.
	 </dd><dt><code class="literal">markauto</code>, <code class="literal">unmarkauto</code></dt><dd>
	 Mark packages as automatically installed or manually
	 installed, respectively. Packages are specified in
	 exactly the same way as for the “<code class="literal">install</code>” command.
	 For instance, “<code class="literal">aptitude markauto
	 '~slibs'</code>” will mark all packages in
	 the “<code class="literal">libs</code>” section as
	 having been automatically installed.
	 
	 For more information on automatically installed
	 packages, see the section “<a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">Managing Automatically
	 Installed Packages</a>” in the aptitude
	 reference manual.
	 </dd><dt><code class="literal">hold</code>, <code class="literal">unhold</code>, <code class="literal">keep</code></dt><dd>
	 Mark packages to be on hold, remove this property, or set to keep in
	 the current state. Packages are specified in exactly the same way
	 as for the “<code class="literal">install</code>” command. For
	 instance, “<code class="literal">aptitude hold '~e^dpkg$'</code>”
	 will mark all packages coming from the source package
	 “<code class="literal">dpkg</code>” to be on hold.
	 
	 The difference between <code class="literal">hold</code> and
	 <code class="literal">keep</code> is that <code class="literal">hold</code> will cause a
	 package to be ignored by future <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 or <a class="link" href="rn01re01.html#manpageFullUpgrade"><code class="literal">full-upgrade</code></a>
	 commands, while <code class="literal">keep</code> merely cancels any scheduled
	 actions on the package. <code class="literal">unhold</code> will allow a
	 package to be upgraded by future <code class="literal">safe-upgrade</code> or
	 <a class="link" href="rn01re01.html#manpageFullUpgrade"><code class="literal">full-upgrade</code></a>
	 commands, without otherwise altering its state.
	 </dd><dt><a id="manpageKeepAll"></a><code class="literal">keep-all</code></dt><dd>
	 Cancels all scheduled actions on all packages; any
	 packages whose sticky state indicates an installation,
	 removal, or upgrade will have this sticky state cleared.
	 </dd><dt><a id="cmdlineForgetNew"></a><code class="literal">forget-new</code></dt><dd>
	 Forgets all internal information about what packages are
	 “new” (equivalent to pressing
	 “f” when in visual mode).
	 
	 This command accepts package names or patterns as arguments. If the
	 string contains a tilde character
	 (“<code class="literal">~</code>”) or a question mark
	 (“<code class="literal">?</code>”), it will be treated as a
	 search pattern and every package matching the pattern will be
	 considered (see the section <a class="link" href="ch02s04.html" title="Search patterns">“Search Patterns”</a> in
	 the aptitude reference manual).
	 </dd><dt><code class="literal">forbid-version</code></dt><dd>
	 Forbid a package from being upgraded to a particular version, while
	 allowing automatic upgrades to future versions. This is useful for
	 example to avoid a known broken version of a package, without having
	 to set and clear manual holds.
	 
	 By default, aptitude will select the forbidden version to be the
	 one which the package would normally be upgraded (the candidate
	 version). This may be overridden by appending
	 “<code class="literal">=<code>version</code></code>”
	 to the package name: for instance, “<code class="literal">aptitude
	 forbid-version vim=1.2.3.broken-4</code>”.
	 
	 To revert the action, “<code class="literal">aptitude install
	 <code>package</code></code>” will remove the
	 ban. To remove the forbidden version without installing the
	 candidate version, the current version should be appended:
	 “install
	 <code>package</code><code class="literal">=<code>version</code></code>”.
	 </dd><dt><code class="literal">update</code></dt><dd>
	 Updates the list of available packages from the <code class="systemitem">apt</code>
	 sources (this is equivalent to “<code class="literal">apt-get
	 update</code>”)
	 </dd><dt><a id="manpageSafeUpgrade"></a><code class="literal">safe-upgrade</code></dt><dd>
	 Upgrades installed packages to their most recent version.
	 Installed packages will not be removed unless they are
	 unused (see the section “<a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">Managing Automatically Installed
	 Packages</a>” in the aptitude reference
	 manual). Packages which are not currently installed may
	 be installed to resolve dependencies unless the <a class="link" href="rn01re01.html#cmdlineOptionNoNewInstalls"><code class="literal">--no-new-installs</code></a>
	 command-line option is supplied.
	 
	 If no <code>package</code>s are listed on
	 the command line, aptitude will attempt to upgrade every
	 package that can be upgraded. Otherwise, aptitude will
	 attempt to upgrade only the packages which it is
	 instructed to upgrade. The
	 <code>package</code>s can be extended with
	 suffixes in the same manner as arguments to
	 <code class="literal">aptitude install</code>, so you can also give
	 additional instructions to aptitude here; for instance,
	 <code class="literal">aptitude safe-upgrade bash dash-</code> will
	 attempt to upgrade the <code class="systemitem">bash</code>
	 package and remove the <code class="systemitem">dash</code>
	 package.
	 
	 It is sometimes necessary to remove one package in order
	 to upgrade another; this command is not able to upgrade
	 packages in such situations. Use the <a class="link" href="rn01re01.html#manpageFullUpgrade"><code class="literal">full-upgrade</code></a>
	 command to upgrade as many packages as possible.
	 </dd><dt><a id="manpageFullUpgrade"></a><code class="literal">full-upgrade</code></dt><dd>
	 Upgrades installed packages to their most recent version,
	 removing or installing packages as necessary. It also installs new
	 Essential or Required packages. This command is less conservative
	 than <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 and thus more likely to perform unwanted actions.
	 However, it is capable of upgrading packages that <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 cannot upgrade.
	 
	 If no <code>package</code>s are listed on
	 the command line, aptitude will attempt to upgrade every
	 package that can be upgraded. Otherwise, aptitude will
	 attempt to upgrade only the packages which it is
	 instructed to upgrade. The
	 <code>package</code>s can be extended with
	 suffixes in the same manner as arguments to
	 <code class="literal">aptitude install</code>, so you can also give
	 additional instructions to aptitude here; for instance,
	 <code class="literal">aptitude full-upgrade bash dash-</code> will
	 attempt to upgrade the <code class="systemitem">bash</code>
	 package and remove the <code class="systemitem">dash</code>
	 package.
	 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top">
	 This command was originally named
	 <code class="literal">dist-upgrade</code> for historical reasons,
	 and aptitude still recognizes
	 <code class="literal">dist-upgrade</code> as a synonym for
	 <code class="literal">full-upgrade</code>.
	 </td></tr></table></div></dd><dt><a id="cmdlineSearch"></a><code class="literal">search</code></dt><dd>
	 Searches for packages matching one of the patterns
	 supplied on the command line. All packages which
	 match any of the given patterns will be displayed; for
	 instance, “<code class="literal">aptitude search
	 '~N' edit</code>” will list all “new” packages and all packages whose name contains “edit”. For more information on
	 search patterns, see the section “<a class="link" href="ch02s04.html" title="Search patterns">Search
	 Patterns</a>” in the aptitude reference
	 manual.
	 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top">
 In the example above, “<code class="literal">aptitude search
 '~N' edit</code>” has two arguments after
 <code class="literal">search</code> and thus is searching for
 two patterns:
 “<code class="literal">~N</code>” and
 “<code class="literal">edit</code>”. As described in
 the <a class="link" href="ch02s04.html" title="Search patterns">search pattern
 reference</a>, a single pattern
 composed of two sub-patterns separated by a space (such
 as “<code class="literal">~N edit</code>”) matches
 only if both patterns match. Thus,
 the command “<code class="literal">aptitude search '~N
 edit'</code>” will only show
 “new” packages whose name contains
 “edit”.
 </td></tr></table></div>
	 Unless you pass the <a class="link" href="rn01re01.html#cmdlineOptionFormat"><code class="literal">-F</code></a> option, the output of
	 <code class="literal">aptitude search</code> will look something
	 like this:
	 <pre class="screen">i apt - Advanced front-end for dpkg
pi apt-build - frontend to apt to build, optimize and in
cp apt-file - APT package searching utility -- command-
ihA raptor-utils - Raptor RDF Parser utilities</pre>
	 Each search result is listed on a separate line. The
	 first character of each line indicates the current state
	 of the package: the most common states are
	 <code class="literal">p</code>, meaning that no trace of the package
	 exists on the system, <code class="literal">c</code>, meaning that
	 the package was deleted but its configuration files remain
	 on the system, <code class="literal">i</code>, meaning that the
	 package is installed, and <code class="literal">v</code>, meaning
	 that the package is virtual. The second character
	 indicates the stored action (if any; otherwise a blank
	 space is displayed) to be performed on the package, with
	 the most common actions being <code class="literal">i</code>,
	 meaning that the package will be installed,
	 <code class="literal">d</code>, meaning that the package will be
	 deleted, and <code class="literal">p</code>, meaning that the
	 package and its configuration files will be removed. If
	 the third character is <code class="literal">A</code>, the package
	 was automatically installed.
	 
	 For a complete list of the possible state and action
	 flags, see the section “<a class="link" href="ch02s02s02.html" title="Accessing package information">Accessing Package
	 Information</a>” in the aptitude reference
	 guide. To customize the output of
	 <code class="literal">search</code>, see the command-line options
	 <a class="link" href="rn01re01.html#cmdlineOptionFormat"><code class="literal">-F</code></a>
	 and <a class="link" href="rn01re01.html#cmdlineOptionSort"><code class="literal">--sort</code></a>.
	 </dd><dt><code class="literal">show</code></dt><dd>
	 Displays detailed information about one or more packages. If a
	 package name contains a tilde character
	 (“<code class="literal">~</code>”) or a question mark
	 (“<code class="literal">?</code>”), it will be treated as a
	 search pattern and all matching packages will be displayed (see the
	 section “<a class="link" href="ch02s04.html" title="Search patterns">Search
	 Patterns</a>” in the aptitude reference manual).
	 
	 If the verbosity level is 1 or greater (i.e., at least one <code class="literal">-v</code>
	 is present on the command-line), information about all
	 versions of the package is displayed. Otherwise, information about
	 the “candidate version” (the version
	 that “<code class="literal">aptitude install</code>”
	 would download) is displayed.
	 
	 You can display information about a different version of
	 the package by appending
	 <code class="literal">=<code>version</code></code> to
	 the package name; you can display the version from a
	 particular archive or release by appending
	 <code class="literal">/<code>archive</code></code> or
	 <code class="literal">/<code>release</code></code> to
	 the package name: for instance,
	 <code class="literal">/unstable</code> or <code class="literal">/sid</code>.
	 If either of these is present, then only the version you
	 request will be displayed, regardless of the verbosity
	 level.
	 
	 If the verbosity level is 1 or greater, the package's
	 architecture, compressed size, filename, and md5sum fields
	 will be displayed. If the verbosity level is 2 or
	 greater, the select version or versions will be displayed
	 once for each archive in which they are found.
	 </dd><dt><code class="literal">showsrc</code></dt><dd>
	 Displays detailed information about one or more source packages.
	 
	 This is a thin wrapper over
	 apt(8).
	 </dd><dt><code class="literal">source</code></dt><dd>
	 Downloads one or more source packages.
	 
	 This is a thin wrapper over
	 apt(8).
	 </dd><dt><a id="cmdlineVersions"></a><code class="literal">versions</code></dt><dd>
 Displays the versions of the packages listed on the
 command-line.
 <pre class="screen">$ aptitude versions wesnoth
p 1:1.4.5-1 100
p 1:1.6.5-1 unstable 500
p 1:1.7.14-1 experimental 1</pre>
 Each version is listed on a separate line. The leftmost
 three characters indicate the current state, planned state
 (if any), and whether the package was automatically
 installed; for more information on their meanings, see
 <a class="link" href="rn01re01.html#cmdlineSearch">the documentation of
 <code class="literal">aptitude search</code></a>. To the right
 of the version number you can find the releases from which
 the version is available, and the pin priority of the
 version.
 
 If a package name contains a tilde character
 (“<code class="literal">~</code>”) or a question mark
 (“<code class="literal">?</code>”), it will be treated
 as a search pattern and all matching
 versions will be displayed (see the
 section “<a class="link" href="ch02s04.html" title="Search patterns">Search
 Patterns</a>” in the aptitude reference
 manual). This means that, for instance, <code class="literal">aptitude
 versions '~i'</code> will display all the versions that
 are currently installed on the system and nothing else,
 not even other versions of the same packages.
 <pre class="screen">$ aptitude versions '~nexim4-daemon-light'
Package exim4-daemon-light:
i 4.71-3 100
p 4.71-4 unstable 500

Package exim4-daemon-light-dbg:
p 4.71-4 unstable 500</pre>
 If the input is a search pattern, or if more than one
 package's versions are to be displayed, aptitude will
 automatically group the output by package, as shown above.
 You can disable this via <code class="literal"><a class="link" href="rn01re01.html#cmdlineGroupBy">--group-by</a>=none</code>,
 in which case aptitude will display a single list of all
 the versions that were found and automatically include the
 package name in each output line:
 <pre class="screen">$ aptitude versions --group-by=none '~nexim4-daemon-light'
i exim4-daemon-light 4.71-3 100
p exim4-daemon-light 4.71-4 unstable 500
p exim4-daemon-light-dbg 4.71-4 unstable 500</pre>
 To disable the package name, pass
 <code class="literal"><a class="link" href="rn01re01.html#cmdlineShowPackageNames">--show-package-names</a>=never</code>:
 <pre class="screen">$ aptitude versions --show-package-names=never --group-by=none '~nexim4-daemon-light'
i 4.71-3 100
p 4.71-4 unstable 500
p 4.71-4 unstable 500</pre>
 In addition to the above options, the information printed
 for each version can be controlled by the command-line
 option <a class="link" href="rn01re01.html#cmdlineOptionFormat"><code class="literal">-F</code></a>.
 The order in which versions are displayed can be
 controlled by the command-line option <a class="link" href="rn01re01.html#cmdlineOptionSort"><code class="literal">--sort</code></a>.
 To prevent aptitude from formatting the output into
 columns, use <a class="link" href="rn01re01.html#cmdlineOptionDisableColumns"><code class="literal">--disable-columns</code></a>.
 </dd><dt><a id="cmdlineAddOrRemoveUserTags"></a><code class="literal">add-user-tag</code>, <code class="literal">remove-user-tag</code></dt><dd>
	 Adds a user tag to or removes a user tag from the selected
	 group of packages. If a package name contains a tilde
	 (“<code class="literal">~</code>”) or question mark
	 (“<code class="literal">?</code>”), it is treated as a
	 search pattern and the tag is added to or removed from all
	 the packages that match the pattern (see the section
	 “<a class="link" href="ch02s04.html" title="Search patterns">Search
	 Patterns</a>” in the aptitude reference
	 manual).
	 
	 User tags are arbitrary strings associated with a package.
	 They can be used with the <a class="link" href="ch02s04s05.html#searchUserTag"><code class="literal">?user-tag(<code>tag</code>)</code></a>
	 search term, which will select all the packages that have
	 a user tag matching <code>tag</code>.
	 </dd><dt><code class="literal">why</code>, <code class="literal">why-not</code></dt><dd>
	 Explains the reason that a particular package should or
	 cannot be installed on the system.
	 
	 This command searches for packages that require or
	 conflict with the given package. It displays a sequence
	 of dependencies leading to the target package, along with
	 a note indicating the installed state of each package in
	 the dependency chain:
	 <pre class="screen">$ aptitude why kdepim
i nautilus-data Recommends nautilus
i A nautilus Recommends desktop-base (&gt;= 0.2)
i A desktop-base Suggests gnome | kde | xfce4 | wmaker
p kde Depends kdepim (&gt;= 4:3.4.3)</pre>
	 The command <code class="literal">why</code> finds a dependency
	 chain that installs the package named on the command line,
	 as above. Note that the dependency that aptitude produced
	 in this case is only a suggestion. This is because no
	 package currently installed on this computer depends on or
	 recommends the <code class="systemitem">kdepim</code> package; if
	 a stronger dependency were available, aptitude would have
	 displayed it.
	 
	 In contrast, <code class="literal">why-not</code> finds a
	 dependency chain leading to a conflict
	 with the target package:
	 <pre class="screen">$ aptitude why-not textopo
i ocaml-core Depends ocamlweb
i A ocamlweb Depends tetex-extra | texlive-latex-extra
i A texlive-latex-extra Conflicts textopo</pre>
	 If one or more <code>pattern</code>s are present (in
	 addition to the mandatory last argument, which should be a valid
	 <code>package</code> name), then aptitude will begin
	 its search at these patterns. That is, the first package in the
	 chain it prints to explain why <code>package</code> is
	 or is not installed, will be a package matching the pattern in
	 question. The patterns are considered to be package names unless
	 they contain a tilde character (“<code class="literal">~</code>”)
	 or a question mark (“<code class="literal">?</code>”), in which
	 case they are treated as search patterns (see the section
	 “<a class="link" href="ch02s04.html" title="Search patterns">Search
	 Patterns</a>” in the aptitude reference manual).
	 
	 If no patterns are present, then aptitude will search
	 for dependency chains beginning at manually installed
	 packages. This effectively shows the packages that have
	 caused or would cause a given package to be installed.
	 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top">
	 <code class="literal">aptitude why</code> does not perform full
	 dependency resolution; it only displays direct
	 relationships between packages. For instance, if A
	 requires B, C requires D, and B and C conflict,
	 “<code class="literal">aptitude why-not D</code>”
	 will not produce the answer “A depends on B, B
	 conflicts with C, and D depends on C”.
	 </td></tr></table></div>
	 By default aptitude outputs only the “most
	 installed, strongest, tightest, shortest”
	 dependency chain. That is, it looks for a chain that only
	 contains packages which are installed or will be
	 installed; it looks for the strongest possible
	 dependencies under that restriction; it looks for chains
	 that avoid ORed dependencies and Provides; and it looks
	 for the shortest dependency chain meeting those criteria.
	 These rules are progressively weakened until a match is
	 found.
	 
	 If the verbosity level is 1 or more, then
	 all the explanations aptitude can
	 find will be displayed, in inverse order of relevance. If
	 the verbosity level is 2 or more, a truly excessive amount
	 of debugging information will be printed to standard
	 output.
	 
	 This command returns 0 if successful, 1 if no explanation
	 could be constructed, and -1 if an error occurred.
	 </dd><dt><code class="literal">clean</code></dt><dd>
	 Removes all previously downloaded <code class="literal">.deb</code> files from the package cache
	 directory (usually <code class="filename">/var/cache/apt/archives</code>).
	 </dd><dt><code class="literal">autoclean</code></dt><dd>
	 Removes any cached packages which can no longer be
	 downloaded. This allows you to prevent a cache from
	 growing out of control over time without completely
	 emptying it.
	 </dd><dt><code class="literal">changelog</code></dt><dd>
	 Downloads and displays the Debian changelog for each of
	 the given source or binary packages.
	 
	 By default, the changelog for the version which would be
	 installed with “<code class="literal">aptitude
	 install</code>” is downloaded. You can select a
	 particular version of a package by appending
	 <code class="literal">=<code>version</code></code> to
	 the package name; you can select the version from a
	 particular archive or release by appending
	 <code class="literal">/<code>archive</code></code> or
	 <code class="literal">/<code>release</code></code> to
	 the package name (for instance,
	 <code class="literal">/unstable</code> or <code class="literal">/sid</code>).
	 </dd><dt><code class="literal">download</code></dt><dd>
	 Downloads the <code class="literal">.deb</code> file for the given
	 package to the current directory.
	 
	 This is a thin wrapper over
	 apt(8).
	 </dd><dt><code class="literal">extract-cache-subset</code></dt><dd>
	 Copy the <code class="systemitem">apt</code> configuration directory
	 (<code class="literal">/etc/apt</code>) and a subset of the package
	 database to the specified directory. If no packages are
	 listed, the entire package database is copied; otherwise
	 only the entries corresponding to the named packages are
	 copied. Each package name may be a search pattern, and
	 all the packages matching that pattern will be selected
	 (see the section “<a class="link" href="ch02s04.html" title="Search patterns">Search Patterns</a>”
	 in the aptitude reference manual). Any existing package
	 database files in the output directory will be
	 overwritten.
	 
	 Dependencies in binary package stanzas will be rewritten
	 to remove references to packages not in the selected set.
	 </dd><dt><code class="literal">help</code></dt><dd>
	 Displays a brief summary of the available commands and
	 options.
	 </dd></dl></div></div><div class="refsect1"><a id="idm8899"></a><h2>Options</h2>
 The following options may be used to modify the behavior of
 the actions described above. Note that while all options
 will be accepted for all commands, some options don't apply
 to particular commands and will be ignored by those
 commands.
 <div class="variablelist"><dl class="variablelist"><dt><code class="literal">--add-user-tag <code>tag</code></code></dt><dd>
	 For <code class="literal">full-upgrade</code>,
	 <code class="literal">safe-upgrade</code>, <code class="literal">forbid-version</code>,
	 <code class="literal">hold</code>, <code class="literal">install</code>,
	 <code class="literal">keep-all</code>, <code class="literal">markauto</code>,
	 <code class="literal">unmarkauto</code>, <code class="literal">purge</code>,
	 <code class="literal">reinstall</code>, <code class="literal">remove</code>,
	 <code class="literal">unhold</code>, and <code class="literal">unmarkauto</code>: add
	 the user tag <code>tag</code> to all packages that are
	 installed, removed, or upgraded by this command as if with the <a class="link" href="rn01re01.html#cmdlineAddOrRemoveUserTags"><code class="literal">add-user-tag</code></a>
	 command.
	 </dd><dt><code class="literal">--add-user-tag-to <code>tag</code>,<code>pattern</code></code></dt><dd>
	 For <code class="literal">full-upgrade</code>,
	 <code class="literal">safe-upgrade</code>, <code class="literal">forbid-version</code>,
	 <code class="literal">hold</code>, <code class="literal">install</code>,
	 <code class="literal">keep-all</code>, <code class="literal">markauto</code>,
	 <code class="literal">unmarkauto</code>, <code class="literal">purge</code>,
	 <code class="literal">reinstall</code>, <code class="literal">remove</code>,
	 <code class="literal">unhold</code>, and <code class="literal">unmarkauto</code>: add
	 the user tag <code>tag</code> to all packages that
	 match <code>pattern</code> as if with the <a class="link" href="rn01re01.html#cmdlineAddOrRemoveUserTags"><code class="literal">add-user-tag</code></a>
	 command. The pattern is a search pattern as described in the
	 section “<a class="link" href="ch02s04.html" title="Search patterns">Search
	 Patterns</a>” in the aptitude reference manual.
	 
	 For instance, <code class="literal">aptitude safe-upgrade
	 --add-user-tag-to "new-installs,?action(install)"</code>
	 will add the tag <code class="literal">new-installs</code> to all
	 the packages installed by the <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 command.
	 </dd><dt><code class="literal">--allow-new-upgrades</code></dt><dd>
	 When the safe resolver is being used (i.e., <a class="link" href="rn01re01.html#cmdlineSafeResolver"><code class="literal">--safe-resolver</code></a>
	 was passed, the action is <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>,
	 or <a class="link" href="ch02s05s05.html#configAlways-Use-Safe-Resolver"><code class="literal">Aptitude::Always-Use-Safe-Resolver</code></a>
	 is set to <code class="literal">true</code>), allow the dependency
	 resolver to install upgrades for packages regardless of
	 the value of <a class="link" href="ch02s05s05.html#configSafe-Resolver-No-New-Upgrades"><code class="literal">Aptitude::Safe-Resolver::No-New-Upgrades</code></a>.
	 </dd><dt><code class="literal">--allow-new-installs</code></dt><dd>
	 Allow the <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 command to install new packages; when the safe resolver is
	 being used (i.e., <a class="link" href="rn01re01.html#cmdlineSafeResolver"><code class="literal">--safe-resolver</code></a>
	 was passed, the action is <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>,
	 or <a class="link" href="ch02s05s05.html#configAlways-Use-Safe-Resolver"><code class="literal">Aptitude::Always-Use-Safe-Resolver</code></a>
	 is set to <code class="literal">true</code>), allow the dependency
	 resolver to install new packages. This option takes
	 effect regardless of the value of <a class="link" href="ch02s05s05.html#configSafe-Resolver-No-New-Installs"><code class="literal">Aptitude::Safe-Resolver::No-New-Installs</code></a>.
	 </dd><dt><code class="literal">--allow-untrusted</code></dt><dd>
	 Install packages from untrusted sources without prompting.
	 You should only use this if you know what you are doing,
	 as it could easily compromise your system's security.
	 </dd><dt><a id="cmdlineOptionDisableColumns"></a><code class="literal">--disable-columns</code></dt><dd>
	 This option causes <code class="literal">aptitude search</code> and
	 <code class="literal">aptitude versions</code> to
	 output their results without any special formatting. In
	 particular: normally aptitude will add whitespace or
	 truncate search results in an attempt to fit its results
	 into vertical “columns”. With this flag,
	 each line will be formed by replacing any format escapes
	 in the format string with the corresponding text; column
	 widths will be ignored.
	 
	 For instance, the first few lines of output from “<code class="literal">aptitude search -F '%p %V' --disable-columns libedataserver</code>” might be:
	 <pre class="screen">disksearch 1.2.1-3
hp-search-mac 0.1.3
libbsearch-ruby 1.5-5
libbsearch-ruby1.8 1.5-5
libclass-dbi-abstractsearch-perl 0.07-2
libdbix-fulltextsearch-perl 0.73-10</pre>
 As in the above example,
 <code class="literal">--disable-columns</code> is often useful in
 combination with a custom display format set using the
 command-line option <a class="link" href="rn01re01.html#cmdlineOptionFormat"><code class="literal">-F</code></a>.
	 
	 This corresponds to the configuration option
	 <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Disable-Columns">Aptitude::CmdLine::Disable-Columns</a></code>.
	 </dd><dt><code class="literal">-D</code>, <code class="literal">--show-deps</code></dt><dd>
	 For commands that will install or remove packages
	 (<code class="literal">install</code>, <a class="link" href="rn01re01.html#manpageFullUpgrade"><code class="literal">full-upgrade</code></a>,
	 etc), show brief explanations of automatic installations
	 and removals.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Show-Deps">Aptitude::CmdLine::Show-Deps</a></code>.
	 </dd><dt><code class="literal">-d</code>, <code class="literal">--download-only</code></dt><dd>
	 Download packages to the package cache as necessary, but
	 do not install or remove anything. By default, the
	 package cache is stored in
	 <code class="filename">/var/cache/apt/archives</code>.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Download-Only">Aptitude::CmdLine::Download-Only</a></code>.
	 </dd><dt><a id="cmdlineOptionFormat"></a>
	 <code class="literal">-F</code> <code>format</code>, <code class="literal">--display-format</code> <code>format</code>
	</dt><dd>
	 Specify the format which should be used to display
	 output from the <code class="literal">search</code> and
 <code class="literal">versions</code> commands.
	 For instance, passing “<code class="literal">%p %v %V</code>”
	 for <code>format</code> will display a package's name,
	 followed by its currently installed version and its
	 candidate version (see the section “<a class="link" href="ch02s05s01.html#secDisplayFormat" title="Customizing how packages are displayed">Customizing how packages are displayed</a>” in the aptitude reference manual for more information).
	 
	 The command-line option <a class="link" href="rn01re01.html#cmdlineOptionDisableColumns"><code class="literal">--disable-columns</code></a>
	 is often useful in combination with <code class="literal">-F</code>.
	 
	 For <code class="literal">search</code>, this corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Package-Display-Format">Aptitude::CmdLine::Package-Display-Format</a></code>;
 for <code class="literal">versions</code>, this corresponds to the
 configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Version-Display-Format">Aptitude::CmdLine::Version-Display-Format</a></code>.
	 </dd><dt><code class="literal">-f</code></dt><dd>
	 Try hard to fix the dependencies of broken packages, even
	 if it means ignoring the actions requested on the command
	 line.
	 
	 This corresponds to the configuration item <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Fix-Broken">Aptitude::CmdLine::Fix-Broken</a></code>.
	 </dd><dt><a id="cmdlineFullResolver"></a><code class="literal">--full-resolver</code></dt><dd>
	 When package dependency problems are encountered, use the
	 default “full” resolver to solve them.
	 Unlike the “safe” resolver activated by <a class="link" href="rn01re01.html#cmdlineSafeResolver"><code class="literal">--safe-resolver</code></a>,
	 the full resolver will happily remove packages to fulfill
	 dependencies. It can resolve more situations than the
	 safe algorithm, but its solutions are more likely to be
	 undesirable.
	 
	 This option can be used to force the use of the full
	 resolver even when <a class="link" href="ch02s05s05.html#configAlways-Use-Safe-Resolver"><code class="literal">Aptitude::Always-Use-Safe-Resolver</code></a>
	 is true.
	 </dd><dt><a id="cmdlineGroupBy"></a>
 <code class="literal">--group-by</code> <code>grouping-mode</code>
 </dt><dd>
 Control how the <a class="link" href="rn01re01.html#cmdlineVersions"><code class="literal">versions</code></a>
 command groups its output. The following values are
 recognized:
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
 <code class="literal">archive</code> to group packages by the
 archive they occur in
 (“<code class="literal">stable</code>”,
 “<code class="literal">unstable</code>”, etc). If
 a package occurs in several archives, it will be
 displayed in each of them.
 </li><li class="listitem">
 <code class="literal">auto</code> to group versions by their
 package unless there is exactly one argument and it is
 not a search pattern.
 </li><li class="listitem">
 <code class="literal">none</code> to display all the versions in
 a single list without any grouping.
 </li><li class="listitem">
 <code class="literal">package</code> to group versions by their
 package.
 </li><li class="listitem">
 <code class="literal">source-package</code> to group versions by
 their source package.
 </li><li class="listitem">
 <code class="literal">source-version</code> to group versions by
 their source package and source version.
 </li></ul></div>
 This corresponds to the configuration option
 <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Versions-Group-By">Aptitude::CmdLine::Versions-Group-By</a></code>.
 </dd><dt>
	 <code class="literal">-h</code>, <code class="literal">--help</code>
	</dt><dd>
	 Display a brief help message. Identical to the <code class="literal">help</code> action.
	 </dd><dt><a id="cmdlineOptionLogFile"></a>
	 <code class="literal">--log-file=<code>file</code></code>
	</dt><dd>
	 If <code>file</code> is a nonempty string,
	 log messages will be written to it, except that if
	 <code>file</code> is
	 “<code class="literal">-</code>”, the messages will be
	 written to standard output instead. If this option
	 appears multiple times, the last occurrence is the one
	 that will take effect.
	 
	 This does not affect the log of installations that
	 aptitude has performed
	 (<code class="filename">/var/log/aptitude</code>); the log messages
	 written using this configuration include internal program
	 events, errors, and debugging messages. See the
	 command-line option <a class="link" href="rn01re01.html#cmdlineOptionLogLevel"><code class="literal">--log-level</code></a>
	 to get more control over what gets logged.
	 
	 This corresponds to the configuration option <a class="link" href="ch02s05s05.html#configLoggingFile"><code class="literal">Aptitude::Logging::File</code></a>.
	 </dd><dt><a id="cmdlineOptionLogLevel"></a>
	 <code class="literal">--log-level=<code>level</code></code>, <code class="literal">--log-level=<code>category</code>:<code>level</code></code>
	</dt><dd>
	 <code class="literal">--log-level=<code>level</code></code>
	 causes aptitude to only log messages whose level is
	 <code>level</code> or higher. For instance,
	 setting the log level to <code class="literal">error</code> will
	 cause only messages at the log levels
	 <code class="literal">error</code> and <code class="literal">fatal</code> to
	 be displayed; all others will be hidden. Valid log levels
	 (in descending order) are <code class="literal">off</code>,
	 <code class="literal">fatal</code>, <code class="literal">error</code>,
	 <code class="literal">warn</code>, <code class="literal">info</code>,
	 <code class="literal">debug</code>, and <code class="literal">trace</code>.
	 The default log level is <code class="literal">warn</code>.
	 
	 <code class="literal">--log-level=<code>category</code>:<code>level</code></code>
	 causes messages in <code>category</code> to
	 only be logged if their level is
	 <code>level</code> or higher.
	 
	 <code class="literal">--log-level</code> may appear multiple times
	 on the command line; the most specific setting is the one
	 that takes effect, so if you pass
	 <code class="literal">--log-level=aptitude.resolver:fatal</code> and
	 <code class="literal">--log-level=aptitude.resolver.hints.match:trace</code>,
	 then messages in
	 <code class="literal">aptitude.resolver.hints.parse</code> will only
	 be printed if their level is <code class="literal">fatal</code>, but
	 all messages in
	 <code class="literal">aptitude.resolver.hints.match</code> will be
	 printed. If you set the level of the same category two or
	 more times, the last setting is the one that will take
	 effect.
	 
	 This does not affect the log of installations that
	 aptitude has performed
	 (<code class="filename">/var/log/aptitude</code>); the log messages
	 written using this configuration include internal program
	 events, errors, and debugging messages. See the
	 command-line option <a class="link" href="rn01re01.html#cmdlineOptionLogLevel"><code class="literal">--log-file</code></a>
	 to change where log messages go.
	 
	 This corresponds to the configuration group <a class="link" href="ch02s05s05.html#configLoggingLevels"><code class="literal">Aptitude::Logging::Levels</code></a>.
	 </dd><dt><a id="cmdlineOptionLogResolver"></a>
	 <code class="literal">--log-resolver</code>
	</dt><dd>
	 Set some standard log levels related to the resolver, to
	 produce logging output suitable for processing with
	 automated tools. This is equivalent to the command-line
	 options
	 <code class="literal">--log-level=aptitude.resolver.search:trace
	 --log-level=aptitude.resolver.search.tiers:info</code>.
	 </dd><dt><a id="cmdlineOptionNoNewInstalls"></a>
	 <code class="literal">--no-new-installs</code>
	</dt><dd>
	 Prevent <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 from installing any new packages; when the safe resolver
	 is being used (i.e., <a class="link" href="rn01re01.html#cmdlineSafeResolver"><code class="literal">--safe-resolver</code></a>
	 was passed or <a class="link" href="ch02s05s05.html#configAlways-Use-Safe-Resolver"><code class="literal">Aptitude::Always-Use-Safe-Resolver</code></a>
	 is set to <code class="literal">true</code>), forbid the dependency
	 resolver from installing new packages. This option takes
	 effect regardless of the value of <a class="link" href="ch02s05s05.html#configSafe-Resolver-No-New-Installs"><code class="literal">Aptitude::Safe-Resolver::No-New-Installs</code></a>.
	 
	 This mimics the historical behavior of apt-get
	 upgrade.
	 </dd><dt><code class="literal">--no-new-upgrades</code></dt><dd>
	 When the safe resolver is being used (i.e., <a class="link" href="rn01re01.html#cmdlineSafeResolver"><code class="literal">--safe-resolver</code></a>
	 was passed or <a class="link" href="ch02s05s05.html#configAlways-Use-Safe-Resolver"><code class="literal">Aptitude::Always-Use-Safe-Resolver</code></a>
	 is set to <code class="literal">true</code>), forbid the dependency
	 resolver from installing upgrades for packages
 regardless of the value of <a class="link" href="ch02s05s05.html#configSafe-Resolver-No-New-Upgrades"><code class="literal">Aptitude::Safe-Resolver::No-New-Upgrades</code></a>.
	 </dd><dt><a id="cmdlineOptionNoShowResolverActions"></a><code class="literal">--no-show-resolver-actions</code></dt><dd>
	 Do not display the actions performed by the
	 “safe” resolver, overriding any configuration
	 option or earlier
	 <a class="link" href="rn01re01.html#cmdlineOptionShowResolverActions"><code class="literal">--show-resolver-actions</code></a>.
	 </dd><dt><a id="cmdlineOptionSort"></a><code class="literal">-O</code> <code>order</code>, <code class="literal">--sort</code> <code>order</code></dt><dd>
	 Specify the order in which output from the <a class="link" href="rn01re01.html#cmdlineSearch"><code class="literal">search</code></a> and <a class="link" href="rn01re01.html#cmdlineVersions"><code class="literal">versions</code></a>
	 commands should be displayed. For instance, passing “<code class="literal">installsize</code>”
	 for <code>order</code> will list packages in
	 order according to their size when installed (see the section “<a class="link" href="ch02s05s01.html#secSortingPolicy" title="Customizing how packages are sorted">Customizing how packages are sorted</a>” in the aptitude reference manual for more information).
	 
 Prepending the order keyword with a tilde character
 (<code class="literal">~</code>) reverses the order from ascending
 to descending.
 
 The default sort order is <code class="literal">name,version</code>.
 </dd><dt><code class="literal">-o</code> <code>key</code><code class="literal">=</code><code>value</code></dt><dd>
	 Set a configuration file option directly; for
	 instance, use <code class="literal">-o
	 Aptitude::Log=/tmp/my-log</code> to log aptitude's
	 actions to <code class="filename">/tmp/my-log</code>. For more
	 information on configuration file options, see the
	 section “<a class="link" href="ch02s05s05.html" title="Configuration file reference">Configuration file
	 reference</a>” in the aptitude reference manual.
	 </dd><dt><code class="literal">-P</code>, <code class="literal">--prompt</code></dt><dd>
	 Always display a prompt before downloading, installing or
	 removing packages, even when no actions other than those
	 explicitly requested will be performed.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Always-Prompt">Aptitude::CmdLine::Always-Prompt</a></code>.
	 </dd><dt><code class="literal">--purge-unused</code></dt><dd>
	 If <code class="literal"><a class="link" href="ch02s05s05.html#configDelete-Unused">Aptitude::Delete-Unused</a></code>
	 is set to “<code class="literal">true</code>” (its
	 default), then in addition to removing each package that
	 is no longer required by any installed package, aptitude
	 will also purge them, removing their configuration files
	 and perhaps other important data. For more information
	 about which packages are considered to be
	 “unused”, see the section “<a class="link" href="ch02s02s06.html" title="Managing automatically installed packages">Managing Automatically Installed
	 Packages</a>” in the aptitude reference
	 manual. THIS OPTION CAN CAUSE DATA LOSS! DO
	 NOT USE IT UNLESS YOU KNOW WHAT YOU ARE DOING!
	 
	 This corresponds to the configuration option
	 <code class="literal"><a class="link" href="ch02s05s05.html#configPurge-Unused">Aptitude::Purge-Unused</a></code>.
	 </dd><dt><code class="literal">-q[=<code>n</code>]</code>, <code class="literal">--quiet[=<code>n</code>]</code></dt><dd>
	 Suppress all incremental progress indicators, thus making
	 the output loggable. This may be supplied multiple times
	 to make the program quieter, but unlike apt-get,
	 aptitude does not enable <code class="literal">-y</code> when <code class="literal">-q</code>
	 is supplied more than once.
	 
	 The optional <code class="literal">=<code>n</code></code>
	 may be used to directly set the amount of quietness (for
	 instance, to override a setting in <code class="filename">/etc/apt/apt.conf</code>);
	 it causes the program to behave as if <code class="literal">-q</code>
	 had been passed exactly <code>n</code>
	 times.
	 </dd><dt><code class="literal">-R</code>, <code class="literal">--without-recommends</code></dt><dd>
	 Do not treat recommendations as
	 dependencies when installing new packages (this overrides settings in <code class="filename">/etc/apt/apt.conf</code> and <code class="filename">~/.aptitude/config</code>).
	 Packages previously installed due to recommendations
	 will not be removed.
	 
	 This corresponds to the pair of configuration options <code class="literal"><a class="link" href="ch02s05s05.html#configAptInstall-Recommends">APT::Install-Recommends</a></code> and <code class="literal"><a class="link" href="ch02s05s05.html#configApt-AutoRemove-RecommendsImportant">APT::AutoRemove::RecommendsImportant</a></code>.
	 </dd><dt><code class="literal">-r</code>, <code class="literal">--with-recommends</code></dt><dd>
	 Treat recommendations as dependencies when installing
	 new packages (this overrides settings in <code class="filename">/etc/apt/apt.conf</code> and <code class="filename">~/.aptitude/config</code>).
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configAptInstall-Recommends">APT::Install-Recommends</a></code>
	 </dd><dt><code class="literal">--remove-user-tag <code>tag</code></code></dt><dd>
	 For <code class="literal">full-upgrade</code>,
	 <code class="literal">safe-upgrade</code>
	 <code class="literal">forbid-version</code>,
	 <code class="literal">hold</code>, <code class="literal">install</code>,
	 <code class="literal">keep-all</code>, <code class="literal">markauto</code>,
	 <code class="literal">unmarkauto</code>, <code class="literal">purge</code>,
	 <code class="literal">reinstall</code>, <code class="literal">remove</code>,
	 <code class="literal">unhold</code>, and
	 <code class="literal">unmarkauto</code>: remove the user tag
	 <code>tag</code> from all packages that are
	 installed, removed, or upgraded by this command as if with
	 the <a class="link" href="rn01re01.html#cmdlineAddOrRemoveUserTags"><code class="literal">add-user-tag</code></a>
	 command.
	 </dd><dt><code class="literal">--remove-user-tag-from <code>tag</code>,<code>pattern</code></code></dt><dd>
	 For <code class="literal">full-upgrade</code>,
	 <code class="literal">safe-upgrade</code>
	 <code class="literal">forbid-version</code>,
	 <code class="literal">hold</code>, <code class="literal">install</code>,
	 <code class="literal">keep-all</code>, <code class="literal">markauto</code>,
	 <code class="literal">unmarkauto</code>, <code class="literal">purge</code>,
	 <code class="literal">reinstall</code>, <code class="literal">remove</code>,
	 <code class="literal">unhold</code>, and
	 <code class="literal">unmarkauto</code>: remove the user tag
	 <code>tag</code> from all packages that
	 match <code>pattern</code> as if with the
	 <a class="link" href="rn01re01.html#cmdlineAddOrRemoveUserTags"><code class="literal">remove-user-tag</code></a>
	 command. The pattern is a search pattern as described in
	 the section “<a class="link" href="ch02s04.html" title="Search patterns">Search Patterns</a>”
	 in the aptitude reference manual.
	 
	 For instance, <code class="literal">aptitude safe-upgrade
	 --remove-user-tag-from
	 "not-upgraded,?action(upgrade)"</code> will remove the
	 <code class="literal">not-upgraded</code> tag from all packages that
	 the <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 command is able to upgrade.
	 </dd><dt><code class="literal">-s</code>, <code class="literal">--simulate</code></dt><dd>
	 In command-line mode, print the actions that would
	 normally be performed, but don't actually perform them.
	 This does not require <code class="systemitem">root</code> privileges. In the visual
	 interface, always open the cache in read-only mode
	 regardless of whether you are <code class="systemitem">root</code>.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configSimulate">Aptitude::Simulate</a></code>.
	 </dd><dt><a id="cmdlineSafeResolver"></a><code class="literal">--safe-resolver</code></dt><dd>
	 When package dependency problems are encountered, use a
	 “safe” algorithm to solve them. This
	 resolver attempts to preserve as many of your choices as
	 possible; it will never remove a package or install a
	 version of a package other than the package's default
	 candidate version. It is the same algorithm used in <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>;
	 indeed, <code class="literal">aptitude --safe-resolver
	 full-upgrade</code> is equivalent to <code class="literal">aptitude
	 safe-upgrade</code>. Because
	 <code class="literal">safe-upgrade</code> always uses the safe
	 resolver, it does not accept the
	 <code class="literal">--safe-resolver</code> flag.
	 
	 This option is equivalent to setting the configuration
	 variable <a class="link" href="ch02s05s05.html#configAlways-Use-Safe-Resolver"><code class="literal">Aptitude::Always-Use-Safe-Resolver</code></a>
	 to <code class="literal">true</code>.
	 </dd><dt><code class="literal">--schedule-only</code></dt><dd>
	 For commands that modify package states, schedule
	 operations to be performed in the future, but don't
	 perform them. You can execute scheduled actions by
	 running <code class="literal">aptitude install</code> with no
	 arguments. This is equivalent to making the corresponding
	 selections in <a class="link" href="ch01s01.html" title="Using aptitude">visual
	 mode</a>, then exiting the program normally.
	 
	 For instance, <code class="literal">aptitude --schedule-only install
	 evolution</code> will schedule the
	 <code class="literal">evolution</code> package for later
	 installation.
	 </dd><dt><a id="cmdlineShowPackageNames"></a><code class="literal">--show-package-names</code> <code>when</code></dt><dd>
 Controls when the <a class="link" href="rn01re01.html#cmdlineVersions"><code class="literal">versions</code></a>
 command shows package names. The following settings are
 allowed:
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
 <code class="literal">always</code>: display package names every
 time that <code class="literal">aptitude versions</code> runs.
 </li><li class="listitem">
 <code class="literal">auto</code>: display package names when
 <code class="literal">aptitude versions</code> runs if the
 output is not grouped by package, and either there is
 a pattern-matching argument or there is more than one
 argument.
 </li><li class="listitem">
 <code class="literal">never</code>: never display package names
 in the output of <code class="literal">aptitude versions</code>.
 </li></ul></div>
 This option corresponds to the configuration item <a class="link" href="ch02s05s05.html#configCmdLine-Versions-Show-Package-Names"><code class="literal">Aptitude::CmdLine::Versions-Show-Package-Names</code></a>.
 </dd><dt><a id="cmdlineOptionShowResolverActions"></a><code class="literal">--show-resolver-actions</code></dt><dd>
	 Display the actions performed by the “safe”
	 resolver and by <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>.
	 
	 When executing the command <a class="link" href="rn01re01.html#manpageSafeUpgrade"><code class="literal">safe-upgrade</code></a>
	 or when the option <a class="link" href="rn01re01.html#cmdlineSafeResolver">--safe-resolver</a> is
	 present, aptitude will display a summary of the actions
	 performed by the resolver before printing the installation
	 preview. This is equivalent to the configuration option <a class="link" href="ch02s05s05.html#configSafe-Resolver-Show-Resolver-Actions"><code class="literal">Aptitude::Safe-Resolver::Show-Resolver-Actions</code></a>.
	 </dd><dt><a id="cmdlineOptionShowSummary"></a><code class="literal">--show-summary[=<code>MODE</code>]</code></dt><dd>
	 Changes the behavior of “<code class="literal">aptitude
	 why</code>” to summarize each dependency chain
	 that it outputs, rather than displaying it in long form.
	 If this option is present and
	 <code>MODE</code> is not
	 “<code class="literal">no-summary</code>”, chains that
	 contain Suggests dependencies will not be displayed:
	 combine <code class="literal">--show-summary</code> with
	 <code class="literal">-v</code> to see a summary of all the reasons
	 for the target package to be installed.
	 
	 <code>MODE</code> can be any one of the
	 following:
	 <div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
		<code class="literal">no-summary</code>: don't show a summary
		(the default behavior if
		<code class="literal">--show-summary</code> is not present).
	 </li><li class="listitem">
		<code class="literal">first-package</code>: display the first
		package in each chain. This is the default value of
		<code>MODE</code> if it is not present.
	 </li><li class="listitem">
		<code class="literal">first-package-and-type</code>: display the
		first package in each chain, along with the strength
		of the weakest dependency in the chain.
	 </li><li class="listitem">
		<code class="literal">all-packages</code>: briefly display each
		chain of dependencies leading to the target package.
	 </li><li class="listitem">
		 <code class="literal">all-packages-with-dep-versions</code>:
		 briefly display each chain of dependencies leading to
		 the target package, including the target version of
		 each dependency.
	 </li></ol></div>
	 This option corresponds to the configuration item <a class="link" href="ch02s05s05.html#configCmdLine-Show-Summary"><code class="literal">Aptitude::CmdLine::Show-Summary</code></a>;
	 if <code class="literal">--show-summary</code> is present on the
	 command-line, it will override <a class="link" href="ch02s05s05.html#configCmdLine-Show-Summary"><code class="literal">Aptitude::CmdLine::Show-Summary</code></a>.
	 <div class="example"><a id="idm9505"></a>Example 12. Usage of <code class="literal">--show-summary</code><div class="example-contents">
	 <code class="literal">--show-summary</code> used with
	 <code class="literal">-v</code> to display all the reasons a
	 package is installed:
	 <pre class="screen">$ aptitude -v --show-summary why foomatic-db
Packages requiring foomatic-db:
 cupsys-driver-gutenprint
 foomatic-db-engine
 foomatic-db-gutenprint
 foomatic-db-hpijs
 foomatic-filters-ppds
 foomatic-gui
 kde
 printconf
 wine

$ aptitude -v --show-summary=first-package-and-type why foomatic-db
Packages requiring foomatic-db:
  [Depends] cupsys-driver-gutenprint
  [Depends] foomatic-db-engine
  [Depends] foomatic-db-gutenprint
  [Depends] foomatic-db-hpijs
  [Depends] foomatic-filters-ppds
  [Depends] foomatic-gui
  [Depends] kde
  [Depends] printconf
  [Depends] wine

$ aptitude -v --show-summary=all-packages why foomatic-db
Packages requiring foomatic-db:
  cupsys-driver-gutenprint D: cups-driver-gutenprint D: cups R: foomatic-filters R: foomatic-db-engine D: foomatic-db
  foomatic-filters-ppds D: foomatic-filters R: foomatic-db-engine D: foomatic-db
  kde D: kdeadmin R: system-config-printer-kde D: system-config-printer R: hal-cups-utils D: cups R: foomatic-filters R: foomatic-db-engine D: foomatic-db
  wine D: libwine-print D: cups-bsd R: cups R: foomatic-filters R: foomatic-db-engine D: foomatic-db
  foomatic-db-engine D: foomatic-db
  foomatic-db-gutenprint D: foomatic-db
  foomatic-db-hpijs D: foomatic-db
  foomatic-gui D: python-foomatic D: foomatic-db-engine D: foomatic-db
  printconf D: foomatic-db

$ aptitude -v --show-summary=all-packages-with-dep-versions why foomatic-db
Packages requiring foomatic-db:
 cupsys-driver-gutenprint D: cups-driver-gutenprint (&gt;= 5.0.2-4) D: cups (&gt;= 1.3.0) R: foomatic-filters (&gt;= 4.0) R: foomatic-db-engine (&gt;= 4.0) D: foomatic-db (&gt;= 20090301)
 foomatic-filters-ppds D: foomatic-filters R: foomatic-db-engine (&gt;= 4.0) D: foomatic-db (&gt;= 20090301)
 kde D: kdeadmin (&gt;= 4:3.5.5) R: system-config-printer-kde (&gt;= 4:4.2.2-1) D: system-config-printer (&gt;= 1.0.0) R: hal-cups-utils D: cups R: foomatic-filters (&gt;= 4.0) R: foomatic-db-engine (&gt;= 4.0) D: foomatic-db (&gt;= 20090301)
 wine D: libwine-print (= 1.1.15-1) D: cups-bsd R: cups R: foomatic-filters (&gt;= 4.0) R: foomatic-db-engine (&gt;= 4.0) D: foomatic-db (&gt;= 20090301)
 foomatic-db-engine D: foomatic-db
 foomatic-db-gutenprint D: foomatic-db
 foomatic-db-hpijs D: foomatic-db
 foomatic-gui D: python-foomatic (&gt;= 0.7.9.2) D: foomatic-db-engine D: foomatic-db (&gt;= 20090301)
 printconf D: foomatic-db
	 </pre>
	 <code class="literal">--show-summary</code> used to list a chain on one line:
	 <pre class="screen">$ aptitude --show-summary=all-packages why aptitude-gtk libglib2.0-data
Packages requiring libglib2.0-data:
 aptitude-gtk D: libglib2.0-0 R: libglib2.0-data</pre></div></div> </dd><dt><code class="literal">-t</code> <code>release</code>, <code class="literal">--target-release</code> <code>release</code></dt><dd>
	 Set the release from which packages should be
	 installed. For instance, “<code class="literal">aptitude -t
	 experimental ...</code>” will install
	 packages from the experimental distribution unless you
	 specify otherwise.
	 
	 This will affect the default candidate version of packages
	 according to the rules described in
	 apt_preferences(5).
	 
	 This corresponds to the configuration item <code class="literal">APT::Default-Release</code>.
	 </dd><dt><code class="literal">-V</code>, <code class="literal">--show-versions</code></dt><dd>
	 Show which versions of packages will be installed.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Show-Versions">Aptitude::CmdLine::Show-Versions</a></code>.
	 </dd><dt><code class="literal">-v</code>, <code class="literal">--verbose</code></dt><dd>
	 Causes some commands (for instance, <code class="literal">show</code>) to display extra information. This may be supplied multiple times to get more and more information.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Verbose">Aptitude::CmdLine::Verbose</a></code>.
	 </dd><dt><code class="literal">--version</code></dt><dd>
	 Display the version of aptitude and some information
	 about how it was compiled.
	 </dd><dt><code class="literal">--visual-preview</code></dt><dd>
	 When installing or removing packages from the command
	 line, instead of displaying the usual prompt, start up the
	 visual interface and display its preview screen.
	 </dd><dt><code class="literal">-W</code>, <code class="literal">--show-why</code></dt><dd>
	 In the preview displayed before packages are installed or
	 removed, show which manually installed package requires
	 each automatically installed package. For instance:
	 <pre class="screen">$ aptitude --show-why install mediawiki
...
The following NEW packages will be installed:
 libapache2-mod-php5{a} (for mediawiki) mediawiki php5{a} (for mediawiki)
 php5-cli{a} (for mediawiki) php5-common{a} (for mediawiki)
 php5-mysql{a} (for mediawiki)</pre>
	 When combined with <code class="literal">-v</code> or a non-zero
	 value for <a class="link" href="ch02s05s05.html#configCmdLine-Verbose"><code class="literal">Aptitude::CmdLine::Verbose</code></a>,
	 this displays the entire chain of dependencies that lead
	 each package to be installed. For instance:
	 <pre class="screen">$ aptitude -v --show-why install libdb4.2-dev
The following NEW packages will be installed:
 libdb4.2{a} (libdb4.2-dev D: libdb4.2) libdb4.2-dev
The following packages will be REMOVED:
 libdb4.4-dev{a} (libdb4.2-dev C: libdb-dev P&lt;- libdb-dev)</pre>
	 This option will also describe why packages are being
	 removed, as shown above. In this example,
	 <code class="systemitem">libdb4.2-dev</code> conflicts with
	 <code class="systemitem">libdb-dev</code>, which is provided by
	 <code class="systemitem">libdb-dev</code>.
	 
	 This argument corresponds to the configuration option
	 <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Show-Why">Aptitude::CmdLine::Show-Why</a></code>
	 and displays the same information that is computed by
	 <code class="literal">aptitude why</code> and <code class="literal">aptitude
	 why-not</code>.
	 </dd><dt><code class="literal">-w</code> <code>width</code>, <code class="literal">--width</code> <code>width</code></dt><dd>
	 Specify the display width which should be used for output from the
	 <code class="literal">search</code> and <code class="literal">versions</code> commands
	 (in the command line).
	 
	 By default and when the output is seen directly in a terminal, the
	 terminal width is used. When the output is redirected or piped, a
	 very large "unlimited" line width is used, and this option is
	 ignored.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Package-Display-Width">Aptitude::CmdLine::Package-Display-Width</a></code>
	 </dd><dt><code class="literal">-y</code>, <code class="literal">--assume-yes</code></dt><dd>
	 When a yes/no prompt would be presented, assume that
	 the user entered “yes”. In particular,
	 suppresses the prompt that appears when installing,
	 upgrading, or removing packages. Prompts for “dangerous” actions, such as removing
	 essential packages, will still be displayed. This
	 option overrides <code class="literal">-P</code>.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Assume-Yes">Aptitude::CmdLine::Assume-Yes</a></code>.
	 </dd><dt><code class="literal">-Z</code></dt><dd>
	 Show how much disk space will be used or freed by the
	 individual packages being installed, upgraded, or
	 removed.
	 
	 This corresponds to the configuration option <code class="literal"><a class="link" href="ch02s05s05.html#configCmdLine-Show-Size-Changes">Aptitude::CmdLine::Show-Size-Changes</a></code>.
	 </dd></dl></div>
 The following options apply to the visual mode of the
 program, but are primarily for internal use; you generally
 won't need to use them yourself.
 <div class="variablelist"><dl class="variablelist"><dt><code class="literal">--autoclean-on-startup</code></dt><dd>
	 Deletes old downloaded files when the program starts
	 (equivalent to starting the program and immediately
	 selecting
	 Actions → Clean
	 obsolete files). You cannot
	 use this option and
	 “<code class="literal">--clean-on-startup</code>”,
	 “<code class="literal">-i</code>”, or
	 “<code class="literal">-u</code>” at the same time.
	 </dd><dt><code class="literal">--clean-on-startup</code></dt><dd>
	 Cleans the package cache when the program starts
	 (equivalent to starting the program and immediately
	 selecting
	 Actions → Clean
	 package cache). You cannot use
	 this option and
	 “<code class="literal">--autoclean-on-startup</code>”,
	 “<code class="literal">-i</code>”, or
	 “<code class="literal">-u</code>” at the same time.
	 </dd><dt><code class="literal">-i</code></dt><dd>
	 Displays a download preview when the program starts
	 (equivalent to starting the program and immediately
	 pressing “g”). You cannot
	 use this option and
	 “<code class="literal">--autoclean-on-startup</code>”,
	 “<code class="literal">--clean-on-startup</code>”, or
	 “<code class="literal">-u</code>” at the same time.
	 </dd><dt><code class="literal">-S</code> <code>fname</code></dt><dd>
	 Loads the extended state information from <code>fname</code> instead of the
	 standard state file.
	 </dd><dt><code class="literal">-u</code></dt><dd>
	 Begins updating the package lists as soon as the program
	 starts. You cannot use this option and
	 “<code class="literal">--autoclean-on-startup</code>”,
	 “<code class="literal">--clean-on-startup</code>”, or
	 “<code class="literal">-i</code>” at the same time.
	 </dd></dl></div></div><div class="refsect1"><a id="idm9679"></a><h2>Environment</h2><div class="variablelist"><dl class="variablelist"><dt><code class="literal">HOME</code></dt><dd>
	 If <code class="filename">$HOME/.aptitude</code> exists, aptitude will store
	 its configuration file in <code class="filename">$HOME/.aptitude/config</code>.
 Otherwise, it will look up the current user's home directory
 using getpwuid(2)
 and place its configuration file there.
	</dd><dt><code class="literal">PAGER</code></dt><dd>
	 If this environment variable is set, aptitude will use it
	 to display changelogs when “<code class="literal">aptitude
	 changelog</code>” is invoked. If not set, it
	 defaults to <code class="literal">more</code>.
	</dd><dt><code class="literal">TMP</code></dt><dd>
	 If <code class="literal">TMPDIR</code> is unset, aptitude will store
	 its temporary files in <code class="literal">TMP</code> if that
	 variable is set. Otherwise, it will store them in
	 <code class="filename">/tmp</code>.
	</dd><dt><code class="literal">TMPDIR</code></dt><dd>
	 aptitude will store its temporary files in the directory
	 indicated by this environment variable. If
	 <code class="literal">TMPDIR</code> is not set, then
	 <code class="literal">TMP</code> will be used; if
	 <code class="literal">TMP</code> is also unset, then aptitude will
	 use <code class="filename">/tmp</code>.
	</dd></dl></div></div><div class="refsect1"><a id="idm9722"></a><h2>Files</h2><div class="variablelist"><dl class="variablelist"><dt><code class="filename">/var/lib/aptitude/pkgstates</code></dt><dd>
	 The file in which stored package states and some package
	 flags are stored.
	 </dd></dl></div><div class="variablelist"><dl class="variablelist"><dt>
	 <code class="filename">/etc/apt/apt.conf</code>,
	 <code class="filename">/etc/apt/apt.conf.d/*</code>,
	 <code class="filename">~/.aptitude/config</code>
	</dt><dd>
	 The configuration files for aptitude.
	 <code class="filename">~/.aptitude/config</code> overrides
	 <code class="filename">/etc/apt/apt.conf</code>. See
	 apt.conf(5)
	 for documentation of the format and contents of these
	 files.
	 </dd></dl></div></div><div class="refsect1"><a id="idm9744"></a><h2>See also</h2>
 apt-get(8), apt(8), <code class="filename">/usr/share/doc/aptitude/html/<code>lang</code>/index.html</code> from the package aptitude-doc-<code>lang</code>
 </div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="rn01.html"><img src="images/prev.gif" alt="Prev" /></a> </td><td width="20%" align="center"><a accesskey="u" href="rn01.html"><img src="images/up.gif" alt="Up" /></a></td><td width="40%" align="right"> <a accesskey="n" href="rn01re02.html"><img src="images/next.gif" alt="Next" /></a></td></tr><tr><td width="40%" align="left" valign="top">Command-line reference </td><td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.gif" alt="Home" /></a></td><td width="40%" align="right" valign="top"> aptitude-create-state-bundle</td></tr></table></div></body></html>

Back to Directory File Manager