Apparently it's also broken in a local 'make doc'. I think I chose the wrong strategy to fix the build with Python 3.5, see https://codereview.appspot.com/563860043 for a proposed fix.
As far as I understand, the website build of lilypond.org doesn't use the scripts from git directly, but instead has "trusted" versions. So these may need updating after the above change lands? Alternatively, whoever is able to can update them now and we can test if the change also works there. Jonas Am Sonntag, den 12.04.2020, 12:36 +0200 schrieb Han-Wen Nienhuys: > If you build the website locally, does it not have the 'b' all over the place? > > On Sun, Apr 12, 2020 at 12:29 PM David Kastrup < > d...@gnu.org > > wrote: > > > > We currently have web pages looking like > > > > <http://lilypond.org/development.html> > > > > > > There are lots of text of the b'...' variety and obviously the download > > sizes are not indicated (so that thing went wrong as well). > > > > This might be related to some Python2/Python3 problem with regard to the > > broken strings. > > > > Anybody with an idea how the deployment of our web sites works or is > > supposed to work and what to do at least in terms of the broken strings? > > > > -- > > David Kastrup
signature.asc
Description: This is a digitally signed message part
