Am Montag, den 21.03.2011, 13:29 +0100 schrieb Rene Engelhard:
> On Mon, Mar 21, 2011 at 01:12:18PM +0100, Paul Menzel wrote:
> > I removed the old `openoffice.org*` packages and installed the
> ^^^^^^^^
> aha.
>
> > `libreoffice.org` ones. The following message is shown on the terminal.
>
> You mean libreoffice.
>
> > update-openoffice-dicts: Trying to remove useless dir "/etc/openoffice".
> > update-openoffice-dicts: Could not remove possibly non-empty dir "/etc/openoffice".
>
> I think this is a bug in dictionaries-common. It shouldn't run update-openoffice-dicts, it isn't
> needed since OOo3(!). The trigger should go away. And IMHO it should only try to remove
> /etc/openoffice if it is empty, as there always were more config files then dictionary.lst there.
>
> > The content is as follows.
> >
> > $ ls -l /etc/openoffice/
> > insgesamt 16
> > -rw-r--r-- 1 root root 4322 18. Jun 2009 psprint.conf
> > -rw-r--r-- 1 root root 151 10. Jun 2010 sofficerc
> > -rw-r--r-- 1 root root 795 18. Jun 2009 soffice.sh
> >
> > These files remain if `openoffice.org-common` was just removed and not
> > purged.
> >
> > $ aptitude search openoffice.org-common
> > c openoffice.org-common
>
> And? That is the definition of "remove". Conffiles stay if you just "remove"
> If you want them gone, use "purge". How is a bug here? Correct, there isn't :)
>
> > Could the message be elaborated to `You can purge the package to remove
> > the superseded OpenOffice.org files.`.
>
> No. Everything you told here is correct behaviour.
>
> > Or is there a migration document where this is or should be covered?
>
> But yes, if you do a "upgrade" this is a bug, those files remain and don't get
> migrated. That doesn't make your steps correct, though. What you got is what is
> correct from your steps. But there shouldn't be a migration document needed at all.
Ok, so to summarize, if I upgraded the packages the files would have
been migrated. (It was actually by mistake, that I removed the packages
and did not upgrade.)
What kind of files are stored under these paths?
$ dpkg -L openoffice.org-common
/etc
/etc/bash_completion.d
/etc/bash_completion.d/ooffice.sh
/etc/openoffice
/etc/openoffice/sofficerc
/etc/openoffice/psprint.conf
/etc/openoffice/soffice.sh
/usr/lib/openoffice
/usr/lib/openoffice/program
/usr/lib/openoffice/share
/usr/lib/openoffice/share/config
I just found additionally the following files there
$ ls /usr/lib/openoffice/program/share/config/
javasettingsunopkginstall.xml
$ ls /usr/lib/openoffice/share/config/
javasettingsunopkginstall.xml
So I guess, I can safely purge `openoffice.org-common`.
Will you close this bug or should I do this?
Thank you for your response and explanation,
Paul
Attachment:
signature.asc
Description: This is a digitally signed message part