Am Dienstag, den 07.04.2020, 10:12 +0200 schrieb Thomas Morley: > Am Di., 7. Apr. 2020 um 09:50 Uhr schrieb David Kastrup < > d...@gnu.org > >: > > Thomas Morley < > > thomasmorle...@gmail.com > > > writes: > > > > > Am Mo., 6. Apr. 2020 um 17:18 Uhr schrieb Thomas Morley > > > < > > > thomasmorle...@gmail.com > > > >: > > > > > > > I'll test GUB with current master on my Ubuntu 18.04, though results > > > > likely tomorrow... > > > > > > FWIW, on my 64-bit Ubunu 18.04, I tried to gub-build release/unstable > > > > > > (1) gubllb /home/hermann/gub/ /home/hermann/lilypond-git/ release/unstable > > > i.e. using Knut's script to build from my local repository > > > > > > Failed with: FileNotFoundError: [Errno 2] No such file or directory: > > > 'book_base.py' > > > > The question is whether we wait for a followup issue to fix the problem, > > or just revert the problematic commit for now. I lean towards the > > latter, to be honest. > > > > -- > > David Kastrup > > Well, I'd test it locally. > > Though, the naive > git revert fa1ec0c100859f7490f524870743f03b54f89ab7
The "offending" commit is ab7a344f689dd9c523f12e818a6f638e1cb7fd4c, not sure where above commit id comes from. Jonas
signature.asc
Description: This is a digitally signed message part
