Aptitude full-upgrade Debian
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
Command-line actions
The first argument which does not begin with a hyphen (“-”) 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:
aptitude install
Install one or more packages. The packages should be listed after the “install” command; if a package name contains a tilde character (“~”) or a question mark (“?”), it will be treated as a search pattern and every package matching the pattern will be installed (see the section “Search Patterns” in the aptitude reference manual).
To select a particular version of the package, append “=version” to the package name: for instance, “aptitude install apt=0.3.1”. Similarly, to select a package from a particular archive, append “/archive” to the package name: for instance, “aptitude install apt/experimental”. You cannot specify both an archive and a version for a package.
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, aptitude remove wesnoth+ will install wesnoth, not remove it. The following override specifiers are available:
package+
aptitude Install package.
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 section about automatic installations in the documentation for more information.
package+M
Install package and immediately mark it as automatically installed (note that if nothing depends on package, this will cause it to be immediately removed).
package-
aptitude Remove package.
package_
Purge package: remove it and all its associated configuration and data files.
package=
Place package on hold: cancel any active installation, upgrade, or removal, and prevent this package from being automatically upgraded in the future.
package:
Keep package at its current version: cancel any installation, removal, or upgrade. Unlike “hold” (above) this does not prevent automatic upgrades in the future.
package&M
Mark package as having been automatically installed.
package&m
Mark package as having been manually installed.
package&BD
Install the build-dependencies of a package.
As a special case, “install” with no arguments will act on any stored/pending actions.
[Note] Note
Once you enter Y at the final confirmation prompt, the “install” command will modify aptitude's stored information about what actions to perform. Therefore, if you issue (e.g.) the command “aptitude install foo bar” on packages previously uninstalled, and then the installation fails once aptitude has started downloading and installing packages, you will need to run “aptitude remove foo bar” to go back to the previous state (and possibly undo installations or upgrades to other packages that were affected by the “install” action).
aptitude remove, purge, reinstall
These commands are the same as “install”, but apply the named action to all packages given on the command line for which it is not overridden.
For instance, “aptitude remove '~ndeity'” will remove all packages whose name contains “deity”.
build-depends, build-dep
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 “install” command, and the build-dependencies of the source packages that build those binary packages are satisfied.
If the command-line parameter --arch-only is present, only architecture-dependent build dependencies (i.e., not Build-Depends-Indep or Build-Conflicts-Indep) will be obeyed.
aptitude markauto, unmarkauto
Mark packages as automatically installed or manually installed, respectively. Packages are specified in exactly the same way as for the “install” command. For instance, “aptitude markauto '~slibs'” will mark all packages in the “libs” section as having been automatically installed.
For more information on automatically installed packages, see the section “Managing Automatically Installed Packages” in the aptitude reference manual.
hold, unhold, keep
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 “install” command. For instance, “aptitude hold '~e^dpkg$'” will mark all packages coming from the source package “dpkg” to be on hold.
The difference between hold and keep is that hold will cause a package to be ignored by future safe-upgrade or full-upgrade commands, while keep merely cancels any scheduled actions on the package. unhold will allow a package to be upgraded by future safe-upgrade or full-upgrade commands, without otherwise altering its state.
keep-all
Cancels all scheduled actions on all packages; any packages whose sticky state indicates an installation, removal, or upgrade will have this sticky state cleared.
aptitude forget-new
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 (“~”) or a question mark (“?”), it will be treated as a search pattern and every package matching the pattern will be considered (see the section “Search Patterns” in the aptitude reference manual).
forbid-version
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 “=version” to the package name: for instance, “aptitude forbid-version vim=1.2.3.broken-4”.
To revert the action, “aptitude install package” will remove the ban. To remove the forbidden version without installing the candidate version, the current version should be appended: “install package=version”.
aptitude update
Updates the list of available packages from the apt sources (this is equivalent to “apt-get update”)
aptitude safe-upgrade
Upgrades installed packages to their most recent version. Installed packages will not be removed unless they are unused (see the section “Managing Automatically Installed Packages” in the aptitude reference manual). Packages which are not currently installed may be installed to resolve dependencies unless the --no-new-installs command-line option is supplied.
If no packages 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 packages can be extended with suffixes in the same manner as arguments to aptitude install, so you can also give additional instructions to aptitude here; for instance, aptitude safe-upgrade bash dash- will attempt to upgrade the bash package and remove the dash 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 full-upgrade command to upgrade as many packages as possible.
aptitude full-upgrade
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 safe-upgrade and thus more likely to perform unwanted actions. However, it is capable of upgrading packages that safe-upgrade cannot upgrade.
If no packages 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 packages can be extended with suffixes in the same manner as arguments to aptitude install, so you can also give additional instructions to aptitude here; for instance, aptitude full-upgrade bash dash- will attempt to upgrade the bash package and remove the dash package.
[Note] Note
This command was originally named dist-upgrade for historical reasons, and aptitude still recognizes dist-upgrade as a synonym for full-upgrade.
No comments