Am Mittwoch, den 15.07.2020, 16:26 +0100 schrieb Phil Holmes: > Here's the lilypond-doc.log zipped.
Do you happen to still have out/lybook-db/snippet-names- bcc309d5e1e5a6301f36814c1d4d872c.log around? In any case, it's odd that you're seeing issues with the very same base commit as 2.21.3 > I was doing a new release to get the documentation on the website looking > correct again. As I said: This won't be the case with the current release/unstable because it doesn't have my fix merged. In my opinion, we need to merge https://gitlab.com/lilypond/lilypond/-/merge_requests/246 to master and then do another release from there. > We've had problems in the past if the build number is not > incremented. > > If I don't get problems I can easily do another release with the updates you > mentioned. If I get me act together, I plan to do a release every couple of > weeks anyway. > > -- > Phil Holmes > > > ----- Original Message ----- > From: "Jonas Hahnfeld" < > hah...@hahnjo.de > > > To: "Phil Holmes" < > em...@philholmes.net > >; "Devel" < > lilypond-devel@gnu.org > > > Sent: Wednesday, July 15, 2020 4:09 PM > Subject: Re: Today's problem with GUB build > >
signature.asc
Description: This is a digitally signed message part