Hi Calum, thank you for reporting your state of the things so quickly!
Am Sat, 23 Jun 2018 23:45:40 +0100 schrieb Calum Mackay <calum.mac...@cdmnet.org>: > > This is probably > > https://bugs.debian.org/853848https://bugs.debian.org/853848, fixed by > > upgrading/removing: > > fonts-beng-extra > > fonts-deva-extra > > fonts-gujr-extra > > fonts-guru-extra > > fonts-orya-extra, fixed by upgrading/removing: Debian bug 853848 was > > fixed a year ago, so upgrading won't help this issue. > > I purged those pkgs, and the problem remained. The pkg removal resulted in > various leftovers (with errors), despite --purge: > > /etc/fonts/conf.avail/65-0-fonts-guru-extra.conf > [..] I took a deeper look at the bug report #853848. It describes that the error happens during package installation (wrong path being used in a postinst script). Thus the package maintainer took the shortcut of fixing the cause ("do not create the unwanted directory anymore"), but he did not revert the caused damage ("remove the unwanted directory if it is there"): https://salsa.debian.org/fonts-team/fonts-deva-extra/commit/77b9d92033842893f160d50fb7d67a6edee70911 This is not really great, since it leaves the burden of cleaning up on the local administrator. But we are on testing - /things/ may happen :( The following workaround should clean up the situation for most installations: find /etc/fonts/conf.avail/ -type d -empty -delete I have the feeling, that this bug (for the munin package) can remain closed. And we just hope that all affected users (of these fonts or munin itself) find this information here helpful for cleaning the situation up manually. Or how would you think, we should proceed? Cheers, Lars
