Package: dbconfig-common Version: 1.8.57 Severity: wishlist File: /var/lib/dpkg/info/dbconfig-common.templates
User is used to doing $BROWSER http://localhost/phpmyadmin/ and seeing all his databases. So upon # aptitude purge phpmyadmin user sees Template: dbconfig-common/dbconfig-remove Type: boolean Default: true Description: Deconfigure database for ${pkg} with dbconfig-common? Since you are removing ${pkg}, it's possible that you no longer want the underlying database and the privileges for the user associated with this package. . Please choose whether database removal and privilege revocation should be handled with dbconfig-common. . If you choose this option, dbconfig-common will check if ${pkg} provided scripts and database commands to undo package specific operations and run them if they exist. Then it will ask if you want to purge the database and revoke the standard privileges for the user of ${pkg}. If you don't want any of this, or if you want to handle this manually, you should refuse this option. and the even more scary: Template: dbconfig-common/purge Type: boolean Default: false Description: Purge the database for ${pkg}? If you no longer need the database for ${pkg} and the privileges of the database user of ${pkg}, you can choose to remove the database and revoke the privileges now. . If you no longer have need of the data being stored by ${pkg}, you should choose this option. If you want to keep this data, or if you would rather handle this process manually, you should refuse this option. Whereupon user has a 1/10 suspicion that this just might mean sweeping away all his MySQL databases in addition to just the phpmyadmin MySQL database... So maybe clarify via a listing right there, of what goes, and what stays, so he can scroll through it to get a better grasp of what is about to happen.
