According to gentoo guidelines, 30 days have to pass for an ebuild to become stable. The ebuild for media-gfx/fontforge-20070501 has been in the trunk since may 2 2007 I've been using this app for some time with no problems at all. Thus, I'm requesting the stabilization.. Thanks! Reproducible: Always
I'd like to second this request. I will need this before a recent version of lilypond can be stabilized. Font herd, if you're okay with this please attach arches.
fontforge is spanky's baby. i'll defer to him.
ive only been bumping it in light of the fonts herd ignoring it and i needed it a while ago for wine ... 20070501 and newer should be safe for stabilization
archs, please stabilize media-gfx/fontforge-20060501. thanks.
you mean media-gfx/fontforge-20070501
Using fontimage: armin@main ~ $ fontimage Copyright (c) 2000-2007 by George Williams. Executable based on sources from 13:10 1-May-2007-ML. File "/usr/bin/fontimage", line 3 if ( Strtol($version)<20061025 ) ^ SyntaxError: invalid syntax Using sfddiff: armin@main ~ $ sfddiff Copyright (c) 2000-2007 by George Williams. Executable based on sources from 13:10 1-May-2007-ML. File "/usr/bin/sfddiff", line 3 if ( Strtol($version)<20060330 ) ^ SyntaxError: invalid syntax With actual stable sfddiff works, and fontimage doesn't exist.
+1 to armin's comment, app-text/mftrace is completely broken with this version.
thanks Marijn ;P what minimum version do you need stable for lilypond? 20070312 seems to be the last version where sfddiff and fontimage work. if that's recent enough we can stabilize that. otherwise i'll put this bug on hold until we find a fix for a newer version.
the error is because fontforge is trying to execute those scripts with python instead of the built in scripting language which seems to be the default behavior now i'll ask upstream about it
(In reply to comment #8) > thanks Marijn ;P > > what minimum version do you need stable for lilypond? I specifically need 20070501 or newer. (In reply to comment #7) > +1 to armin's comment, app-text/mftrace is completely broken with this version. stabilizing mftrace-1.2.9 will prolly solve that.
(In reply to comment #9) > the error is because fontforge is trying to execute those scripts with python > instead of the built in scripting language which seems to be the default > behavior now > > i'll ask upstream about it Mike asked, Mike got an answer, so all arches should stay, as a fix will be provided shortly: http://sourceforge.net/mailarchive/forum.php?thread_name=200706281752.19188.vapier%40gentoo.org&forum_name=fontforge-devel
please readd arches when it's ready for prime time. ;-)
Any update on this Christian? This is keeping some very obsolete (and broken) lilyponds in the stable tree.
this has been fixed in all released versions since ... so pick any fontforge version after 20070723 and stabilize it i'd say
Okay, reCCing arch teams. Please stablilize media-gfx/fontforge-20070808.
Euhm, make that media-gfx/fontforge-20070831, it's near enough to the 30 days IMHO.
Stable for HPPA.
alpha/ia64/sparc/x86 stable
amd64 stable
stable on ppc
stable on ppc64
