Re: ready for 2.21.80?

2020-11-01 Thread Jonas Hahnfeld
Am Sonntag, den 01.11.2020, 13:54 +0100 schrieb Jonas Hahnfeld: > Am Sonntag, den 01.11.2020, 12:36 + schrieb Phil Holmes: > > On 01/11/2020 12:30, Jonas Hahnfeld wrote: > > > Am Sonntag, den 01.11.2020, 12:02 + schrieb Phil Holmes: > > > > Thanks.  Now uploaded. > > > Thanks to you for

Re: ready for 2.21.80?

2020-11-01 Thread Jonas Hahnfeld
Am Sonntag, den 01.11.2020, 12:36 + schrieb Phil Holmes: > On 01/11/2020 12:30, Jonas Hahnfeld wrote: > > Am Sonntag, den 01.11.2020, 12:02 + schrieb Phil Holmes: > > > Thanks.  Now uploaded. > > Thanks to you for staying with us while we resolve such things! > > > > > We do need to get

Re: ready for 2.21.80?

2020-11-01 Thread Phil Holmes
On 01/11/2020 12:30, Jonas Hahnfeld wrote: Am Sonntag, den 01.11.2020, 12:02 + schrieb Phil Holmes: Thanks.  Now uploaded. Thanks to you for staying with us while we resolve such things! We do need to get the latest/correct VERSION into master, as well as updating the news details. 

Re: ready for 2.21.80?

2020-11-01 Thread Jonas Hahnfeld
Am Sonntag, den 01.11.2020, 12:02 + schrieb Phil Holmes: > Thanks.  Now uploaded. Thanks to you for staying with us while we resolve such things! > We do need to get the latest/correct VERSION into master, as well as updating > the news details.  That should allow the website to be rebuilt. 

Re: ready for 2.21.80?

2020-11-01 Thread Phil Holmes
Thanks.  Now uploaded.  We do need to get the latest/correct VERSION into master, as well as updating the news details.  That should allow the website to be rebuilt.  I'm assuming that the best bet would be to cherry-pick the news updates from stable/2.22 into release/unstable, and edit and

Re: ready for 2.21.80?

