Your message dated Sun, 08 Mar 2026 07:53:45 +0000
with message-id <[email protected]>
and subject line fixed
has caused the Debian Bug report #920708,
regarding fonts-b612 segfault and other problems with ufo2otf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
920708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920708
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-fontforge
Version: 1:20170731~dfsg-1
Severity: normal
Forwarding this to fontforge/python-fontforge:
Hello,
I can indeed reproduce the crash.
It looks a bug in libfontforge2. (ufo2otf simply calls python-fontforge
which in turn uses libfontforge2.)
I think you should report it to the fontforge package maintainers.
Regards,
Le 28/01/2019 à 08:02, Alex Myczko a écrit :
Hi Pierre
I'm trying to package b612, however ufo2otf errors, to reproduce:
(from #debian-fonts)
08:00 < tarzeau> ufo2otf specialists here? i've got double frees and fea
errors and segfaults
08:01 < tarzeau>
http://phd-sid.ethz.ch/debian/fonts-b612/fonts-b612_1.003%2Bgit20180121-1.dsc
(take this, uncomment debian/rules lines, run debuild)
any help welcome
Thanks,
[email protected]
--- End Message ---
--- Begin Message ---
fixed
--- End Message ---
