Change:
[ "OpenMoji-Color.ttf" "OpenMoji-Black.ttf" ] variant; <ins> # With newer fontforge the build hangs, see # https://github.com/NixOS/nixpkgs/issues/167869 # Patches etc taken from # https://github.com/NixOS/nixpkgs/commit/69da642a5a9bb433138ba1b13c8d56fb5bb6ec05 fontforge-20201107 = fontforge.overrideAttrs (old: rec { version = "20201107"; src = fetchFromGitHub { owner = "fontforge"; repo = "fontforge"; rev = version; sha256 = "sha256-Rl/5lbXaPgIndANaD0IakaDus6T53FjiBb45FIuGrvc="; }; patches = [ (fetchpatch { url = "https://salsa.debian.org/fonts-team/fontforge/raw/76bffe6ccf8ab20a0c81476a80a87ad245e2fd1c/debian/patches/0001-add-extra-cmake-install-rules.patch"; sha256 = "u3D9od2xLECNEHhZ+8dkuv9818tPkdP6y/Tvd9CADJg="; }) (fetchpatch { url = "https://github.com/fontforge/fontforge/commit/69e263b2aff29ad22f97f13935cfa97a1eabf207.patch"; sha256 = "06yyf90605aq6ppfiz83mqkdmnaq5418axp9jgsjyjq78b00xb29"; }) ]; buildInputs = old.buildInputs ++ [ libuninameslist ]; }); scfbuild-with-fontforge-20201107 = scfbuild.override (old: { fontforge = fontforge-20201107; }); </ins> in stdenv.mkDerivation rec { pname = "openmoji"; version = "13.1.0";

Discussion:
openmoji-color and openmoji-black now both take 12h to build. They are timing out on hydra Steps to reproduce the behavior: -build -A openmoji-color
Could this be the same as ? Should we switch to prebuilt fonts here too?
It could be. But in the past the build only took a minute or 2. Now it takes basically forever. I'm trying to bisect when this was introduced but bisecting timeouts is slow and error-prone.
According to is the first bad commit. That isn't particularly helpful.
I did a better bisection and got () which is much more helpful. I saw that PR but thought it seemed too old. I guess I forgot how long a staging cycle can take. cc I don't know what the best approach here is. Report the bug upstream to fontforge or openmoji? There are a lot of warnings and errors in the build so I suspect that it may be an openmoji problem and fontforge was doing its best before and working but now is failing? The command I used for reference was:
after a brief look at this fontforge has a reported regression in its ability to remove overlaps () but if openmoji is the only font that is failing because of that, maybe they're relying too much on fontforge's abliity to fix things at build time (with the latest master commits from openmoji and fontforge, the openmoji build also hangs)
I tried diffing the logs but they are basically completely different once starts. In case they are helpful to anyone here are the builds before and after that commit. (The after obviously cuts off after the "infinite loop").
Great investigation! Maybe as a short-term fix we could override fontforge for this package?
That sounds like a reasonable mitigation until a patch is available.
Bump, would really love to have openmoji available when I upgrade 21.11 -22.05!
why the thumbs down?
Bumping issues is not a helpful thing to do.
In general yes, though in this case it reminded me to fix this before 22.05 :) Here you go
I tried running bisection on fontforge itself using after applying the patch below: Unfortunately, the automatic bisection did not work for some reason. Possibly because the does not match the error message:
needs to be reported upstream
Which one though? Openmoji or fontforge?