2020-10-31 Thread Jonas Hahnfeld
Am Samstag, den 31.10.2020, 17:55 +0100 schrieb Jonas Hahnfeld: > Am Samstag, den 31.10.2020, 16:43 + schrieb Phil Holmes: > > GUB now almost completes, but fails making one of the German docs.  It > > looks like this is the error: > > > > Forking into jobs:  (10998 10997 10996 10995 10994

Re: ready for 2.21.80?

2020-10-31 Thread Jonas Hahnfeld
Am Samstag, den 31.10.2020, 16:43 + schrieb Phil Holmes: > GUB now almost completes, but fails making one of the German docs.  It looks > like this is the error: > > Forking into jobs:  (10998 10997 10996 10995 10994 10993 10992 10991) > logfile lilypond-multi-run-5.log (exit 1): > ne

Re: ready for 2.21.80?

2020-10-31 Thread Phil Holmes
GUB now almost completes, but fails making one of the German docs.  It looks like this is the error: Forking into jobs:  (10998 10997 10996 10995 10994 10993 10992 10991) logfile lilypond-multi-run-5.log (exit 1): ne breaks... Drawing systems... Writing ./16/lily-ec7f1c19-1.signature Layout

Re: ready for 2.21.80?

2020-10-31 Thread Phil Holmes
Nuked the build directory and redid configur, etc., and all now looks good, thanks. On 31/10/2020 15:16, Jonas Hahnfeld wrote: Am Samstag, den 31.10.2020, 15:08 + schrieb Phil Holmes: Fails trying to do the PO make: phil@ubuntu12:~/lilypond-git$ make -C $LILYPOND_BUILD_DIR po-replace

Re: ready for 2.21.80?

2020-10-31 Thread Jonas Hahnfeld
Am Samstag, den 31.10.2020, 15:08 + schrieb Phil Holmes: > Fails trying to do the PO make: > > phil@ubuntu12:~/lilypond-git$ make -C $LILYPOND_BUILD_DIR po-replace > make: Entering directory '/media/IntelSSD/lilypond/lilypond-git/build' >

Re: ready for 2.21.80?

2020-10-31 Thread Phil Holmes
Fails trying to do the PO make: phil@ubuntu12:~/lilypond-git$ make -C $LILYPOND_BUILD_DIR po-replace make: Entering directory '/media/IntelSSD/lilypond/lilypond-git/build' /home/phil/lilypond-git/build/.././make/stepmake.make:116:

Re: ready for 2.21.80?

2020-10-31 Thread Phil Holmes
I see your confusion.  My eyes obviously need testing :-( On 31/10/2020 13:31, Jonas Hahnfeld wrote: Am Samstag, den 31.10.2020, 13:23 + schrieb Phil Holmes: Looking at this now.  I see that in the 2.22 branch VERSION numbers are stable 2.22.0 and devel will be 2.21.80.  I've never really

Re: ready for 2.21.80?

2020-10-31 Thread Jonas Hahnfeld
Am Samstag, den 31.10.2020, 13:23 + schrieb Phil Holmes: > Looking at this now.  I see that in the 2.22 branch VERSION numbers are > stable 2.22.0 and devel will be 2.21.80.  I've never really worked out how > GUB decides to create a new stable version or a development version, but it's >

Re: ready for 2.21.80?

2020-10-31 Thread Phil Holmes
Looking at this now.  I see that in the 2.22 branch VERSION numbers are stable 2.22.0 and devel will be 2.21.80.  I've never really worked out how GUB decides to create a new stable version or a development version, but it's conceivable that it creates the highest numerical version.  I'm

Re: ready for 2.21.80?

2020-10-29 Thread Phil Holmes
Should get this done over the weekend. On 29/10/2020 15:52, Jonas Hahnfeld wrote: Am Sonntag, den 25.10.2020, 14:42 +0100 schrieb Jonas Hahnfeld: As the title says. We still need to merge the PO translations (see https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick them to

Re: ready for 2.21.80?

2020-10-29 Thread Jonas Hahnfeld
Am Sonntag, den 25.10.2020, 14:42 +0100 schrieb Jonas Hahnfeld: > As the title says. We still need to merge the PO translations (see > https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick > them to stable/2.22. If you speak one of the concerned languages that > I've been hijacking

Re: ready for 2.21.80?

2020-10-29 Thread Jonas Hahnfeld
Am Montag, den 26.10.2020, 16:59 +0100 schrieb Jean-Charles Malahieude: > Le 26/10/2020 à 12:06, Jonas Hahnfeld a écrit : > > […] > > Changing directory before invoking lilypond-book might solve this > > problem and help against similar issues in the future: > >

Re: ready for 2.21.80?

2020-10-26 Thread Jean-Charles Malahieude
Le 26/10/2020 à 12:06, Jonas Hahnfeld a écrit : […] Changing directory before invoking lilypond-book might solve this problem and help against similar issues in the future: https://gitlab.com/lilypond/lilypond/-/merge_requests/479 This looks good in preliminary testing, both with separate build

Re: ready for 2.21.80?

2020-10-26 Thread Jonas Hahnfeld
Am Sonntag, den 25.10.2020, 20:14 +0100 schrieb Jonas Hahnfeld: > Am Sonntag, den 25.10.2020, 19:57 +0100 schrieb Jonas Hahnfeld: > > Am Sonntag, den 25.10.2020, 19:29 +0100 schrieb Jean-Charles > > Malahieude: > > > Le 25/10/2020 à 19:13, Jonas Hahnfeld a écrit : > > > > I can try to help if I

Re: ready for 2.21.80?

2020-10-25 Thread Jonas Hahnfeld
Am Sonntag, den 25.10.2020, 19:57 +0100 schrieb Jonas Hahnfeld: > Am Sonntag, den 25.10.2020, 19:29 +0100 schrieb Jean-Charles > Malahieude: > > Le 25/10/2020 à 19:13, Jonas Hahnfeld a écrit : > > > I can try to help if I understand the problem in detail. As you mention > > > the NR, you're

Re: ready for 2.21.80?

2020-10-25 Thread Jonas Hahnfeld
Am Sonntag, den 25.10.2020, 19:29 +0100 schrieb Jean-Charles Malahieude: > Le 25/10/2020 à 19:13, Jonas Hahnfeld a écrit : > > > > I can try to help if I understand the problem in detail. As you mention > > the NR, you're probably referring to the Selected Snippets / Morceaux > > choisis? The

Re: ready for 2.21.80?

2020-10-25 Thread Jean-Charles Malahieude
Le 25/10/2020 à 19:13, Jonas Hahnfeld a écrit : I can try to help if I understand the problem in detail. As you mention the NR, you're probably referring to the Selected Snippets / Morceaux choisis? The first example would be:

Re: ready for 2.21.80?

2020-10-25 Thread Jonas Hahnfeld
Am Sonntag, den 25.10.2020, 18:01 +0100 schrieb Jean-Charles Malahieude: > Le 25/10/2020 à 14:42, Jonas Hahnfeld a écrit : > > As the title says. We still need to merge the PO translations (see > > https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick > > them to stable/2.22. If you

Re: ready for 2.21.80?

2020-10-25 Thread Jean-Charles Malahieude
Le 25/10/2020 à 14:42, Jonas Hahnfeld a écrit : As the title says. We still need to merge the PO translations (see https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick them to stable/2.22. If you speak one of the concerned languages that I've been hijacking the translation for

Re: ready for 2.21.80?

2020-10-25 Thread Dan Eble
On Oct 25, 2020, at 09:42, Jonas Hahnfeld wrote: > > As the title says. We still need to merge the PO translations (see > https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick > them to stable/2.22. If you speak one of the concerned languages that > I've been hijacking the

ready for 2.21.80?

2020-10-25 Thread Jonas Hahnfeld
As the title says. We still need to merge the PO translations (see https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick them to stable/2.22. If you speak one of the concerned languages that I've been hijacking the translation for (ca, eo, es, it, nl, sv), please consider giving it