Package: caudium Version: 2:1.4.7-5 Hello,
purging caudium leads to some warnings:
dpkg - warning: while removing caudium, directory `/var/log/caudium' not empty
so not removed.
dpkg - warning: while removing caudium-modules, directory `/usr/lib/caudium'
not empty so not removed.
While not removing /var/log/caudium is probably okay somehow,
/usr/lib/caudium could not be removed because of a caudium-images
symlink created there by postinst, which should be removed, too.
While tracking this down I found that postinst does also create
directories in /usr/local/share, which IMHO you could at least try to
remove...
rmdir /usr/local/share/caudium/modules || true
rmdir /usr/local/share/caudium || true
...should in question point the user to the right locations to look at.
And btw... regarding the question in the postrm script: IMHO you should
at least tell the user that you left a backup of the config-files in
/var/backups although he decided to purge the package (and thus also
decided to remove it's config-files) :)
And regarding the caudium-images symlink in /usr/lib/caudium: in your
prerm script you do:
if [ -d /usr/lib/caudium/caudium-images/auto ]; then
rm -r /usr/lib/caudium/caudium-images/auto
fi
This will remove the package-shipped /usr/share/caudium/caudium-images/auto
when prerm is called. This should usually be okay, however I had at least
one case (after initial install of caudium) where these files were lost.
I just cannot reproduce it until now. So probably extending the
condition to some -a -d /usr/lib/caudium/caudium-images could be a good
idea.
regards
Mario
--
<Sique> Huch? 802.1q? Was sucht das denn hier? Wie kommt das ans TAGgeslicht?
signature.asc
Description: Digital signature
