Hi Christian, On Thu, Mar 27, 2008 at 07:46:04PM +0100, Christian Perrier wrote: > Quoting Davide Viti (zinosat@tiscali.it): > > > It'd be great if someone could tell me when this change happended > > (it is not obvious from the FF changelog [2]) and which version (at least) > > of FF should be used to avoid the problem. > > > Whatever version it is, we could have a problem, here, as Kestutis > wants to step back on FF maintenance. > > Kartik Mistry mentioned some interest in packaging FF, so it might be > a good start *now* to decide about packaging a new version..:-) Yesterday I tried to see what it'd take to prepare a new package and followed these steps: - Download sources for previous package (apt-get source fontforge) - Download source for new package (http://sourceforge.net/project/showfiles.php?group_id=103338) version "20080302" as of yesterday (today a new version has been released) - Download fontfoge package sources (svn://svn.debian.org/pkg-fonts/packages/fontforge) and updated changlog file and rules files as to reflect new version To get things working I had to unpack/repack the source package, since it's been named "fontforge_full-20080309.tar.bz2" rather than "fontforge_full-20080302.tar.bz2". Patches apply cleanly and compilation goes fine. Shall we try to update the package? regards, Davide
Attachment:
signature.asc
Description: Digital signature