Le samedi 31 octobre 2015 à 11:20 +0530, Vasudev Kamath a écrit : > Philippe Cochy <acquadoria@gmail.com> writes: > > > I apologize but I do not see the problem to generate this font with > > the classic fontforge. The new fontforge version brings many > > regressions. I would hate an irresponsible forcing to early put > > forward. > > Did you try to build the font with fontforge?. If you are just assuming > then please see below error. And also see upstream bug which I reported > where a person confirm he is able to build with fontforge compiled from > *source* (not one from Debian) > > Here is what I see when I try to build the font in clean chroot > environment. > > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building fonts-monoid using existing ./fonts-monoid_0.60.orig.tar.gz > dpkg-source: warning: ignoring deletion of file Monoisome/Monoisome-Regular.ttf, use --include-removal to override > dpkg-source: warning: ignoring deletion of file Utilities/WIP'n'test/MonoidTest-Retina.ttf, use --include-removal to override > dpkg-source: info: building fonts-monoid in fonts-monoid_0.60-1.debian.tar.xz > dpkg-source: info: building fonts-monoid in fonts-monoid_0.60-1.dsc > debian/rules build > test -x debian/rules > mkdir -p "." > > WARNING: copyright-check disabled - touch debian/copyright_hints to enable. > > touch debian/stamp-copyright-check > touch debian/stamp-upstream-cruft > /usr/bin/make -C . CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall" CPPFLAGS="-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" all > make[1]: Entering directory '/build/fonts-monoid-0.60' > Scripts/build.py 1 0 Monoisome/Monoisome.sfdir > Failed to find NameList: AGL For New Fonts > Makefile:6: recipe for target 'all' failed > make[1]: *** [all] Segmentation fault (core dumped) > make[1]: Leaving directory '/build/fonts-monoid-0.60' > /usr/share/cdbs/1/class/makefile.mk:47: recipe for target 'debian/stamp-makefile-build' failed > make: *** [debian/stamp-makefile-build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > E: Failed autobuilding of package > W: no hooks of type C found -- ignoring > I: unmounting dev/pts filesystem > I: unmounting run/shm filesystem > I: unmounting proc filesystem > -> Cleaning COW directory > forking: rm -rf /var/cache/pbuilder/build-sid/cow.30876 > > I see error and a segmentation fault. Current version of fontforge in > Debian is 20120731.b-5+b3 Sure! The sfdir (font.props) format was changed in the new fontforge. I do not think the solution is in a headlong rush but to save the font using the classic fontforge. Classic and new fontforge are for now incompatible. (It would be interesting to try with .sfd) What remained stable this is the ttf format that can be use with both ;-)
Attachment:
signature.asc
Description: This is a digitally signed message part