Hi David,
it looks like now both branches have master merged and are identical:
$ git diff origin/dev/translation-merge origin/translation
[empty]
Is that intended?
To me this sounds conceptually wrong, given that you want to use one of
them (I didn't understand which one) for 2.20.1 - I don't
Am Montag, den 02.03.2020, 21:40 +0100 schrieb David Kastrup:
> Jonas Hahnfeld <
> hah...@hahnjo.de
> > writes:
>
> > Am Montag, den 02.03.2020, 20:10 +0100 schrieb David Kastrup:
> > > dev/translation-merge
> > >
> > > Fails at make test (at least on my system).
> >
> > Ah, the merge
I am forwarding a message I sent to the translators list for the
information of everyone.
I would like to merge what is now the translation branch into staging
soon (at the current point of time, this would be a fast-forward but I'd
probably make it an explicit merge commit).
Please check
Hi,
Some time ago, I heard of a fantastic GSoC project aimed at enabling
cross-staff spanners.
[1]https://lilypondblog.org/2016/08/google-summer-of-code-2016-cross-vo
ice-spanners/
However, this is not yet in any release.
For the score I'm engraving, it would be
David Kastrup writes:
> Jonas Hahnfeld writes:
>
>> Am Montag, den 02.03.2020, 20:10 +0100 schrieb David Kastrup:
>>> dev/translation-merge
>>>
>>> Fails at make test (at least on my system).
>>
>> Ah, the merge re-instantiated some code for Python 2. The following
>> diff fixes 'make test'
Jonas Hahnfeld writes:
> Am Montag, den 02.03.2020, 20:10 +0100 schrieb David Kastrup:
>> dev/translation-merge
>>
>> Fails at make test (at least on my system).
>
> Ah, the merge re-instantiated some code for Python 2. The following
> diff fixes 'make test' for me:
Pushed something that is
Jonas Hahnfeld writes:
> Am Montag, den 02.03.2020, 20:10 +0100 schrieb David Kastrup:
>> dev/translation-merge
>>
>> Fails at make test (at least on my system).
>
> Ah, the merge re-instantiated some code for Python 2. The following
> diff fixes 'make test' for me:
[...]
> But very please DO
Folks--
It seems that I've got a working process for 64-bit Mac builds of LilyPond,
and I will soon automate the process to build Mac .app bundles for every
tagged release. Which brings me to the next question: what is the process
to update the LilyPond website so that download links for these
On Mon, Mar 2, 2020 at 1:15 AM Werner LEMBERG wrote:
>
> > how do I set LOCALEDIR (in this case, to match the packaged app
> > bundle rather than the build-time path)? Unlike everything else of
> > this nature, neither the .reloc files nor environment variables work
> > (and I've tried setting
Am Montag, den 02.03.2020, 20:10 +0100 schrieb David Kastrup:
> dev/translation-merge
>
> Fails at make test (at least on my system).
Ah, the merge re-instantiated some code for Python 2. The following
diff fixes 'make test' for me:
diff --git a/python/musicxml.py b/python/musicxml.py
index
Jonas Hahnfeld writes:
> Am Montag, den 02.03.2020, 19:53 +0100 schrieb David Kastrup:
>> I am currently trying to merge translations and master. make test gives
>> me
>>
>> [...]
>> Making input/regression/lilypond-book/out-test/html-musicxml-file.html <
>> htmly
>> langdefs.py: warning:
Am Montag, den 02.03.2020, 19:53 +0100 schrieb David Kastrup:
> I am currently trying to merge translations and master. make test gives
> me
>
> [...]
> Making input/regression/lilypond-book/out-test/html-musicxml-file.html < htmly
> langdefs.py: warning: lilypond-doc gettext domain not found.
>
Jonas Hahnfeld writes:
> Sure, the solution is to apply #5799. Turns out the solution is not
> only for x86_64-w64-mingw32 but also for 32 bit mingw that GUB
> uses. So I'm arguing that it should go in before 2.21.0 is cut.
Well, the rationale for being conservative with new patches is so that
I am currently trying to merge translations and master. make test gives
me
Dissecting...
All snippets are up to date...
Linking files...
Compiling
/usr/local/tmp/lilypond/input/regression/midi/out-test/collated-files.texi...
Writing
Am Montag, den 02.03.2020, 19:38 +0100 schrieb David Kastrup:
> Jonas Hahnfeld <
> hah...@hahnjo.de
> > writes:
>
> > Am Montag, den 02.03.2020, 10:48 +0100 schrieb Jonas Hahnfeld:
> > > Am Sonntag, den 01.03.2020, 15:39 +0100 schrieb David Kastrup:
> > > > But fortunately, we are now at the
Jonas Hahnfeld writes:
> Am Montag, den 02.03.2020, 10:48 +0100 schrieb Jonas Hahnfeld:
>> Am Sonntag, den 01.03.2020, 15:39 +0100 schrieb David Kastrup:
>> >
>> > But fortunately, we are now at the point where 2.20 _and_ 2.21 are going
>> > to be a thing rather soon. Assuming that things like
Am Montag, den 02.03.2020, 10:48 +0100 schrieb Jonas Hahnfeld:
> Am Sonntag, den 01.03.2020, 15:39 +0100 schrieb David Kastrup:
> >
> > But fortunately, we are now at the point where 2.20 _and_ 2.21 are going
> > to be a thing rather soon. Assuming that things like the Python3
> > migration
I've just put an update in staging.
--
Phil Holmes
- Original Message -
From: "Trevor"
To: "Lily-Devel List"
Sent: Sunday, March 01, 2020 11:10 PM
Subject: Missing link
Congratulations to all involved in getting 2.20 out the door!
This is a big step forward.
One minor glitch I
LGTM, thanks!
https://codereview.appspot.com/571780043/
OK, now I got it.
Suppose I've erroneously treated these cases as broken line + 8-char
indent.
Now it should be the way you want it to be.
Cheers,
Torsten
https://codereview.appspot.com/571780043/
On 2020/02/29 22:53:43, lemzwerg wrote:
> > > Can we assume that FontForge's python support and is
> > > always enabled? Shall we check this?
> >
> > the FF page doesn't say that python is optional.
>
> It's a build option in both the old (configure) and new (cmake)
builds...
GUB doesn't have
> On 2 Mar 2020, at 01:46, Marnen Laibow-Koser wrote:
>
> On Sun, Mar 1, 2020 at 7:04 PM Hans Åberg wrote:
>
> > On 1 Mar 2020, at 23:45, Marnen Laibow-Koser wrote:
> >
> > One question as I continue to work on 64-bit Mac packaging: how do I set
> > LOCALEDIR (in this case, to match the
Am Sonntag, den 01.03.2020, 15:39 +0100 schrieb David Kastrup:
>
> But fortunately, we are now at the point where 2.20 _and_ 2.21 are going
> to be a thing rather soon. Assuming that things like the Python3
> migration don't cause more of a standstill for 2.21.0 than we imagine,
> but then one
23 matches
Mail list logo
