Apache OpenOffice (AOO) Bugzilla – Issue 99539
"apt-get purge" does not remove config files completely because of openoffice.org-ure
Last modified: 2013-08-07 15:26:05 UTC
Hello all, I hope I have chosen the right (Sub)componenent to report my problem. If not, feel free to change it ... ;) I am not sure, when I noticed this problem at first, but - as I am now TCM testing with localisation35 - the problem exists since month ... :( The problem: If I want to completely deinstall OOo via "apt-get purge ooobas* openof*" under Debian SID, I always get the message: <quote> Entferne openoffice.org-ure ... dpkg - Warnung: Während Entfernens von openoffice.org-ure ist Verzeichnis »/opt« nicht leer, wird daher nicht gelöscht. </quote> Roughly translated: <quote> Purging openoffice.org-ure ... dpkg - Warning: Cannot remove /opt, because it is not empty. Leaving it untouched" </qoute> This also happens if I install it and directly purge it without starting OOo before. And instead of not only removing /opt, apt-get does as well not remove the included /opt/openoffice.org3 directory. So there seem to be an error in the postrm mechanism/script. Please have a look and fix it. If I could be of any help (mostly: more information and the like ... ;) ), please give me a shout TIA Thomas.
CCed: rene
well, it seems that the packages declare /opt as belonging to them so dpkg -r tries to remove it. Which fails since there's other stuff in /opt still there.
(btw. apt-get purge does not exist, what does exist is dpkg -P, aptitude purge and apt-get --ppurge remove) That there still is a oprnoffice.org3 dir there is a sure sign you didn't remove your OOo stuff completely, and that something misses a dep on the -ure package: because when ure should be removed, everything should be removed, no? Removing me from Cc again.
There are files installed by unopkg that are not removed at uninstall time. Hard to fix.
Hello @ll, thank you for your quick reaction :) @rene: I am using SID here (with apt-0.7.20.2) where it is possible to use "apt-get purge..." directly ... ;) @of: Does it mean, that - during the installation - OOo uses unopkg to install something? Why? Would it not be possible to stop it doing it? If not: Which files does unopkg install in /o/oo.o3?
All the spellchecking stuff are installed with unopkg. It's a no-go to stop this :-).
Right, this is a problem of the 'bundled extensions'. Therefore I'll set this to duplicate. *** This issue has been marked as a duplicate of 77196 ***
Hello of, I am not that sure, if this issue is a duplicate of #77196. In the latter one the reporter is asking to handle extensions via a setup option to (re)install it, if I understand that issue right ... ;) In my case I reported something like an missing interaction with the package manager in Debian. I have not tried to install OOo without the oo.o-ure package (would that be possible?), but I have also seen in the past, that (if I use synaptic to purge OOo) the OOo-ure package is never selected as a - from what ever package it should be dependant - dependency to the rest of OOo. So the rest of OOo always will be purged, but will as well give the error message like "Warning: Cannot remove..." ... :( So I think, my issue should not be marked as an duplicate, but handled differently, because in Debian(based) systems there should be some kind of solution (maybe just start the installation of the ure extensions, if an user starts the first time, and install $extension in /home/$user), or am I wrong? Have fun Thomas.
duplicate -> closed