Yes, in the thread http://permalink.gmane.org/gmane.linux.debian.devel.general/130808 talks about the problem. OK, thanks.
>>>>> Paul Hardy <[EMAIL PROTECTED]> writes: > Thank you both for your diagnostic information on this bug record. > Thank you also for your interest in this package, which I'm now > maintaining after it was orphaned for a couple of years. I believe > that the latest version fixes the problem. However, I wanted to give > you a more detailed explanation. > First, "xfonts-unifont" was meant to overwrite unifont.pcf.gz with a > more updated version, so it is okay that it's doing that. It should > just do it without complaining about anything being amiss. I didn't > put lines in the Debian package saying that "xfonts-unifont" Conflicts > with and Replaces the old "unifont" package. > Originally there was just a package called "unifont" that contained a > BDF and later a PCF font. I am now able to generate a TrueType font, > thanks to software that Luis Gonzalez Miranda wrote. After asking on > debian lists, it sounded like the best approach was to split the > "unifont" package into two new packages: "xfonts-unifont" for a PCF > font, and "ttf-unifont" for a TrueType font. That's what I did, with > the "unifont" package now installing both "xfonts-unifont" and > "ttf-unifont". > I didn't think of the case of someone installing "xfonts-unifont" when > "unifont" was already installed. I should have. My excuse is that > this was my first Debian package. :-) > A new version was just uploaded yesterday that should fix this > problem. There are also some glyph improvements, and more > documentation if you're interested in the "unifont-bin" package to see > how it is all put together. > See http://ftp.debian.org/debian/pool/main/u/unifont/ for the 20080808 > version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
