PATCHES - Countdown for April 5th

Hello, Here is the current patch countdown list. The next countdown will be on April 6th A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ *** Push: 5872 convert-ly rule for 2.19.39 as cleanup for issue 4800

New Esperanto PO file for 'lilypond' (version 2.19.84)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Esperanto team of translators. The file is available at: https://translationproject.org/latest/lilypond/eo.po (We can arrange things so

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On Sat, Apr 4, 2020 at 1:43 PM wrote: > > I will run this through "make check" and push to staging now. > Done. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 2020/04/04 07:53:24, hahnjo wrote: > 1: As a side note, this means there's a very funny workaround: Just push *any* > commit to master with a pure ASCII description and you'll not see the failure > anymore :D In the distance, a brass band plays "The Star-Spangled Banner." https://codereview.a

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

I will run this through "make check" and push to staging now. https://codereview.appspot.com/563810043/diff/545810044/scripts/build/output-distance.py File scripts/build/output-distance.py (right): https://codereview.appspot.com/563810043/diff/545810044/scripts/build/output-distance.py#newcode13

Re: Remove all uses of markup macro from scm/*.scm (issue 575930043 by d...@gnu.org)

On 2020/04/03 23:27:47, dak wrote: > On 2020/04/03 22:22:31, hanwenn wrote: > > note that this still doesn't fix the next error message for compilation which > is > > > > > > > > fatal error: Not a markup command: line > > > > which is triggered by the *definition* of the markup macro: > > > >

Re: how to test patches?

James Lowe writes: > Hello, > > So nothing has changed in master since yesterday. > > Therefore any make check is going to fall over on my testing. > > What to do? You could do commit -m "nonsense" --allow-empty on current master, do your tests, and afterwards do git reset --hard HEAD~1 to r

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

Valentin Villenave writes: > On 4/4/20, jonas.hahnf...@gmail.com wrote: >> The reason is that the latest commit in master has a non-ASCII >> character in the first line of its commit message [1]. > > So IIUC it *was* f5f907599ce88d3d610483fa42fa78be12f53d2e in the end… > but just because of a ch

how to test patches?

Hello, So nothing has changed in master since yesterday. Therefore any make check is going to fall over on my testing. What to do? Regards James

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 2020/04/04 09:07:08, hahnjo wrote: > On 2020/04/04 09:04:50, pkx166h-lilypond wrote: > > Actually I am using Python 2.7. I don't as far as I can tell have any python > 3.x > > on my system. > > > > James > > That's impossible ;-) it's required in master and you tested the patch switching > to

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 2020/04/04 09:02:01, valentin_villenave.net wrote: > On 4/4/20, mailto:jonas.hahnf...@gmail.com wrote: > > The reason is that the latest commit in master has a non-ASCII > > character in the first line of its commit message [1]. > > So IIUC it *was* f5f907599ce

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 2020/04/04 09:04:50, pkx166h-lilypond wrote: > Actually I am using Python 2.7. I don't as far as I can tell have any python 3.x > on my system. > > James That's impossible ;-) it's required in master and you tested the patch switching to Python 3, so I'm fairly certain you have it. The executa

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 2020/04/04 07:16:40, hahnjo wrote: > On 2020/04/03 22:15:06, hanwenn wrote: > > On 2020/04/03 22:00:02, dak wrote: > > > Is this likely related to the problems in `make check` that James currently > > > experiences? > > > > Yes. > > > > Unfortunately, the default encoding depends on the envir

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 4/4/20, jonas.hahnf...@gmail.com wrote: > The reason is that the latest commit in master has a non-ASCII > character in the first line of its commit message [1]. So IIUC it *was* f5f907599ce88d3d610483fa42fa78be12f53d2e in the end… but just because of a char in the commit message!? Man, how f

Re: Cannot make check from current master (with no patches applied)

Hello, On 03/04/2020 16:56, David Kastrup wrote: David Kastrup writes: Valentin Villenave writes: On 4/3/20, David Kastrup wrote: Anybody have an idea whose Patchy pushed the following: commit f5f907599ce88d3d610483fa42fa78be12f53d2e Uh, I did push it onto staging after the usual review

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

To add another data point: I'm able to reproduce the failure with a self-compiled Python 3.5.9 that I have laying around for testing. The reason is that the latest commit in master has a non-ASCII character in the first line of its commit message [1]. Applying the change to open_write_file solves t

Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)

On 2020/04/03 22:15:06, hanwenn wrote: > On 2020/04/03 22:00:02, dak wrote: > > Is this likely related to the problems in `make check` that James currently > > experiences? > > Yes. > > Unfortunately, the default encoding depends on the environment > > " > In text mode, if encoding is not s