Removing of a package consists of the following steps: 1. Of course, this only applies to files in system directories, not configuration files written to individual users' home directories. In that case, dpkg won't remove them by itself, but the package's postrm script (which is called by dpkg), has to take care of their removal during purge. Note: some configuration files might be unknown to dpkg because they are created and handled separately through the configuration scripts. If -a or -pending is given instead of a package name, then all packages unpacked, but marked to be removed or purged in file /var/lib/dpkg/status, are removed or purged, respectively. P or -purge removes everything, including conffiles. (Conffiles are configuration files that are listed in the DEBIAN/conffiles control file). This may avoid having to reconfigure the package if it is reinstalled later. r or -remove remove everything except conffiles. -r, -remove, -P, -purge package.| -a| -pending Remove an installed package.This can be fixed later by running: dpkg -configure -pending. Use of this option may leave packages in the improper triggers-awaited and triggers-pending states. If package names are supplied only those packages' triggers will be processed, exactly once each where necessary. -triggers-only package.| -a| -pending Processes only triggers.Run postinst script, if provided by the package.

Unpack the conffiles, and at the same time back up the old conffiles, so that they can be restored if something goes wrong. Configuring consists of the following steps: 1. To reconfigure a package which has already been configured, try the If -a or -pending is given instead of package, all unpacked but unconfigured packages are configured. -configure package.| -a| -pending Configure a package which has been unpacked but not yet configured.If -recursive or -R option is specified, package_file must refer to a directory instead. Unpack the package, but don't configure it. See -configure for detailed information about how this is done. Note that this script is executed after the preinst script of the new package, because new files are written at the same time old files are removed. If another version of the same package was installed before the new installation, execute the postrm script of the old package. Unpack the new files, and at the same time back up the old files, so that if something goes wrong, they can be restored. Run preinst script, if provided by the package. If another version of the same package was installed before the new installation, execute prerm script of the old package. Extract the control files of the new package. Installation consists of the following steps: 1.

Aptitude stdin unavailable