Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I am trying to do a clean install of the octave3.2 package.

To do this, I removed it, then tried to reinstall it.

When I reinstalled, an error occurred. It could be a bug in the package, but I want to make sure I have everything removed so that I can do a clean install.

Is it enough to do this?

sudo apt-get --purge remove octave3.2
share|improve this question
    
Could one reinstall the package and pay attention to the package OR dependencies list.. ? –  user309924 Jul 28 '14 at 11:36
    
Recommended to visit this –  Pandya Oct 3 '14 at 16:03

3 Answers 3

This is a generic answer to the question about the effects of purging packages generally. For advice specific to your situation, you'll have to edit your question to include additional information--in particular, the complete and exact text of the error message you are getting.

Removing packages with sudo apt-get purge ... or sudo apt-get --purge remove ... will remove them and all their global (i.e., systemwide) configuration files. This is usually what people mean when they talk about completely removing a package.

But that doesn't mean your system is the same as it was before the package was installed. In particular:

  • This does not remove packages that were installed as dependencies, when you installed the package you're now removing. Assuming those packages aren't dependencies of any other packages, and that you haven't marked them as manually installed, you can remove the dependencies with sudo apt-get autoremove or (if you want to delete their systemwide configuration files too) sudo apt-get --purge autoremove.

  • This does not remove non-systemwide configuration files. Specifically, it does not remove user-specific configuration:

    • It does not remove the configuration files and directories located in users' home directories (or in the .config subdirectory of their home directories), created by the software the package provides.

      • If these files/folders are not stored in .config, they usually start with a . themselves. Either way, you can see them with ls by using the -a or -A flag, and you can see them in Nautilus and most other file browsers/managers by pressing Ctrl+H or going to View > Show Hidden Files.
    • It does not reverse changes made to existing user-specific configuration files.

    • It does not remove new gconf or dconf keys, or reverse any gconf or dconf configuration changes.

  • Using purge or --purge remove instead of remove does not reverse changes to existing systemwide configuration files provided by other packages or created manually by the user. However, sometimes such changes are undone by uninstalling the package (whether or not it's a purge rather than a remove).

share|improve this answer

Better keep track of extra dependency packages installed while you are installing one.

The following extra packages will be installed: libgssglue1 libnfsidmap2 libtirpc1 nfs-common rpcbind

If you remove original package only, the dependency package may remain.

So you have to manually remove each one using

apt-get purge

.

share|improve this answer

Instead of removing auto-installed dependent packages manually, use the following instead:

 zanfilip@zanfilip-VPCEB3L0E:~/jp/eclipse$ sudo apt-get --purge autoremove
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    The following packages will be REMOVED
      libupstart1* linux-headers-3.16.0-30* linux-headers-3.16.0-30-generic*
      linux-image-3.16.0-30-generic* linux-image-extra-3.16.0-30-generic*
    0 to upgrade, 0 to newly install, 5 to remove and 23 not to upgrade.
    After this operation, 279 MB disk space will be freed.
    Do you want to continue? [Y/n] 

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.