(debian-policy.info)Details of removal and/or configuration purging


Prev: Details of configuration Up: Package maintainer scripts and installation procedure
Enter node , (file) or (file)node

6.8 Details of removal and/or configuration purging
===================================================

  1.      `prerm' remove

     If prerm fails during replacement due to conflict

          `conflictor's-postinst' abort-remove \
              in-favour `package' `new-version'

     Or else we call:

          `postinst' abort-remove

     If this fails, the package is in a “Half-Configured” state, or else
     it remains “Installed”.

  2. The package’s files are removed (except ‘conffile’s).

  3.      `postrm' remove

     If it fails, there’s no error unwind, and the package is in an
     “Half-Installed” state.

  4. All the maintainer scripts except the ‘postrm’ are removed.

     If we aren’t purging the package we stop here.  Note that packages
     which have no ‘postrm’ and no ‘conffile’s are automatically purged
     when removed, as there is no difference except for the ‘dpkg’
     status.

  5. The ‘conffile’s and any backup files (‘~’-files, ‘#*#’ files,
     ‘%’-files, ‘.dpkg-{old,new,tmp}’, etc.)  are removed.

  6.      `postrm' purge

     If this fails, the package remains in a “Config-Files” state.

  7. The package’s file list is removed.


automatically generated by info2www version 1.2.2.9