Am Mittwoch, den 01.07.2020, 10:43 +0200 schrieb Jean Abou Samra: > Owen, > > Le 01/07/2020 à 00:36, Owen Lamb a écrit : > > On Tue, Jun 30, 2020 at 3:04 PM Jean Abou Samra <j...@abou-samra.fr> wrote: > > > So git clean didn't work? At this point, unfortunately I can't help > > > much--my > > > previous message was merely a shot in the dark but I understand almost > > > nothing > > > about fonts. Also, I'll be going on vacation pretty soon, so I won't have > > > time > > > to set up LilyDev, sorry… > > > > > > > No worries. Have a great vacation! > Thanks! > > > That said, if CI itself started to fail recently, there must be something > > > broken > > > in the sources, possibly in relation with a specific environement. Could > > > you try > > > to compile after a git checkout release/2.18.0-1? If that succeeds, you > > > want to > > > go through a git bisect to find the culprit. > > > > > > > > > > That's a good idea--I'll try that next. > > > PS: I guess https://gitlab.com/lilypond/lilypond/-/merge_requests/205 is > > > going > > > to help in debugging. > > > > > > > > > > This page is all Greek to me at the moment, but I'll look into it. Thanks! > > Quick explanation: among other things, this merge request introduces a --ci > flag in autogen.sh, > which helps testing just as CI does, with the same compiler settings. > > Compiling this branch with --ci yields fine results for me. So, the issue is > very likely related to your environment. CI runs in a docker container that > is either Ubuntu 16 or 18. These ship with older versions of FontForge than > my Ubuntu 20, as you'll notice in > https://packages.ubuntu.com/search?keywords=fontforge&searchon=names&suite=bionic§ion=all > (the version there being 20170731 while mine is 20190801). > > Paging Jonas: could we perhaps add a Docker file for Ubuntu 20.04? > > I hope your problem can be solved by installing a newer FontForge, which can > be done > from Ubuntu's newest apt repositories.
This makes absolutely no sense to me: CI runs with Ubuntu 16.04 and has no problems on master with a version of FontForge from 2012 (?). So I very much doubt this is the issue. > To do that, I guess (guess!) you should add the > following line to /etc/apt/sources.list: > deb http://cz.archive.ubuntu.com/ubuntu focal main universe > > (view the full list of mirrors at > https://packages.ubuntu.com/focal/amd64/fontforge/download). > > Then, > > sudo apt update > sudo apt-get -t focal install fontforge > > could do the trick, though I'm really unsure with apt usage. You must not do this. Mixing repositories from different versions is bound to produce problems. Jonas
signature.asc
Description: This is a digitally signed message part