Package: aptitude-common
Version: 0.8.13-6.1
Severity: minor
* What led up to the situation?
Checking for defects with
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page"
[Use "groff -e ' $' <file>" to find trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
troff: backtrace: file '<stdin>':1603
troff:<stdin>:1603: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.11.7-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
aptitude-common depends on no packages.
Versions of packages aptitude-common recommends:
ii aptitude 0.8.13-6.1
aptitude-common suggests no packages.
-- no debconf information
Input file is aptitude-curses.8
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
The same goes for man pages that are used as an input.
For a style guide use
mandoc -T lint
-.-
So any 'generator' should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
This is just a simple quality control measure.
The 'generator' may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Input text line longer than 80 bytes.
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
Not beginning each input sentence on a new line.
Lines should thus be shorter.
See man-pages(7), item 'semantic newline'.
-.-
The difference between the formatted output of the original and patched file
can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -u <out1> <out2>
and for groff, using
"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - "
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output of 'diff -u' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -b -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-.
Output from "mandoc -T lint aptitude-curses.8 ": (shortened list)
116 input text line longer than 80 bytes
12 skipping paragraph macro
1 whitespace at end of input line
-.-.
Output from "test-groff -mandoc -t -ww -b -z aptitude-curses.8 ": (shortened
list)
1 trailing space in the line
-.-.
Output from "mandoc -T lint aptitude-curses.8 ":
mandoc: aptitude-curses.8:3:15: STYLE: whitespace at end of input line
mandoc: aptitude-curses.8:52:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:56:221: STYLE: input text line longer than 80 bytes:
It allows the user t...
mandoc: aptitude-curses.8:58:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:59:189: STYLE: input text line longer than 80 bytes:
The first argument w...
mandoc: aptitude-curses.8:69:222: STYLE: input text line longer than 80 bytes:
command; if a packag...
mandoc: aptitude-curses.8:97:246: STYLE: input text line longer than 80 bytes:
If the package was n...
mandoc: aptitude-curses.8:121:81: STYLE: input text line longer than 80 bytes:
<\fIpackage\fR>: rem...
mandoc: aptitude-curses.8:128:137: STYLE: input text line longer than 80 bytes:
on hold: cancel any ...
mandoc: aptitude-curses.8:176:2: WARNING: skipping paragraph macro: br after br
mandoc: aptitude-curses.8:188:121: STYLE: input text line longer than 80 bytes:
to go back to the pr...
mandoc: aptitude-curses.8:209:229: STYLE: input text line longer than 80 bytes:
Satisfy the build\-d...
mandoc: aptitude-curses.8:211:109: STYLE: input text line longer than 80 bytes:
command, and the bui...
mandoc: aptitude-curses.8:223:137: STYLE: input text line longer than 80 bytes:
Mark packages as aut...
mandoc: aptitude-curses.8:240:147: STYLE: input text line longer than 80 bytes:
Mark packages to be ...
mandoc: aptitude-curses.8:271:164: STYLE: input text line longer than 80 bytes:
Cancels all schedule...
mandoc: aptitude-curses.8:282:273: STYLE: input text line longer than 80 bytes:
This command accepts...
mandoc: aptitude-curses.8:291:238: STYLE: input text line longer than 80 bytes:
Forbid a package fro...
mandoc: aptitude-curses.8:295:155: STYLE: input text line longer than 80 bytes:
will select the forb...
mandoc: aptitude-curses.8:302:136: STYLE: input text line longer than 80 bytes:
will remove the ban\...
mandoc: aptitude-curses.8:316:138: STYLE: input text line longer than 80 bytes:
Upgrades installed p...
mandoc: aptitude-curses.8:320:115: STYLE: input text line longer than 80 bytes:
reference manual)\&....
mandoc: aptitude-curses.8:329:82: STYLE: input text line longer than 80 bytes:
will attempt to upgr...
mandoc: aptitude-curses.8:330:81: STYLE: input text line longer than 80 bytes:
<\fIpackage\fR>s can...
mandoc: aptitude-curses.8:341:151: STYLE: input text line longer than 80 bytes:
It is sometimes nece...
mandoc: aptitude-curses.8:348:199: STYLE: input text line longer than 80 bytes:
Upgrades installed p...
mandoc: aptitude-curses.8:350:101: STYLE: input text line longer than 80 bytes:
and thus more likely...
mandoc: aptitude-curses.8:359:82: STYLE: input text line longer than 80 bytes:
will attempt to upgr...
mandoc: aptitude-curses.8:360:81: STYLE: input text line longer than 80 bytes:
<\fIpackage\fR>s can...
mandoc: aptitude-curses.8:381:2: WARNING: skipping paragraph macro: br after br
mandoc: aptitude-curses.8:396:166: STYLE: input text line longer than 80 bytes:
Searches for package...
mandoc: aptitude-curses.8:417:2: WARNING: skipping paragraph macro: br after br
mandoc: aptitude-curses.8:460:154: STYLE: input text line longer than 80 bytes:
Each search result i...
mandoc: aptitude-curses.8:483:260: STYLE: input text line longer than 80 bytes:
Displays detailed in...
mandoc: aptitude-curses.8:491:128: STYLE: input text line longer than 80 bytes:
is present on the co...
mandoc: aptitude-curses.8:497:81: STYLE: input text line longer than 80 bytes:
You can display info...
mandoc: aptitude-curses.8:499:98: STYLE: input text line longer than 80 bytes:
to the package name;...
mandoc: aptitude-curses.8:508:275: STYLE: input text line longer than 80 bytes:
If the verbosity lev...
mandoc: aptitude-curses.8:544:223: STYLE: input text line longer than 80 bytes:
Each version is list...
mandoc: aptitude-curses.8:545:182: STYLE: input text line longer than 80 bytes:
the documentation of...
mandoc: aptitude-curses.8:547:156: STYLE: input text line longer than 80 bytes:
If a package name co...
mandoc: aptitude-curses.8:555:138: STYLE: input text line longer than 80 bytes:
will display all the...
mandoc: aptitude-curses.8:573:97: STYLE: input text line longer than 80 bytes:
If the input is a se...
mandoc: aptitude-curses.8:575:90: STYLE: input text line longer than 80 bytes:
will automatically g...
mandoc: aptitude-curses.8:578:126: STYLE: input text line longer than 80 bytes:
will display a singl...
mandoc: aptitude-curses.8:609:120: STYLE: input text line longer than 80 bytes:
In addition to the a...
mandoc: aptitude-curses.8:619:299: STYLE: input text line longer than 80 bytes:
Adds a user tag to o...
mandoc: aptitude-curses.8:625:86: STYLE: input text line longer than 80 bytes:
User tags are arbitr...
mandoc: aptitude-curses.8:633:92: STYLE: input text line longer than 80 bytes:
Explains the reason ...
mandoc: aptitude-curses.8:635:245: STYLE: input text line longer than 80 bytes:
This command searche...
mandoc: aptitude-curses.8:653:119: STYLE: input text line longer than 80 bytes:
finds a dependency c...
mandoc: aptitude-curses.8:655:138: STYLE: input text line longer than 80 bytes:
produced in this cas...
mandoc: aptitude-curses.8:679:97: STYLE: input text line longer than 80 bytes:
<\fIpattern\fR>s are...
mandoc: aptitude-curses.8:683:107: STYLE: input text line longer than 80 bytes:
will begin its searc...
mandoc: aptitude-curses.8:685:286: STYLE: input text line longer than 80 bytes:
is or is not install...
mandoc: aptitude-curses.8:693:180: STYLE: input text line longer than 80 bytes:
will search for depe...
mandoc: aptitude-curses.8:705:2: WARNING: skipping paragraph macro: br after br
mandoc: aptitude-curses.8:707:169: STYLE: input text line longer than 80 bytes:
does not perform ful...
mandoc: aptitude-curses.8:717:393: STYLE: input text line longer than 80 bytes:
dependency chain\&. ...
mandoc: aptitude-curses.8:723:185: STYLE: input text line longer than 80 bytes:
can find will be dis...
mandoc: aptitude-curses.8:725:111: STYLE: input text line longer than 80 bytes:
This command returns...
mandoc: aptitude-curses.8:738:171: STYLE: input text line longer than 80 bytes:
Removes any cached p...
mandoc: aptitude-curses.8:743:94: STYLE: input text line longer than 80 bytes:
Downloads and displa...
mandoc: aptitude-curses.8:749:97: STYLE: input text line longer than 80 bytes:
to the package name;...
mandoc: aptitude-curses.8:773:370: STYLE: input text line longer than 80 bytes:
configuration direct...
mandoc: aptitude-curses.8:777:103: STYLE: input text line longer than 80 bytes:
reference manual)\&....
mandoc: aptitude-curses.8:779:116: STYLE: input text line longer than 80 bytes:
Dependencies in bina...
mandoc: aptitude-curses.8:787:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:788:246: STYLE: input text line longer than 80 bytes:
The following option...
mandoc: aptitude-curses.8:807:87: STYLE: input text line longer than 80 bytes:
to all packages that...
mandoc: aptitude-curses.8:876:177: STYLE: input text line longer than 80 bytes:
Install packages fro...
mandoc: aptitude-curses.8:885:81: STYLE: input text line longer than 80 bytes:
to output their resu...
mandoc: aptitude-curses.8:887:93: STYLE: input text line longer than 80 bytes:
will add whitespace ...
mandoc: aptitude-curses.8:911:94: STYLE: input text line longer than 80 bytes:
is often useful in c...
mandoc: aptitude-curses.8:929:136: STYLE: input text line longer than 80 bytes:
Download packages to...
mandoc: aptitude-curses.8:946:121: STYLE: input text line longer than 80 bytes:
will display a packa...
mandoc: aptitude-curses.8:966:123: STYLE: input text line longer than 80 bytes:
Try hard to fix the ...
mandoc: aptitude-curses.8:1014:105: STYLE: input text line longer than 80
bytes: to group versions by...
mandoc: aptitude-curses.8:1087:180: STYLE: input text line longer than 80
bytes: has performed (/var/...
mandoc: aptitude-curses.8:1108:88: STYLE: input text line longer than 80 bytes:
to be displayed; all...
mandoc: aptitude-curses.8:1126:117: STYLE: input text line longer than 80
bytes: may appear multiple ...
mandoc: aptitude-curses.8:1134:132: STYLE: input text line longer than 80
bytes: will be printed\&. I...
mandoc: aptitude-curses.8:1138:180: STYLE: input text line longer than 80
bytes: has performed (/var/...
mandoc: aptitude-curses.8:1148:175: STYLE: input text line longer than 80
bytes: Set some standard lo...
mandoc: aptitude-curses.8:1156:81: STYLE: input text line longer than 80 bytes:
from installing any ...
mandoc: aptitude-curses.8:1197:83: STYLE: input text line longer than 80 bytes:
will list packages i...
mandoc: aptitude-curses.8:1203:112: STYLE: input text line longer than 80
bytes: Prepending the order...
mandoc: aptitude-curses.8:1215:83: STYLE: input text line longer than 80 bytes:
/tmp/my\-log\&. For ...
mandoc: aptitude-curses.8:1224:156: STYLE: input text line longer than 80
bytes: Always display a pro...
mandoc: aptitude-curses.8:1236:109: STYLE: input text line longer than 80
bytes: (its default), then ...
mandoc: aptitude-curses.8:1238:155: STYLE: input text line longer than 80
bytes: will also purge them...
mandoc: aptitude-curses.8:1252:156: STYLE: input text line longer than 80
bytes: Suppress all increme...
mandoc: aptitude-curses.8:1263:91: STYLE: input text line longer than 80 bytes:
may be used to direc...
mandoc: aptitude-curses.8:1275:94: STYLE: input text line longer than 80 bytes:
treat recommendation...
mandoc: aptitude-curses.8:1278:100: STYLE: input text line longer than 80
bytes: ~/\&.aptitude/config...
mandoc: aptitude-curses.8:1288:94: STYLE: input text line longer than 80 bytes:
Treat recommendation...
mandoc: aptitude-curses.8:1314:89: STYLE: input text line longer than 80 bytes:
from all packages th...
mandoc: aptitude-curses.8:1357:135: STYLE: input text line longer than 80
bytes: In command\-line mod...
mandoc: aptitude-curses.8:1359:109: STYLE: input text line longer than 80
bytes: privileges\&. In the...
mandoc: aptitude-curses.8:1370:254: STYLE: input text line longer than 80
bytes: algorithm to solve t...
mandoc: aptitude-curses.8:1388:166: STYLE: input text line longer than 80
bytes: For commands that mo...
mandoc: aptitude-curses.8:1390:81: STYLE: input text line longer than 80 bytes:
with no arguments\&....
mandoc: aptitude-curses.8:1429:132: STYLE: input text line longer than 80
bytes: runs if the output i...
mandoc: aptitude-curses.8:1461:154: STYLE: input text line longer than 80
bytes: will display a summa...
mandoc: aptitude-curses.8:1469:123: STYLE: input text line longer than 80
bytes: to summarize each de...
mandoc: aptitude-curses.8:1629:88: STYLE: input text line longer than 80 bytes:
will install package...
mandoc: aptitude-curses.8:1631:94: STYLE: input text line longer than 80 bytes:
This will affect the...
mandoc: aptitude-curses.8:1664:163: STYLE: input text line longer than 80
bytes: When installing or r...
mandoc: aptitude-curses.8:1669:167: STYLE: input text line longer than 80
bytes: In the preview displ...
mandoc: aptitude-curses.8:1705:97: STYLE: input text line longer than 80 bytes:
This option will als...
mandoc: aptitude-curses.8:1727:207: STYLE: input text line longer than 80
bytes: By default and when ...
mandoc: aptitude-curses.8:1738:94: STYLE: input text line longer than 80 bytes:
actions, such as rem...
mandoc: aptitude-curses.8:1747:114: STYLE: input text line longer than 80
bytes: Show how much disk s...
mandoc: aptitude-curses.8:1753:151: STYLE: input text line longer than 80
bytes: The following option...
mandoc: aptitude-curses.8:1757:114: STYLE: input text line longer than 80
bytes: Deletes old download...
mandoc: aptitude-curses.8:1767:110: STYLE: input text line longer than 80
bytes: Cleans the package c...
mandoc: aptitude-curses.8:1777:112: STYLE: input text line longer than 80
bytes: Displays a download ...
mandoc: aptitude-curses.8:1794:97: STYLE: input text line longer than 80 bytes:
Begins updating the ...
mandoc: aptitude-curses.8:1801:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:1809:98: STYLE: input text line longer than 80 bytes:
$HOME/\&.aptitude/co...
mandoc: aptitude-curses.8:1839:92: STYLE: input text line longer than 80 bytes:
will store its tempo...
mandoc: aptitude-curses.8:1851:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:1868:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:1874:2: WARNING: skipping paragraph macro: PP after SH
mandoc: aptitude-curses.8:1882:99: STYLE: input text line longer than 80 bytes:
Main maintainer afte...
mandoc: aptitude-curses.8:1885:2: WARNING: skipping paragraph macro: br after SH
mandoc: aptitude-curses.8:1891:245: STYLE: input text line longer than 80
bytes: This manual page is ...
mandoc: aptitude-curses.8:1893:240: STYLE: input text line longer than 80
bytes: This manual page is ...
mandoc: aptitude-curses.8:1895:208: STYLE: input text line longer than 80
bytes: You should have rece...
-.-.
Remove space characters at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
3:.\" Author:
1603:
-.-.
Strings longer than 3/4 of a standard line length (80)
Use "\:" to split the string at the end of an output line, for example a
long URLs (web address)
1095 \fB\-\-log\-level=\fR\fB<\fIlevel\fR>\fR,
\fB\-\-log\-level=\fR\fB<\fIcategory\fR>\fR\fB:\fR\fB<\fIlevel\fR>\fR
1118 \fB\-\-log\-level=\fR\fB<\fIcategory\fR>\fR\fB:\fR\fB<\fIlevel\fR>\fR
1129 \fB\-\-log\-level=aptitude\&.resolver\&.hints\&.match:trace\fR, then
messages in
1149 \fB\-\-log\-level=aptitude\&.resolver\&.search:trace
\-\-log\-level=aptitude\&.resolver\&.search\&.tiers:info\fR\&.
-.-.
Wrong distance between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
56: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\&.
59:The first argument which does not begin with a hyphen (\(lq\fB\-\fR\(rq) is
considered to be an action that the program should perform\&. If an action is
not specified on the command\-line,
67:Install one or more packages\&. The packages should be listed after the
78:\(lq\fBaptitude install apt=0\&.3\&.1\fR\(rq\&. Similarly, to select a
package from a particular archive, append
81:\(lq\fBaptitude install apt/experimental\fR\(rq\&. You cannot specify both
an archive and a version for a package\&.
87:to the name of the package\&. For example,
90:\fBwesnoth\fR, not remove it\&. The following override specifiers are
available:
97: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
135:at its current version: cancel any installation, removal, or upgrade\&.
Unlike
182:\fBaptitude\fR\*(Aqs stored information about what actions to perform\&.
Therefore, if you issue (e\&.g\&.) the command
209: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
223:Mark packages as automatically installed or manually installed,
respectively\&. Packages are specified in exactly the same way as for the
225:command\&. For instance,
240: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
242:command\&. For instance,
282:This command accepts package names or patterns as arguments\&. If the
string contains a tilde character (\(lq\fB~\fR\(rq) or a question mark
(\(lq\fB?\fR\(rq), it will be treated as a search pattern and every package
matching the pattern will be considered (see the section
291: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\&.
295: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
302:will remove the ban\&. To remove the forbidden version without installing
the candidate version, the current version should be appended:
316:Upgrades installed packages to their most recent version\&. Installed
packages will not be removed unless they are unused (see the section
320:reference manual)\&. Packages which are not currently installed may be
installed to resolve dependencies unless the
327:will attempt to upgrade every package that can be upgraded\&. Otherwise,
329:will attempt to upgrade only the packages which it is instructed to
upgrade\&. The
341: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
348: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
350:and thus more likely to perform unwanted actions\&. However, it is capable
of upgrading packages that
357:will attempt to upgrade every package that can be upgraded\&. Otherwise,
359:will attempt to upgrade only the packages which it is instructed to
upgrade\&. The
396: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,
401:\(lqedit\(rq\&. For more information on search patterns, see the section
427:\(lq\fBedit\fR\(rq\&. As described in the
433:patterns match\&. Thus, the command
460: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
464:\fBv\fR, 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
467:\fBp\fR, meaning that the package and its configuration files will be
removed\&. If the third character is
474:reference guide\&. To customize the output of
483:Displays detailed information about one or more packages\&. If a package
name contains a tilde character (\(lq\fB~\fR\(rq) or a question mark
(\(lq\fB?\fR\(rq), it will be treated as a search pattern and all matching
packages will be displayed (see the section
491:is present on the command\-line), information about all versions of the
package is displayed\&. Otherwise, information about the
506:\fB/sid\fR\&. If either of these is present, then only the version you
request will be displayed, regardless of the verbosity level\&.
508:If the verbosity level is 1 or greater, the package\*(Aqs 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\&.
544: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
545:the documentation of \fBaptitude search\fR\&. 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\&.
553:reference manual)\&. This means that, for instance,
575:will automatically group the output by package, as shown above\&. You can
disable this via
610:\fB\-F\fR\&. The order in which versions are displayed can be controlled by
the command\-line option
611:\fB\-\-sort\fR\&. To prevent
619:Adds a user tag to or removes a user tag from the selected group of
packages\&. If a package name contains a tilde (\(lq\fB~\fR\(rq) or question
mark (\(lq\fB?\fR\(rq), 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
625:User tags are arbitrary strings associated with a package\&. They can be
used with the
635: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:
653:finds a dependency chain that installs the package named on the command
line, as above\&. Note that the dependency that
655:produced in this case is only a suggestion\&. This is because no package
currently installed on this computer depends on or recommends the
683:will begin its search at these patterns\&. That is, the first package in
the chain it prints to explain why
685: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 (\(lq\fB~\fR\(rq) or a question mark (\(lq\fB?\fR\(rq), in
which case they are treated as search patterns (see the section
693: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\&.
707: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,
717: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\&.
723: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\&.
738: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\&.
747:is downloaded\&. You can select a particular version of a package by
appending
773:configuration directory (\fB/etc/apt\fR) 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
777:reference manual)\&. Any existing package database files in the output
directory will be overwritten\&.
788: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\*(Aqt apply to particular commands and will be
ignored by those commands\&.
833:command\&. The pattern is a search pattern as described in the section
870:\fBtrue\fR), allow the dependency resolver to install new packages\&. This
option takes effect regardless of the value of
876: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\*(Aqs security\&.
885:to output their results without any special formatting\&. In particular:
normally
888:\(lqcolumns\(rq\&. 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\&.
929:Download packages to the package cache as necessary, but do not install or
remove anything\&. By default, the package cache is stored in
942:commands\&. For instance, passing
976:resolver to solve them\&. Unlike the
979:\fB\-\-safe\-resolver\fR, 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\&.
990:command groups its output\&. The following values are recognized:
1002:\(lq\fBunstable\fR\(rq, etc)\&. If a package occurs in several archives,
it will be displayed in each of them\&.
1071:Display a brief help message\&. Identical to the
1083:\(lq\fB\-\fR\(rq, 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\&.
1087:has performed (/var/log/aptitude); the log messages written using this
configuration include internal program events, errors, and debugging
messages\&. See the command\-line option
1102:or higher\&. For instance, setting the log level to
1108:to be displayed; all others will be hidden\&. Valid log levels (in
descending order) are
1115:\fBtrace\fR\&. The default log level is
1134: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\&.
1138:has performed (/var/log/aptitude); the log messages written using this
configuration include internal program events, errors, and debugging
messages\&. See the command\-line option
1148: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
1161:\fBtrue\fR), forbid the dependency resolver from installing new
packages\&. This option takes effect regardless of the value of
1193:commands should be displayed\&. For instance, passing
1215:/tmp/my\-log\&. For more information on configuration file options, see
the section
1238:will also purge them, removing their configuration files and perhaps other
important data\&. For more information about which packages are considered to be
1244:\fITHIS OPTION CAN CAUSE DATA LOSS! DO NOT USE IT UNLESS YOU KNOW WHAT YOU
ARE DOING!\fR
1252:Suppress all incremental progress indicators, thus making the output
loggable\&. This may be supplied multiple times to make the program quieter,
but unlike
1278:~/\&.aptitude/config)\&. Packages previously installed due to
recommendations will not be removed\&.
1340:command\&. The pattern is a search pattern as described in the section
1357:In command\-line mode, print the actions that would normally be performed,
but don\*(Aqt actually perform them\&. This does not require
1359:privileges\&. In the visual interface, always open the cache in read\-only
mode regardless of whether you are
1370: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\*(Aqs default candidate version\&. It is
the same algorithm used in
1374:\fBaptitude safe\-upgrade\fR\&. Because
1388:For commands that modify package states, schedule operations to be
performed in the future, but don\*(Aqt perform them\&. You can execute
scheduled actions by running
1390:with no arguments\&. This is equivalent to making the corresponding
selections in
1404:command shows package names\&. The following settings are allowed:
1461:will display a summary of the actions performed by the resolver before
printing the installation preview\&. This is equivalent to the configuration
option
1469:to summarize each dependency chain that it outputs, rather than displaying
it in long form\&. If this option is present and
1502:\fBfirst\-package\fR: display the first package in each chain\&. This is
the default value of
1627:Set the release from which packages should be installed\&. For instance,
1649:\fBshow\fR) to display extra information\&. This may be supplied multiple
times to get more and more information\&.
1669:In the preview displayed before packages are installed or removed, show
which manually installed package requires each automatically installed
package\&. For instance:
1689:\fBAptitude::CmdLine::Verbose\fR, this displays the entire chain of
dependencies that lead each package to be installed\&. For instance:
1705:This option will also describe why packages are being removed, as shown
above\&. In this example,
1727: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\&.
1736:\(lqyes\(rq\&. In particular, suppresses the prompt that appears when
installing, upgrading, or removing packages\&. Prompts for
1738:actions, such as removing essential packages, will still be displayed\&.
This option overrides
1758:Actions \(-> Clean obsolete files)\&. You cannot use this option and
1768:Actions \(-> Clean package cache)\&. You cannot use this option and
1778:\(lqg\(rq)\&. You cannot use this option and
1794:Begins updating the package lists as soon as the program starts\&. You
cannot use this option and
1809:$HOME/\&.aptitude/config\&. Otherwise, it will look up the current
user\*(Aqs home directory using
1820:is invoked\&. If not set, it defaults to
1832:if that variable is set\&. Otherwise, it will store them in
1839:will store its temporary files in the directory indicated by this
environment variable\&. If
1863:/etc/apt/apt\&.conf\&. See
1880:\fBManuel A. Fernandez Montecelo\fR <\&m...@debian.org\&>
1889:Copyright 2014\-2016 Manuel A\&. Fernandez Montecelo
1893:This manual page is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more
details\&.
-.-.
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Lines longer than 1023 bytes cat force the mailer to use "quote-printable"
encoding for the transmission.
Line 34, length 90
\fBaptitude\fR [<\fIoptions\fR>...] {autoclean | clean | forget\-new |
keep\-all | update}
Line 36, length 89
\fBaptitude\fR [<\fIoptions\fR>...] {full\-upgrade | safe\-upgrade}
[<\fIpackages\fR>...]
Line 38, length 242
\fBaptitude\fR [<\fIoptions\fR>...] {build\-dep | build\-depends | changelog |
download | forbid\-version | hold | install | markauto | purge | reinstall |
remove | show | showsrc | source | unhold | unmarkauto | versions}
<\fIpackages\fR>...
Line 40, length 83
\fBaptitude\fR extract\-cache\-subset <\fIoutput\-directory\fR>
<\fIpackages\fR>...
Line 44, length 104
\fBaptitude\fR [<\fIoptions\fR>...] {add\-user\-tag | remove\-user\-tag}
<\fItag\fR> <\fIpackages\fR>...
Line 46, length 90
\fBaptitude\fR [<\fIoptions\fR>...] {why | why\-not} [<\fIpatterns\fR>...]
<\fIpackage\fR>
Line 48, length 101
\fBaptitude\fR [\-S\ <\fIfname\fR>] [\-\-autoclean\-on\-startup |
\-\-clean\-on\-startup | \-i | \-u]
Line 56, length 221
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\&.
Line 59, length 189
The first argument which does not begin with a hyphen (\(lq\fB\-\fR\(rq) is
considered to be an action that the program should perform\&. If an action is
not specified on the command\-line,
Line 69, length 222
command; if a package name contains a tilde character (\(lq\fB~\fR\(rq) or a
question mark (\(lq\fB?\fR\(rq), it will be treated as a search pattern and
every package matching the pattern will be installed (see the section
Line 78, length 112
\(lq\fBaptitude install apt=0\&.3\&.1\fR\(rq\&. Similarly, to select a package
from a particular archive, append
Line 81, length 116
\(lq\fBaptitude install apt/experimental\fR\(rq\&. You cannot specify both an
archive and a version for a package\&.
Line 97, length 246
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
Line 121, length 81
<\fIpackage\fR>: remove it and all its associated configuration and data
files\&.
Line 128, length 137
on hold: cancel any active installation, upgrade, or removal, and prevent this
package from being automatically upgraded in the future\&.
Line 182, length 119
\fBaptitude\fR\*(Aqs stored information about what actions to perform\&.
Therefore, if you issue (e\&.g\&.) the command
Line 188, length 121
to go back to the previous state (and possibly undo installations or upgrades
to other packages that were affected by the
Line 198, length 111
\(lq\fBinstall\fR\(rq, but apply the named action to all packages given on the
command line for which it is not
Line 209, length 229
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
Line 211, length 109
command, and the build\-dependencies of the source packages that build those
binary packages are satisfied\&.
Line 223, length 137
Mark packages as automatically installed or manually installed, respectively\&.
Packages are specified in exactly the same way as for the
Line 240, length 147
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
Line 271, length 164
Cancels all scheduled actions on all packages; any packages whose sticky state
indicates an installation, removal, or upgrade will have this sticky state
cleared\&.
Line 282, length 273
This command accepts package names or patterns as arguments\&. If the string
contains a tilde character (\(lq\fB~\fR\(rq) or a question mark
(\(lq\fB?\fR\(rq), it will be treated as a search pattern and every package
matching the pattern will be considered (see the section
Line 291, length 238
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\&.
Line 295, length 155
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
Line 302, length 136
will remove the ban\&. To remove the forbidden version without installing the
candidate version, the current version should be appended:
Line 316, length 138
Upgrades installed packages to their most recent version\&. Installed packages
will not be removed unless they are unused (see the section
Line 320, length 115
reference manual)\&. Packages which are not currently installed may be
installed to resolve dependencies unless the
Line 329, length 82
will attempt to upgrade only the packages which it is instructed to upgrade\&.
The
Line 330, length 81
<\fIpackage\fR>s can be extended with suffixes in the same manner as arguments
to
Line 341, length 151
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
Line 348, length 199
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
Line 350, length 101
and thus more likely to perform unwanted actions\&. However, it is capable of
upgrading packages that
Line 359, length 82
will attempt to upgrade only the packages which it is instructed to upgrade\&.
The
Line 360, length 81
<\fIpackage\fR>s can be extended with suffixes in the same manner as arguments
to
Line 396, length 166
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,
Line 452, length 81
pi apt\-build \- frontend to apt to build, optimize and
in
Line 453, length 84
cp apt\-file \- APT package searching utility \-\-
command\-
Line 460, length 154
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
Line 462, length 95
\fBc\fR, meaning that the package was deleted but its configuration files
remain on the system,
Line 464, length 210
\fBv\fR, 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
Line 467, length 106
\fBp\fR, meaning that the package and its configuration files will be
removed\&. If the third character is
Line 483, length 260
Displays detailed information about one or more packages\&. If a package name
contains a tilde character (\(lq\fB~\fR\(rq) or a question mark
(\(lq\fB?\fR\(rq), it will be treated as a search pattern and all matching
packages will be displayed (see the section
Line 491, length 128
is present on the command\-line), information about all versions of the package
is displayed\&. Otherwise, information about the
Line 497, length 81
You can display information about a different version of the package by
appending
Line 499, length 98
to the package name; you can display the version from a particular archive or
release by appending
Line 506, length 134
\fB/sid\fR\&. If either of these is present, then only the version you request
will be displayed, regardless of the verbosity level\&.
Line 508, length 275
If the verbosity level is 1 or greater, the package\*(Aqs 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\&.
Line 536, length 82
p 1:1\&.4\&.5\-1
100
Line 537, length 82
p 1:1\&.6\&.5\-1 unstable
500
Line 544, length 223
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
Line 545, length 182
the documentation of \fBaptitude search\fR\&. 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\&.
Line 547, length 156
If a package name contains a tilde character (\(lq\fB~\fR\(rq) or a question
mark (\(lq\fB?\fR\(rq), it will be treated as a search pattern and all matching
Line 555, length 138
will display all the versions that are currently installed on the system and
nothing else, not even other versions of the same packages\&.
Line 573, length 97
If the input is a search pattern, or if more than one package\*(Aqs versions
are to be displayed,
Line 575, length 90
will automatically group the output by package, as shown above\&. You can
disable this via
Line 578, length 126
will display a single list of all the versions that were found and
automatically include the package name in each output line:
Line 585, length 82
i exim4\-daemon\-light 4\&.71\-3
100
Line 586, length 82
p exim4\-daemon\-light 4\&.71\-4 unstable
500
Line 587, length 83
p exim4\-daemon\-light\-dbg 4\&.71\-4 unstable
500
Line 600, length 102
$ aptitude versions \-\-show\-package\-names=never \-\-group\-by=none
\*(Aq~nexim4\-daemon\-light\*(Aq
Line 609, length 120
In addition to the above options, the information printed for each version can
be controlled by the command\-line option
Line 610, length 100
\fB\-F\fR\&. The order in which versions are displayed can be controlled by the
command\-line option
Line 619, length 299
Adds a user tag to or removes a user tag from the selected group of packages\&.
If a package name contains a tilde (\(lq\fB~\fR\(rq) or question mark
(\(lq\fB?\fR\(rq), 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
Line 625, length 86
User tags are arbitrary strings associated with a package\&. They can be used
with the
Line 633, length 92
Explains the reason that a particular package should or cannot be installed on
the system\&.
Line 635, length 245
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:
Line 653, length 119
finds a dependency chain that installs the package named on the command line,
as above\&. Note that the dependency that
Line 655, length 138
produced in this case is only a suggestion\&. This is because no package
currently installed on this computer depends on or recommends the
Line 679, length 97
<\fIpattern\fR>s are present (in addition to the mandatory last argument, which
should be a valid
Line 683, length 107
will begin its search at these patterns\&. That is, the first package in the
chain it prints to explain why
Line 685, length 286
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 (\(lq\fB~\fR\(rq) or a question mark (\(lq\fB?\fR\(rq), in which case
they are treated as search patterns (see the section
Line 693, length 180
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\&.
Line 707, length 169
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,
Line 717, length 393
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\&.
Line 723, length 185
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\&.
Line 725, length 111
This command returns 0 if successful, 1 if no explanation could be constructed,
and \-1 if an error occurred\&.
Line 738, length 171
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\&.
Line 743, length 94
Downloads and displays the Debian changelog for each of the given source or
binary packages\&.
Line 749, length 97
to the package name; you can select the version from a particular archive or
release by appending
Line 773, length 370
configuration directory (\fB/etc/apt\fR) 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
Line 777, length 103
reference manual)\&. Any existing package database files in the output
directory will be overwritten\&.
Line 779, length 116
Dependencies in binary package stanzas will be rewritten to remove references
to packages not in the selected set\&.
Line 788, length 246
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\*(Aqt apply to particular commands and will be
ignored by those commands\&.
Line 807, length 87
to all packages that are installed, removed, or upgraded by this command as if
with the
Line 840, length 84
\fBaptitude safe\-upgrade \-\-add\-user\-tag\-to
"new\-installs,?action(install)"\fR
Line 856, length 102
\fBtrue\fR), allow the dependency resolver to install upgrades for packages
regardless of the value of
Line 870, length 121
\fBtrue\fR), allow the dependency resolver to install new packages\&. This
option takes effect regardless of the value of
Line 876, length 177
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\*(Aqs security\&.
Line 885, length 81
to output their results without any special formatting\&. In particular:
normally
Line 887, length 93
will add whitespace or truncate search results in an attempt to fit its results
into vertical
Line 888, length 174
\(lqcolumns\(rq\&. 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\&.
Line 891, length 85
\(lq\fBaptitude search \-F \*(Aq%p %V\*(Aq \-\-disable\-columns
libedataserver\fR\(rq
Line 911, length 94
is often useful in combination with a custom display format set using the
command\-line option
Line 921, length 93
\fBfull\-upgrade\fR, etc), show brief explanations of automatic installations
and removals\&.
Line 929, length 136
Download packages to the package cache as necessary, but do not install or
remove anything\&. By default, the package cache is stored in
Line 946, length 121
will display a package\*(Aqs name, followed by its currently installed version
and its candidate version (see the section
Line 966, length 123
Try hard to fix the dependencies of broken packages, even if it means ignoring
the actions requested on the command line\&.
Line 979, length 210
\fB\-\-safe\-resolver\fR, 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\&.
Line 1002, length 112
\(lq\fBunstable\fR\(rq, etc)\&. If a package occurs in several archives, it
will be displayed in each of them\&.
Line 1014, length 105
to group versions by their package unless there is exactly one argument and it
is not a search pattern\&.
Line 1083, length 171
\(lq\fB\-\fR\(rq, 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\&.
Line 1087, length 180
has performed (/var/log/aptitude); the log messages written using this
configuration include internal program events, errors, and debugging
messages\&. See the command\-line option
Line 1095, length 111
\fB\-\-log\-level=\fR\fB<\fIlevel\fR>\fR,
\fB\-\-log\-level=\fR\fB<\fIcategory\fR>\fR\fB:\fR\fB<\fIlevel\fR>\fR
Line 1108, length 88
to be displayed; all others will be hidden\&. Valid log levels (in descending
order) are
Line 1126, length 117
may appear multiple times on the command line; the most specific setting is the
one that takes effect, so if you pass
Line 1134, length 132
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\&.
Line 1138, length 180
has performed (/var/log/aptitude); the log messages written using this
configuration include internal program events, errors, and debugging
messages\&. See the command\-line option
Line 1148, length 175
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
Line 1149, length 115
\fB\-\-log\-level=aptitude\&.resolver\&.search:trace
\-\-log\-level=aptitude\&.resolver\&.search\&.tiers:info\fR\&.
Line 1156, length 81
from installing any new packages; when the safe resolver is being used
(i\&.e\&.,
Line 1161, length 127
\fBtrue\fR), forbid the dependency resolver from installing new packages\&.
This option takes effect regardless of the value of
Line 1175, length 108
\fBtrue\fR), forbid the dependency resolver from installing upgrades for
packages regardless of the value of
Line 1197, length 83
will list packages in order according to their size when installed (see the
section
Line 1203, length 112
Prepending the order keyword with a tilde character (\fB~\fR) reverses the
order from ascending to descending\&.
Line 1215, length 83
/tmp/my\-log\&. For more information on configuration file options, see the
section
Line 1224, length 156
Always display a prompt before downloading, installing or removing packages,
even when no actions other than those explicitly requested will be performed\&.
Line 1236, length 109
(its default), then in addition to removing each package that is no longer
required by any installed package,
Line 1238, length 155
will also purge them, removing their configuration files and perhaps other
important data\&. For more information about which packages are considered to be
Line 1244, length 88
\fITHIS OPTION CAN CAUSE DATA LOSS! DO NOT USE IT UNLESS YOU KNOW WHAT YOU ARE
DOING!\fR
Line 1252, length 156
Suppress all incremental progress indicators, thus making the output
loggable\&. This may be supplied multiple times to make the program quieter,
but unlike
Line 1263, length 91
may be used to directly set the amount of quietness (for instance, to override
a setting in
Line 1275, length 94
treat recommendations as dependencies when installing new packages (this
overrides settings in
Line 1278, length 100
~/\&.aptitude/config)\&. Packages previously installed due to recommendations
will not be removed\&.
Line 1288, length 94
Treat recommendations as dependencies when installing new packages (this
overrides settings in
Line 1314, length 89
from all packages that are installed, removed, or upgraded by this command as
if with the
Line 1347, length 89
\fBaptitude safe\-upgrade \-\-remove\-user\-tag\-from
"not\-upgraded,?action(upgrade)"\fR
Line 1357, length 135
In command\-line mode, print the actions that would normally be performed, but
don\*(Aqt actually perform them\&. This does not require
Line 1359, length 109
privileges\&. In the visual interface, always open the cache in read\-only mode
regardless of whether you are
Line 1370, length 254
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\*(Aqs default candidate version\&. It is the
same algorithm used in
Line 1388, length 166
For commands that modify package states, schedule operations to be performed in
the future, but don\*(Aqt perform them\&. You can execute scheduled actions by
running
Line 1390, length 81
with no arguments\&. This is equivalent to making the corresponding selections
in
Line 1429, length 132
runs if the output is not grouped by package, and either there is a
pattern\-matching argument or there is more than one argument\&.
Line 1461, length 154
will display a summary of the actions performed by the resolver before printing
the installation preview\&. This is equivalent to the configuration option
Line 1469, length 123
to summarize each dependency chain that it outputs, rather than displaying it
in long form\&. If this option is present and
Line 1472, length 99
\(lq\fBno\-summary\fR\(rq, chains that contain Suggests dependencies will not
be displayed: combine
Line 1502, length 93
\fBfirst\-package\fR: display the first package in each chain\&. This is the
default value of
Line 1515, length 139
\fBfirst\-package\-and\-type\fR: display the first package in each chain, along
with the strength of the weakest dependency in the chain\&.
Line 1526, length 96
\fBall\-packages\fR: briefly display each chain of dependencies leading to the
target package\&.
Line 1537, length 166
\fBall\-packages\-with\-dep\-versions\fR: briefly display each chain of
dependencies leading to the target package, including the target version of
each dependency\&.
Line 1582, length 125
cupsys\-driver\-gutenprint D: cups\-driver\-gutenprint D: cups R:
foomatic\-filters R: foomatic\-db\-engine D: foomatic\-db
Line 1583, length 86
foomatic\-filters\-ppds D: foomatic\-filters R: foomatic\-db\-engine D:
foomatic\-db
Line 1584, length 165
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
Line 1585, length 106
wine D: libwine\-print D: cups\-bsd R: cups R: foomatic\-filters R:
foomatic\-db\-engine D: foomatic\-db
Line 1592, length 84
$ aptitude \-v \-\-show\-summary=all\-packages\-with\-dep\-versions why
foomatic\-db
Line 1594, length 194
cupsys\-driver\-gutenprint D: cups\-driver\-gutenprint (>= 5\&.0\&.2\-4) D:
cups (>= 1\&.3\&.0) R: foomatic\-filters (>= 4\&.0) R: foomatic\-db\-engine (>=
4\&.0) D: foomatic\-db (>= 20090301)
Line 1595, length 111
foomatic\-filters\-ppds D: foomatic\-filters R: foomatic\-db\-engine (>=
4\&.0) D: foomatic\-db (>= 20090301)
Line 1596, length 253
kde D: kdeadmin (>= 4:3\&.5\&.5) R: system\-config\-printer\-kde (>=
4:4\&.2\&.2\-1) D: system\-config\-printer (>= 1\&.0\&.0) R: hal\-cups\-utils
D: cups R: foomatic\-filters (>= 4\&.0) R: foomatic\-db\-engine (>= 4\&.0) D:
foomatic\-db (>= 20090301)
Line 1597, length 160
wine D: libwine\-print (= 1\&.1\&.15\-1) D: cups\-bsd R: cups R:
foomatic\-filters (>= 4\&.0) R: foomatic\-db\-engine (>= 4\&.0) D: foomatic\-db
(>= 20090301)
Line 1601, length 108
foomatic\-gui D: python\-foomatic (>= 0\&.7\&.9\&.2) D: foomatic\-db\-engine
D: foomatic\-db (>= 20090301)
Line 1629, length 88
will install packages from the experimental distribution unless you specify
otherwise\&.
Line 1631, length 94
This will affect the default candidate version of packages according to the
rules described in
Line 1649, length 115
\fBshow\fR) to display extra information\&. This may be supplied multiple times
to get more and more information\&.
Line 1664, length 163
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\&.
Line 1669, length 167
In the preview displayed before packages are installed or removed, show which
manually installed package requires each automatically installed package\&. For
instance:
Line 1689, length 136
\fBAptitude::CmdLine::Verbose\fR, this displays the entire chain of
dependencies that lead each package to be installed\&. For instance:
Line 1705, length 97
This option will also describe why packages are being removed, as shown
above\&. In this example,
Line 1727, length 207
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\&.
Line 1736, length 128
\(lqyes\(rq\&. In particular, suppresses the prompt that appears when
installing, upgrading, or removing packages\&. Prompts for
Line 1738, length 94
actions, such as removing essential packages, will still be displayed\&. This
option overrides
Line 1747, length 114
Show how much disk space will be used or freed by the individual packages being
installed, upgraded, or removed\&.
Line 1753, length 151
The following options apply to the visual mode of the program, but are
primarily for internal use; you generally won\*(Aqt need to use them yourself\&.
Line 1757, length 114
Deletes old downloaded files when the program starts (equivalent to starting
the program and immediately selecting
Line 1767, length 110
Cleans the package cache when the program starts (equivalent to starting the
program and immediately selecting
Line 1777, length 112
Displays a download preview when the program starts (equivalent to starting the
program and immediately pressing
Line 1794, length 97
Begins updating the package lists as soon as the program starts\&. You cannot
use this option and
Line 1809, length 98
$HOME/\&.aptitude/config\&. Otherwise, it will look up the current user\*(Aqs
home directory using
Line 1839, length 92
will store its temporary files in the directory indicated by this environment
variable\&. If
Line 1882, length 99
Main maintainer after Daniel Burrows, documentation about new features,
corrections and formatting.
Line 1891, length 245
This manual page is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at your option) any
later version\&.
Line 1893, length 240
This manual page is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more
details\&.
Line 1895, length 208
You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc\&., 51
Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA\&.
-.-.
Add a zero (0) in front of a decimal fraction that begins with a period
(.)
191:.sp .5v
390:.sp .5v
439:.sp .5v
711:.sp .5v
-.-.
Show if docman-to-man created this
4:.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.-.
No need for "\&" to be in front of a period (.) if not at the beginning of
a line.
56: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\&.
59:The first argument which does not begin with a hyphen (\(lq\fB\-\fR\(rq) is
considered to be an action that the program should perform\&. If an action is
not specified on the command\-line,
67:Install one or more packages\&. The packages should be listed after the
78:\(lq\fBaptitude install apt=0\&.3\&.1\fR\(rq\&. Similarly, to select a
package from a particular archive, append
81:\(lq\fBaptitude install apt/experimental\fR\(rq\&. You cannot specify both
an archive and a version for a package\&.
87:to the name of the package\&. For example,
90:\fBwesnoth\fR, not remove it\&. The following override specifiers are
available:
97: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
135:at its current version: cancel any installation, removal, or upgrade\&.
Unlike
182:\fBaptitude\fR\*(Aqs stored information about what actions to perform\&.
Therefore, if you issue (e\&.g\&.) the command
209: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
215:is present, only architecture\-dependent build dependencies (i\&.e\&., not
223:Mark packages as automatically installed or manually installed,
respectively\&. Packages are specified in exactly the same way as for the
225:command\&. For instance,
240: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
242:command\&. For instance,
282:This command accepts package names or patterns as arguments\&. If the
string contains a tilde character (\(lq\fB~\fR\(rq) or a question mark
(\(lq\fB?\fR\(rq), it will be treated as a search pattern and every package
matching the pattern will be considered (see the section
291: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\&.
295: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
298:\(lq\fBaptitude forbid\-version vim=1\&.2\&.3\&.broken\-4\fR\(rq\&.
302:will remove the ban\&. To remove the forbidden version without installing
the candidate version, the current version should be appended:
316:Upgrades installed packages to their most recent version\&. Installed
packages will not be removed unless they are unused (see the section
320:reference manual)\&. Packages which are not currently installed may be
installed to resolve dependencies unless the
327:will attempt to upgrade every package that can be upgraded\&. Otherwise,
329:will attempt to upgrade only the packages which it is instructed to
upgrade\&. The
341: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
348: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
350:and thus more likely to perform unwanted actions\&. However, it is capable
of upgrading packages that
357:will attempt to upgrade every package that can be upgraded\&. Otherwise,
359:will attempt to upgrade only the packages which it is instructed to
upgrade\&. The
396: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,
401:\(lqedit\(rq\&. For more information on search patterns, see the section
427:\(lq\fBedit\fR\(rq\&. As described in the
433:patterns match\&. Thus, the command
460: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
464:\fBv\fR, 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
467:\fBp\fR, meaning that the package and its configuration files will be
removed\&. If the third character is
474:reference guide\&. To customize the output of
483:Displays detailed information about one or more packages\&. If a package
name contains a tilde character (\(lq\fB~\fR\(rq) or a question mark
(\(lq\fB?\fR\(rq), it will be treated as a search pattern and all matching
packages will be displayed (see the section
489:If the verbosity level is 1 or greater (i\&.e\&., at least one
491:is present on the command\-line), information about all versions of the
package is displayed\&. Otherwise, information about the
506:\fB/sid\fR\&. If either of these is present, then only the version you
request will be displayed, regardless of the verbosity level\&.
508:If the verbosity level is 1 or greater, the package\*(Aqs 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\&.
536:p 1:1\&.4\&.5\-1
100
537:p 1:1\&.6\&.5\-1 unstable
500
538:p 1:1\&.7\&.14\-1 experimental
1
544: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
545:the documentation of \fBaptitude search\fR\&. 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\&.
553:reference manual)\&. This means that, for instance,
563:i 4\&.71\-3
100
564:p 4\&.71\-4 unstable
500
567:p 4\&.71\-4 unstable
500
575:will automatically group the output by package, as shown above\&. You can
disable this via
585:i exim4\-daemon\-light 4\&.71\-3
100
586:p exim4\-daemon\-light 4\&.71\-4 unstable
500
587:p exim4\-daemon\-light\-dbg 4\&.71\-4 unstable
500
601:i 4\&.71\-3
100
602:p 4\&.71\-4 unstable
500
603:p 4\&.71\-4 unstable
500
610:\fB\-F\fR\&. The order in which versions are displayed can be controlled by
the command\-line option
611:\fB\-\-sort\fR\&. To prevent
619:Adds a user tag to or removes a user tag from the selected group of
packages\&. If a package name contains a tilde (\(lq\fB~\fR\(rq) or question
mark (\(lq\fB?\fR\(rq), 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
625:User tags are arbitrary strings associated with a package\&. They can be
used with the
635: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:
643:i A nautilus Recommends desktop\-base (>= 0\&.2)
645:p kde Depends kdepim (>= 4:3\&.4\&.3)
653:finds a dependency chain that installs the package named on the command
line, as above\&. Note that the dependency that
655:produced in this case is only a suggestion\&. This is because no package
currently installed on this computer depends on or recommends the
683:will begin its search at these patterns\&. That is, the first package in
the chain it prints to explain why
685: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 (\(lq\fB~\fR\(rq) or a question mark (\(lq\fB?\fR\(rq), in
which case they are treated as search patterns (see the section
693: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\&.
707: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,
717: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\&.
723: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\&.
731:\fB\&.deb\fR
738: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\&.
747:is downloaded\&. You can select a particular version of a package by
appending
762:\fB\&.deb\fR
773:configuration directory (\fB/etc/apt\fR) 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
777:reference manual)\&. Any existing package database files in the output
directory will be overwritten\&.
788: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\*(Aqt apply to particular commands and will be
ignored by those commands\&.
833:command\&. The pattern is a search pattern as described in the section
850:When the safe resolver is being used (i\&.e\&.,
864:command to install new packages; when the safe resolver is being used
(i\&.e\&.,
870:\fBtrue\fR), allow the dependency resolver to install new packages\&. This
option takes effect regardless of the value of
876: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\*(Aqs security\&.
885:to output their results without any special formatting\&. In particular:
normally
888:\(lqcolumns\(rq\&. 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\&.
898:disksearch 1\&.2\&.1\-3
899:hp\-search\-mac 0\&.1\&.3
900:libbsearch\-ruby 1\&.5\-5
901:libbsearch\-ruby1\&.8 1\&.5\-5
902:libclass\-dbi\-abstractsearch\-perl 0\&.07\-2
903:libdbix\-fulltextsearch\-perl 0\&.73\-10
929:Download packages to the package cache as necessary, but do not install or
remove anything\&. By default, the package cache is stored in
942:commands\&. For instance, passing
976:resolver to solve them\&. Unlike the
979:\fB\-\-safe\-resolver\fR, 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\&.
990:command groups its output\&. The following values are recognized:
1002:\(lq\fBunstable\fR\(rq, etc)\&. If a package occurs in several archives,
it will be displayed in each of them\&.
1071:Display a brief help message\&. Identical to the
1083:\(lq\fB\-\fR\(rq, 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\&.
1087:has performed (/var/log/aptitude); the log messages written using this
configuration include internal program events, errors, and debugging
messages\&. See the command\-line option
1102:or higher\&. For instance, setting the log level to
1108:to be displayed; all others will be hidden\&. Valid log levels (in
descending order) are
1115:\fBtrace\fR\&. The default log level is
1127:\fB\-\-log\-level=aptitude\&.resolver:fatal\fR
1129:\fB\-\-log\-level=aptitude\&.resolver\&.hints\&.match:trace\fR, then
messages in
1130:\fBaptitude\&.resolver\&.hints\&.parse\fR
1133:\fBaptitude\&.resolver\&.hints\&.match\fR
1134: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\&.
1138:has performed (/var/log/aptitude); the log messages written using this
configuration include internal program events, errors, and debugging
messages\&. See the command\-line option
1148: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
1149:\fB\-\-log\-level=aptitude\&.resolver\&.search:trace
\-\-log\-level=aptitude\&.resolver\&.search\&.tiers:info\fR\&.
1156:from installing any new packages; when the safe resolver is being used
(i\&.e\&.,
1161:\fBtrue\fR), forbid the dependency resolver from installing new
packages\&. This option takes effect regardless of the value of
1170:When the safe resolver is being used (i\&.e\&.,
1193:commands should be displayed\&. For instance, passing
1215:/tmp/my\-log\&. For more information on configuration file options, see
the section
1238:will also purge them, removing their configuration files and perhaps other
important data\&. For more information about which packages are considered to be
1252:Suppress all incremental progress indicators, thus making the output
loggable\&. This may be supplied multiple times to make the program quieter,
but unlike
1264:/etc/apt/apt\&.conf); it causes the program to behave as if
1276:/etc/apt/apt\&.conf
1278:~/\&.aptitude/config)\&. Packages previously installed due to
recommendations will not be removed\&.
1289:/etc/apt/apt\&.conf
1291:~/\&.aptitude/config)\&.
1340:command\&. The pattern is a search pattern as described in the section
1357:In command\-line mode, print the actions that would normally be performed,
but don\*(Aqt actually perform them\&. This does not require
1359:privileges\&. In the visual interface, always open the cache in read\-only
mode regardless of whether you are
1370: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\*(Aqs default candidate version\&. It is
the same algorithm used in
1374:\fBaptitude safe\-upgrade\fR\&. Because
1388:For commands that modify package states, schedule operations to be
performed in the future, but don\*(Aqt perform them\&. You can execute
scheduled actions by running
1390:with no arguments\&. This is equivalent to making the corresponding
selections in
1404:command shows package names\&. The following settings are allowed:
1461:will display a summary of the actions performed by the resolver before
printing the installation preview\&. This is equivalent to the configuration
option
1469:to summarize each dependency chain that it outputs, rather than displaying
it in long form\&. If this option is present and
1502:\fBfirst\-package\fR: display the first package in each chain\&. This is
the default value of
1594: cupsys\-driver\-gutenprint D: cups\-driver\-gutenprint (>= 5\&.0\&.2\-4)
D: cups (>= 1\&.3\&.0) R: foomatic\-filters (>= 4\&.0) R: foomatic\-db\-engine
(>= 4\&.0) D: foomatic\-db (>= 20090301)
1595: foomatic\-filters\-ppds D: foomatic\-filters R: foomatic\-db\-engine (>=
4\&.0) D: foomatic\-db (>= 20090301)
1596: kde D: kdeadmin (>= 4:3\&.5\&.5) R: system\-config\-printer\-kde (>=
4:4\&.2\&.2\-1) D: system\-config\-printer (>= 1\&.0\&.0) R: hal\-cups\-utils
D: cups R: foomatic\-filters (>= 4\&.0) R: foomatic\-db\-engine (>= 4\&.0) D:
foomatic\-db (>= 20090301)
1597: wine D: libwine\-print (= 1\&.1\&.15\-1) D: cups\-bsd R: cups R:
foomatic\-filters (>= 4\&.0) R: foomatic\-db\-engine (>= 4\&.0) D: foomatic\-db
(>= 20090301)
1601: foomatic\-gui D: python\-foomatic (>= 0\&.7\&.9\&.2) D:
foomatic\-db\-engine D: foomatic\-db (>= 20090301)
1616:$ aptitude \-\-show\-summary=all\-packages why aptitude\-gtk
libglib2\&.0\-data
1617:Packages requiring libglib2\&.0\-data:
1618: aptitude\-gtk D: libglib2\&.0\-0 R: libglib2\&.0\-data
1627:Set the release from which packages should be installed\&. For instance,
1628:\(lq\fBaptitude \-t experimental \&.\&.\&.\fR\(rq
1649:\fBshow\fR) to display extra information\&. This may be supplied multiple
times to get more and more information\&.
1669:In the preview displayed before packages are installed or removed, show
which manually installed package requires each automatically installed
package\&. For instance:
1676:\&.\&.\&.
1689:\fBAptitude::CmdLine::Verbose\fR, this displays the entire chain of
dependencies that lead each package to be installed\&. For instance:
1695:$ aptitude \-v \-\-show\-why install libdb4\&.2\-dev
1697: libdb4\&.2{a} (libdb4\&.2\-dev D: libdb4\&.2) libdb4\&.2\-dev
1699: libdb4\&.4\-dev{a} (libdb4\&.2\-dev C: libdb\-dev P<\- libdb\-dev)
1705:This option will also describe why packages are being removed, as shown
above\&. In this example,
1706:libdb4\&.2\-dev
1727: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\&.
1736:\(lqyes\(rq\&. In particular, suppresses the prompt that appears when
installing, upgrading, or removing packages\&. Prompts for
1738:actions, such as removing essential packages, will still be displayed\&.
This option overrides
1758:Actions \(-> Clean obsolete files)\&. You cannot use this option and
1768:Actions \(-> Clean package cache)\&. You cannot use this option and
1778:\(lqg\(rq)\&. You cannot use this option and
1794:Begins updating the package lists as soon as the program starts\&. You
cannot use this option and
1805:$HOME/\&.aptitude
1809:$HOME/\&.aptitude/config\&. Otherwise, it will look up the current
user\*(Aqs home directory using
1820:is invoked\&. If not set, it defaults to
1832:if that variable is set\&. Otherwise, it will store them in
1839:will store its temporary files in the directory indicated by this
environment variable\&. If
1857:/etc/apt/apt\&.conf, /etc/apt/apt\&.conf\&.d/*, ~/\&.aptitude/config
1861:~/\&.aptitude/config
1863:/etc/apt/apt\&.conf\&. See
1871:/usr/share/doc/aptitude/html/<\fIlang\fR>/index\&.html
1889:Copyright 2014\-2016 Manuel A\&. Fernandez Montecelo
1893:This manual page is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more
details\&.
1895:You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc\&., 51
Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA\&.
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z ":
troff: backtrace: file '<stdin>':1603
troff:<stdin>:1603: warning: trailing space in the line
