Bug 650212 – media-gfx/fontforge - missing Python 3.6 support

• Status: RESOLVED DUPLICATE of bug 646278
• Product: Gentoo Linux

[Description Coacher 2018-03-11 14:11:23 UTC]

${SUMMARY}

[Comment 1 Mike Gilbert 2018-03-11 14:38:49 UTC]

Yes, because it doesn't work.

[Comment 2 Coacher 2018-03-11 23:24:11 UTC]

(In reply to Mike Gilbert from comment #1)
> Yes, because it doesn't work.
I see. Is there an upstream issue we can track or smth?

[Comment 3 Shane Peelar 2018-05-03 14:18:00 UTC]

Created attachment 529586 [details]
Fontforge Python 3.6 ebuild

I tried it here with a modified ebuild and it appears to be working fine with Python 3.6.5. This has allowed me to eliminate Python 3.5 from my system.

[Comment 4 Mike Gilbert 2018-05-03 16:09:52 UTC]

(In reply to Shane Peelar from comment #3)

Did you run the test suite (FEATURES=test)?

[Comment 5 rnddim 2018-05-25 14:25:17 UTC]

After seeing the news item about switching to Python 3.6 soon, I tried switching ahead of time and encountered this issue. I tried to use the modified ebuild attached with FEATURES=test specified on the commandline, and I'll attach the resulting build log.

Only one test fails, and it's "40: FontForge .sfd file open check", which happens to be a python scripting test. Using the same attached ebuild, but with my settings reverted to using 3.5 instead of 3.6, this same test passes, and in fact the ebuild is allowed to complete. So obviously something about fontforge needs to be changed to accommodate 3.6 beyond modifying the ebuild.

[Comment 6 rnddim 2018-05-25 14:26:18 UTC]

Created attachment 533098 [details]
Build log of modified ebuild, with tests

[Comment 7 Mike Gilbert 2018-05-28 18:45:15 UTC]

*** This bug has been marked as a duplicate of bug 646278 ***