Closed cionx closed 2 years ago
I can confirm, there does seem to be some new problem and it does seem to be ufoLib2 related. There was a release a little while back so it may be in there. On the other hand I checked some UFO based projects such as Raleway that build with fontship
but from UFO sources, so I'm guessing this might actually be specific to handling SFD sources. I'll look into it, but maybe not for a few days.
In case it is useful to you to build the font now as opposed to whenever I figure this out, I can confirm that the Docker images released at the time Fontship was last released still work to build this font. It is only local installs that have newer libraries that what was current when I released v0.8.2 that are causing trouble.
$ alias fontship-docker='docker run -it --volume "$(pwd):/data" --user "$(id -u):$(id -g)" theleagueof/fontship:latest'
$ fontship-docker make
Also the CI still works so if you submit a PR it will build remotely and you can download artifacts.
Thanks both for the report and for tracking down the cause @cionx. I hope you don't mind I marked you as the co-author of the fixing commit (51dc0ba) because after some review it seemed to me like that was the right solution. This should build easily again (tested with fontship
most recent stable v0.8.2 and the current Git HEAD v0.8.2.r16.g33e4ab0).
Describe the bug The current build script
tools/build.py
seems to be broken.Steps to reproduce Following the build instructions in the
README.md
, clone the repository and then runfontship make
.Expected vs. actual behavior I expect the fonts to build. But instead, the build process immediately crashes.
Screenshots / logs
Additional context The problem seems to lie in the following line: https://github.com/alerque/libertinus/blob/7625ca761348c857075b89115697053f3f70e3a6/tools/build.py#L14 I checked the ufoLib2 documentation and the parameter
validate
does not seem to exist anymore. From what I can tell, it was removed in https://github.com/fonttools/ufoLib2/commit/ecf9390f26ebf9c5984a2e9e3e5a739450885e91.It seems to me that simply removing the parameter
validate=False
seems to be enough to make the build process work again. (I tested this on my local machine.) But I don’t understand the build process well enough to guarantee that this doesn’t break anything in the resulting font files.