Package: xfonts-100dpi
Version: 1:1.0.0-2
When testing xfonts-100dpi (and a whole bunch of other xfonts-*
packages), I get the following error:
0m12.3s ERROR: Package purging left files on system:
/etc/X11
owned by: x11-common, xfonts-100dpi
/usr/share/fonts
owned by: xfonts-encodings, xfonts-utils, xfonts-100dpi
/usr/share/fonts/X11
owned by: xfonts-encodings, xfonts-utils, xfonts-100dpi
/usr/share/fonts/X11/100dpi
owned by: xfonts-100dpi
/usr/share/fonts/X11/100dpi/fonts.alias
The /etc/X11 problem may be due to a dpkg bug, so let's not worry about
it for now. The /usr/share/fonts/X11/100dpi/fonts.alias file gets
removed properly if the font package is removed and purged before the
xfonts-utils package is removed. This is not, however, guaranteed by
dependencies: since xfonts-100dpi depends on xfonts-utils, the latter
won't be removed before the former, but for purging, this is not true.
I am not very familiar with how fonts are packaged for X, so the
following may be total crock, but it strikes me that running
update-fonts-alias already during the removal phase (and not waiting for
the purge phase) might be the way to do this. After all, the font files
are removed during removal, so the fonts.alias files might as well be
updated then, too, mightn't they?
This problem affects at least the following other font packages:
xfonts-100dpi, xfonts-75dpi, xfonts-a12k12, xfonts-ayu, xfonts-base,
xfonts-kappa20, xfonts-marumoji, xfonts-mplus, xfonts-nexus,
xfonts-shinonome. I'm only reporting it against one, because it seems to
me that the code to handle these are shared, so fixing it once should be
enough. At worst, the fix needs to be copied to the other packages. If
it helps, I can clone the bug against the others (and any new ones I may
find).
--
If possible, use code, not comments.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
