xfonts-nexus post install calls /usr/X11R6/bin/mkfontdir

[Jason Ribeiro]

Here is the result of 'sudo aptitude install xfonts-nexus' on Dapper:

Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following NEW packages will be installed:
  xfonts-nexus
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 7760B of archives. After unpacking 94.2kB will be used.
Writing extended state information... Done
Get:1 http://us.archive.ubuntu.com dapper/universe xfonts-nexus 0.0.2-9ubuntu1 [7760B]
Fetched 7760B in 2s (2749B/s)
Selecting previously deselected package xfonts-nexus.
(Reading database ... 242021 files and directories currently installed.)
Unpacking xfonts-nexus (from .../xfonts-nexus_0.0.2-9ubuntu1_all.deb) ...
Setting up xfonts-nexus (0.0.2-9ubuntu1) ...
/var/lib/dpkg/info/xfonts-nexus.postinst: line 6: /usr/X11R6/bin/mkfontdir: No such file or directory

'mkfontdir' seems to have been moved to '/usr/bin/mkfontdir'

[Steve Kowalik (stevenk)]

This bug is corrected in the latest release of the xfonts-nexus package, which is version 0.0.2-12ubuntu1 uploaded to Edgy. This bug isn't fatal, so I'd suggest that 'sudo mkfontdir' be run as a workaround before Edgy is released.