screech-and-boink.ly
Hey all, I'm getting the following when compiling a local branch based off of master: LILYPOND_VERSION=2.15.41 /usr/bin/python /home/mikesol/lilypond-git/scripts/lilypond-book.py -I /home/mikesol/lilypond-git/Documentation/ -I ./out -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/build/Documentation/snippets/out -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output /home/mikesol/lilypond-git/Documentation/usage.tely lilypond-book.py: error: file not found: screech-and-boink.ly It's a branch I hadn't compiled for some time, so I'm not sure if there's a problem w/ deleted files or what have you. I did a git pull before compiling off of current master. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
m...@mikesolomon.org m...@mikesolomon.org writes: Hey all, I'm getting the following when compiling a local branch based off of master: LILYPOND_VERSION=2.15.41 /usr/bin/python /home/mikesol/lilypond-git/scripts/lilypond-book.py -I /home/mikesol/lilypond-git/Documentation/ -I ./out -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/build/Documentation/snippets/out -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitl ehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output /home/mikesol/lilypond-git/Documentation/usage.tely lilypond-book.py: error: file not found: screech-and-boink.ly It's a branch I hadn't compiled for some time, so I'm not sure if there's a problem w/ deleted files or what have you. I did a git pull before compiling off of current master. dak@lola:/usr/local/tmp/lilypond$ git log origin --graph --decorate Documentation/snippets/screech-and-boink.ly * commit 58933e3e40e9cfbdc70b846bc808c723e053f7b3 | Author: Phil Holmes m...@philholmes.net | Date: Tue Jun 26 11:50:43 2012 +0100 | | LSR updates from tarball | * commit f71ede90de06fdc16dad9ed75f38558efe819080 Author: Phil Holmes m...@philholmes.net Date: Sun Apr 8 18:35:34 2012 +0100 New version of LSR upgrade The commit in June, however, just updates the version, so it should not be relevant. The question is what happened here: whether you are missing the file, or whether the file has not been copied to the place where it is expected. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
- Original Message - From: m...@mikesolomon.org To: Devel Dev lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 9:01 AM Subject: screech-and-boink.ly Hey all, I'm getting the following when compiling a local branch based off of master: LILYPOND_VERSION=2.15.41 /usr/bin/python /home/mikesol/lilypond-git/scripts/lilypond-book.py -I /home/mikesol/lilypond-git/Documentation/ -I ./out -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/build/Documentation/snippets/out -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output /home/mikesol/lilypond-git/Documentation/usage.tely lilypond-book.py: error: file not found: screech-and-boink.ly It's a branch I hadn't compiled for some time, so I'm not sure if there's a problem w/ deleted files or what have you. I did a git pull before compiling off of current master. Cheers, MS Is this after deleting your build directory and starting from scratch? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: formatted GNUmakefile
Werner LEMBERG writes: And here is a revised version which shortens even more overlong lines. +1 SUBDIRS = \ python scripts \ I'm a big fan of splitting lists into one entry per line; esp. if you break at position 20 rather than 78. We still have no sensible word-based diff format; as long as diffs work per line, mutations are much more obvious and readable that way. test-clean: test-snippets-clean $(MAKE) -C input/regression \ out=test \ clean This would be debatable. As it is only 50 characters wide, I would probably put in on one line. Otoh, it helps with the diff rule above. Mostly a matter of taste. Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
issue 6352049 - regtest
Hi, I wanted to follow Grahams proposal on http://codereview.appspot.com/6352049/#msg4 about adding a reg-test. I performed these steps: - creating a new file, naming it: page-headers-and-footers.ly - pasting it into /input/regression - Pressing the Ammend previous commit of the LilyDev-GUI to prepare a new patch set But I can't create a new local commit or a patch set which contains page-headers-and-footers.ly What am I doing wrong? -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
On 30 juin 2012, at 12:04, Phil Holmes wrote: - Original Message - From: m...@mikesolomon.org To: Devel Dev lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 9:01 AM Subject: screech-and-boink.ly Hey all, I'm getting the following when compiling a local branch based off of master: LILYPOND_VERSION=2.15.41 /usr/bin/python /home/mikesol/lilypond-git/scripts/lilypond-book.py -I /home/mikesol/lilypond-git/Documentation/ -I ./out -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/build/Documentation/snippets/out -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output /home/mikesol/lilypond-git/Documentation/usage.tely lilypond-book.py: error: file not found: screech-and-boink.ly It's a branch I hadn't compiled for some time, so I'm not sure if there's a problem w/ deleted files or what have you. I did a git pull before compiling off of current master. Cheers, MS Is this after deleting your build directory and starting from scratch? -- Phil Holmes Yup. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
On 30 juin 2012, at 10:30, David Kastrup wrote: m...@mikesolomon.org m...@mikesolomon.org writes: Hey all, I'm getting the following when compiling a local branch based off of master: LILYPOND_VERSION=2.15.41 /usr/bin/python /home/mikesol/lilypond-git/scripts/lilypond-book.py -I /home/mikesol/lilypond-git/Documentation/ -I ./out -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/build/Documentation/snippets/out -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitl ehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output /home/mikesol/lilypond-git/Documentation/usage.tely lilypond-book.py: error: file not found: screech-and-boink.ly It's a branch I hadn't compiled for some time, so I'm not sure if there's a problem w/ deleted files or what have you. I did a git pull before compiling off of current master. dak@lola:/usr/local/tmp/lilypond$ git log origin --graph --decorate Documentation/snippets/screech-and-boink.ly * commit 58933e3e40e9cfbdc70b846bc808c723e053f7b3 | Author: Phil Holmes m...@philholmes.net | Date: Tue Jun 26 11:50:43 2012 +0100 | | LSR updates from tarball | * commit f71ede90de06fdc16dad9ed75f38558efe819080 Author: Phil Holmes m...@philholmes.net Date: Sun Apr 8 18:35:34 2012 +0100 New version of LSR upgrade The commit in June, however, just updates the version, so it should not be relevant. The question is what happened here: whether you are missing the file, or whether the file has not been copied to the place where it is expected. -- David Kastrup The file is in Documentation/snippets/ As for the copying, I'm not sure... I build in a separate build directory, but I nuked it and started from scratch and still got the same problem. ~Mike ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: issue 6352049 - regtest
Thomas Morley thomasmorle...@googlemail.com writes: Hi, I wanted to follow Grahams proposal on http://codereview.appspot.com/6352049/#msg4 about adding a reg-test. I performed these steps: - creating a new file, naming it: page-headers-and-footers.ly - pasting it into /input/regression - Pressing the Ammend previous commit of the LilyDev-GUI to prepare a new patch set But I can't create a new local commit or a patch set which contains page-headers-and-footers.ly What am I doing wrong? Likely git is not even considering your file as something it should be interested in. git add input/regression/page-headers-and-footers.ly should change that. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: issue 6352049 - regtest
On Sat, Jun 30, 2012 at 12:38:17PM +0200, Thomas Morley wrote: I performed these steps: - creating a new file, naming it: page-headers-and-footers.ly - pasting it into /input/regression - Pressing the Ammend previous commit of the LilyDev-GUI to prepare a new patch set But I can't create a new local commit or a patch set which contains page-headers-and-footers.ly I'm not certain that lily-git.tcl supports adding new files, since that's a rare thing. Open a terminal, go to your lilypond source directory, then type git add input/regression/page-headers-and-footers.ly then go back to lily-git.tcl, make amand previous commit, and you should get it included in the patch set. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
m...@apollinemike.com m...@apollinemike.com writes: The file is in Documentation/snippets/ As for the copying, I'm not sure... I build in a separate build directory, but I nuked it and started from scratch and still got the same problem. Does started from scratch include rerunning autogen.sh? I am just now doing a rerun without separate build directory (does this only happen with make doc, or is make all sufficient?). If that works, I'll check with it. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: which-page (issue 6352049)
On 2012/06/29 10:13:42, t.daniels_treda.co.uk wrote: Thomas Morley wrote Friday, June 29, 2012 10:32 AM Of course all features (old and new) should be documented. But, AFAICT, non of the possibilities offered in /ly/titling-init.ly (i.e. first-page, last-page, not-first-page, part-last-page) is documented anywhere in LM or NR. Well, they should be documented, but I propose to open a new issue to do so. Eluze already opened an issue for this - 2579 - and I'm part-way through a fix to the docs. I'll upload it for review shortly, and I'd appreciate your comments and help. Will do. I found only one multi-page-file in the regression-tests containing a feature of titling-init.ly (i.e. `not-first-page'): input/regression/page-breaks.ly But I think this file tests something else. So I'd suggest to open a new issue for that, too. Fine - please do. Regtest added now. -Harm http://codereview.appspot.com/6352049/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: issue 6352049 - regtest
2012/6/30 Graham Percival gra...@percival-music.ca: On Sat, Jun 30, 2012 at 12:38:17PM +0200, Thomas Morley wrote: I performed these steps: - creating a new file, naming it: page-headers-and-footers.ly - pasting it into /input/regression - Pressing the Ammend previous commit of the LilyDev-GUI to prepare a new patch set But I can't create a new local commit or a patch set which contains page-headers-and-footers.ly I'm not certain that lily-git.tcl supports adding new files, since that's a rare thing. Open a terminal, go to your lilypond source directory, then type git add input/regression/page-headers-and-footers.ly then go back to lily-git.tcl, make amand previous commit, and you should get it included in the patch set. - Graham Thanks Graham, thanks David, now it works. Just uploaded a new patch set. One tiny thing. The terminal returns as last message: WARNING: could not change issue labels; please email lilypond-devel with the issue number: 2626 Tracker issue done Don't know what that means. -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Regression test rater
First of all, thanks to those who have spent time and energy rating the regression test at http://www.philholmes.net/lilypond/regtests/ - we're very close to having a rating for all the tests. I'd like to let you know that I've updated the way it works to how it really should have been in the first place - tests with the fewest ratings are presented before tests with a number of ratings, so every rating added now will be the first for that regtest - we've only a few to get that initial rating, so please have another go. Please be assured that all the ratings have been captured, and once we have sufficient, I will make sure that the regtests are updated to take account of the comments. Thanks again, and please give it a further push. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: issue 6352049 - regtest
On Sat, Jun 30, 2012 at 03:32:50PM +0200, Thomas Morley wrote: One tiny thing. The terminal returns as last message: WARNING: could not change issue labels; please email lilypond-devel with the issue number: 2626 Tracker issue done Don't know what that means. It means that your gmail account is not registered with the lilypond google project. Either Phil or Colin should add you to the project (I can't recall if Colin's been added as an owner or not). For now, I've made 2626 Patch-new. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: issue 6352049 - regtest
- Original Message - From: Graham Percival gra...@percival-music.ca To: Thomas Morley thomasmorle...@googlemail.com; Phil Holmes em...@philholmes.net; Colin Campbell c...@shaw.ca Cc: David Kastrup d...@gnu.org; lilypond-devel lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 2:50 PM Subject: Re: issue 6352049 - regtest On Sat, Jun 30, 2012 at 03:32:50PM +0200, Thomas Morley wrote: One tiny thing. The terminal returns as last message: WARNING: could not change issue labels; please email lilypond-devel with the issue number: 2626 Tracker issue done Don't know what that means. It means that your gmail account is not registered with the lilypond google project. Either Phil or Colin should add you to the project (I can't recall if Colin's been added as an owner or not). For now, I've made 2626 Patch-new. - Graham Colin is able to make the change, but since I was here I've done it - Thomas has been added as a committer to the Google issue tracker. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Get texidoc translations out of snippets source files(issue6352053)
- Original Message - From: Phil Holmes m...@philholmes.net To: Graham Percival gra...@percival-music.ca; john.mander...@gmail.com; philehol...@googlemail.com; lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com Sent: Friday, June 29, 2012 6:11 PM Subject: Re: Get texidoc translations out of snippets source files(issue6352053) - Original Message - From: Graham Percival gra...@percival-music.ca To: john.mander...@gmail.com; philehol...@googlemail.com; lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com Sent: Friday, June 29, 2012 5:27 PM Subject: Re: Get texidoc translations out of snippets source files (issue6352053) On Fri, Jun 29, 2012 at 03:56:03PM +, philehol...@googlemail.com wrote: http://codereview.appspot.com/6352053/diff/1/scripts/auxiliar/makelsr.py#newcode79 scripts/auxiliar/makelsr.py:79: default=out/bin, ... it would be better if the default was the build/out directory, and if convert-ly and lilypond aren't found, the script fails, with a message about how to use the -p option. Excellent catch! But let's take that one step further, and use $LILYPOND_BUILD_DIR/out/bin/ as the default. Now that John has gone through the fuss of creating it, let's use it. :) - Graham I think we may need to be careful how we get this patch into master, since it has a specific sequence of events associated: makelsr-from-tarball using this patch; push resulting Doc/snippets to git - if step one is done and step 2 delayed, we may get unpredictable results. -- Phil Holmes I see the patch is now in master. I think this means I need to use an archived copy of the LSR (the one I used for the last update of git from the tarball) to update Documentation/snippets using John's new script and push the resultant snippets to staging. That way, git will have newly correct versions of the snippets - without extraneous translations in them. Once that's OK, I'll grab a new tarball and repeat. Agreed? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
David Kastrup d...@gnu.org writes:
m...@apollinemike.com m...@apollinemike.com writes:
The file is in Documentation/snippets/
As for the copying, I'm not sure... I build in a separate build
directory, but I nuked it and started from scratch and still got the
same problem.
Does started from scratch include rerunning autogen.sh?
I am just now doing a rerun without separate build directory (does this
only happen with make doc, or is make all sufficient?). If that works,
I'll check with it.
Interestingly, I just got the same error
LILYPOND_VERSION=2.15.41 /usr/bin/python ../scripts/lilypond-book.py -I ./ -I
./out -I ../input -I /usr/local/tmp/lilypond/Documentation -I
/usr/local/tmp/lilypond/Documentation/snippets/out -I ../input/regression/ -I
/usr/local/tmp/lilypond/Documentation/included/ -I
/usr/local/tmp/lilypond/mf/out/ -I /usr/local/tmp/lilypond/mf/out/ -I
/usr/local/tmp/lilypond/Documentation/pictures -I
/usr/local/tmp/lilypond/Documentation/pictures/./out --process='true
-dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts
--header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees
--header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja
--header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs
--header=texidocde --header=texidoces --header=texidocfr --header=texidochu
--header=texidocit --header=texidocja --header=texidocnl --header=texidoczh
-dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out
--format=texi --loglevel=WARN --skip-lily-check --lily-output-dir
/usr/local/tmp/lilypond/out/lybook-db --redirect-lilypond-output usage.tely
langdefs.py: warning: lilypond-doc gettext domain not found.
lilypond-book.py: error: file not found: screech-and-boink.ly
make[1]: *** [out/usage.texi] Error 1
make[1]: Leaving directory `/usr/local/tmp/lilypond/Documentation'
make: *** [all] Error 2
after a few changes (non-separate build directory) and doing make on
master. It would appear that at the very least, some recent changes are
non-rubust against switching of branches.
git reflog here states
43fe858 HEAD@{0}: checkout: moving from 43fe858eb18418ae1d8867786ad873b7a4e2ae8a
43fe858 HEAD@{1}: commit: Fix description in lily/include/smobs.hh
e6a5019 HEAD@{2}: checkout: moving from grace to origin/staging
f3f25b6 HEAD@{3}: commit (amend): lots
ab03743 HEAD@{4}: commit: lots
fb4ec44 HEAD@{5}: checkout: moving from unrational to grace
5d0a0ba HEAD@{6}: commit: get rid of Rational
5e3f01b HEAD@{7}: checkout: moving from b5250b853d1a520e8245b895ad11bfdf0d636275
b5250b8 HEAD@{8}: commit: Fix polarity of rhythmic-location=?
e47e8dc HEAD@{9}: checkout: moving from moment to origin
and the grace branch is based off
commit 5a3cea00a530d2f80cfce66e58dbeadbfe373bb6
Author: David Kastrup d...@gnu.org
Date: Sat Jun 23 17:14:03 2012 +0200
Make third argument @var{alter} of ly:make-pitch optional.
This has already been the case in the function signature, but actual use
as an optional function argument resulted in an error message.
which is a rather recent commit, and similar things go for the other
stuff I checked out.
I'll see what kind of cleanup will do the trick here, but it clearly
_is_ a nuisance, being encountered by two different people so far.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
David Kastrup d...@gnu.org writes:
David Kastrup d...@gnu.org writes:
m...@apollinemike.com m...@apollinemike.com writes:
The file is in Documentation/snippets/
As for the copying, I'm not sure... I build in a separate build
directory, but I nuked it and started from scratch and still got the
same problem.
Does started from scratch include rerunning autogen.sh?
I am just now doing a rerun without separate build directory (does this
only happen with make doc, or is make all sufficient?). If that works,
I'll check with it.
Interestingly, I just got the same error
LILYPOND_VERSION=2.15.41 /usr/bin/python ../scripts/lilypond-book.py -I ./ -I
./out -I ../input -I /usr/local/tmp/lilypond/Documentation -I
/usr/local/tmp/lilypond/Documentation/snippets/out -I ../input/regression/ -I
/usr/local/tmp/lilypond/Documentation/included/ -I
/usr/local/tmp/lilypond/mf/out/ -I /usr/local/tmp/lilypond/mf/out/ -I
/usr/local/tmp/lilypond/Documentation/pictures -I
/usr/local/tmp/lilypond/Documentation/pictures/./out --process='true
-dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts
--header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees
--header=doctitlefr --header=doctitlehu --header=doctitleit
--header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc
--header=texidoccs --header=texidocde --header=texidoce
s --header=texidocfr --header=texidochu --header=texidocit
--header=texidocja --header=texidocnl --header=texidoczh
-dcheck-internal-types -ddump-signatures -danti-alias-factor=2'
--output=./out --format=texi --loglevel=WARN --skip-lily-check
--lily-output-dir /usr/local/tmp/lilypond/out/lybook-db
--redirect-lilypond-output usage.tely
langdefs.py: warning: lilypond-doc gettext domain not found.
lilypond-book.py: error: file not found: screech-and-boink.ly
make[1]: *** [out/usage.texi] Error 1
make[1]: Leaving directory `/usr/local/tmp/lilypond/Documentation'
make: *** [all] Error 2
after a few changes (non-separate build directory) and doing make on
master. It would appear that at the very least, some recent changes are
non-rubust against switching of branches.
git reflog here states
43fe858 HEAD@{0}: checkout: moving from
43fe858eb18418ae1d8867786ad873b7a4e2ae8a
43fe858 HEAD@{1}: commit: Fix description in lily/include/smobs.hh
e6a5019 HEAD@{2}: checkout: moving from grace to origin/staging
f3f25b6 HEAD@{3}: commit (amend): lots
ab03743 HEAD@{4}: commit: lots
fb4ec44 HEAD@{5}: checkout: moving from unrational to grace
5d0a0ba HEAD@{6}: commit: get rid of Rational
5e3f01b HEAD@{7}: checkout: moving from
b5250b853d1a520e8245b895ad11bfdf0d636275
b5250b8 HEAD@{8}: commit: Fix polarity of rhythmic-location=?
e47e8dc HEAD@{9}: checkout: moving from moment to origin
and the grace branch is based off
commit 5a3cea00a530d2f80cfce66e58dbeadbfe373bb6
Author: David Kastrup d...@gnu.org
Date: Sat Jun 23 17:14:03 2012 +0200
Make third argument @var{alter} of ly:make-pitch optional.
This has already been the case in the function signature, but actual use
as an optional function argument resulted in an error message.
which is a rather recent commit, and similar things go for the other
stuff I checked out.
I'll see what kind of cleanup will do the trick here, but it clearly
_is_ a nuisance, being encountered by two different people so far.
Rerunning make did not retrigger the error. Notice that I have _not_
been running any multi-job make, so we are not even talking about a race
condition here.
That makes me suspect one of the following commits that are all
build-system related.
commit e6a5019c531bbc6663e0eebc645409148dbd8931
Author: John Mandereau - LilyPond development john.mander...@gmail.com
Date: Thu Jun 28 18:32:18 2012 +0200
Clean fonts and docs makefiles, trying to fix 'make -j' race conditions
On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo),
make -j3 all repeatedly calls fontforge before needed .pfb files are
generated and makeinfo/extract_texi_filenames/texi2omf before .texi
file has been generated/copied. Fix this by using order prerequisites
and adding targets to WWW-1 (first stage of doc build); order (rather
than ordinary) prerequisites avoid having always outdated targets,
which would trigger compilation at install.
Remove a rule for Info manual that is no longer needed and which might
short-circuit .dep file generation.
mf/GNUmakefile: also factorize prerequisites in fonts using a macro.
commit 512d405d07aba8742658902b105a94ebbd40c2dc
Author: John Mandereau john.mander...@gmail.com
Date: Thu Jun 28 13:30:05 2012 +0200
Get texidoc translations out of snippets source files
generated and makeinfo/extract_texi_filenames/texi2omf before .texi
file has been generated/copied. Fix this by using order prerequisites
and adding targets to WWW-1
Updates to LSR make - problem?
Mike has raised a problem that he has had a make fail while trying to compile master. The failing line is: LILYPOND_VERSION=2.15.41 /usr/bin/python /home/mikesol/lilypond-git/scripts/lilypond-book.py -I /home/mikesol/lilypond-git/Documentation/ -I ./out -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/build/Documentation/snippets/out -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output /home/mikesol/lilypond-git/Documentation/usage.tely lilypond-book.py: error: file not found: screech-and-boink.ly This is an example of a snippet which is found in a general manual - in this case lilypond-book.itely, which is included in usage.tely It should be found, since we have the switch -I /home/mikesol/lilypond-git/build/Documentation/snippets/out in the call to lilypond-book. However, on Mike's machine, build/Doc/snippets/out does not exist - so the makesnippets script hasn't run (or hasn't completed properly). Do we have a missing dependency or something? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
David Kastrup d...@gnu.org writes: make clean all again delivers LILYPOND_VERSION=2.15.41 /usr/bin/python ../scripts/lilypond-book.py -I ./ -I ./out -I ../input -I /usr/local/tmp/lilypond/Documentation -I /usr/local/tmp/lilypond/Documentation/snippets/out -I ../input/regression/ -I /usr/local/tmp/lilypond/Documentation/included/ -I /usr/local/tmp/lilypond/mf/out/ -I /usr/local/tmp/lilypond/mf/out/ -I /usr/local/tmp/lilypond/Documentation/pictures -I /usr/local/tmp/lilypond/Documentation/pictures/./out --process='true -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN --skip-lily-check --lily-output-dir /usr/local/tmp/lilypond/out/lybook-db --redirect-lilypond-output usage.tely langdefs.py: warning: lilypond-doc gettext domain not found. lilypond-book.py: error: file not found: screech-and-boink.ly make[1]: *** [out/usage.texi] Error 1 make[1]: Leaving directory `/usr/local/tmp/lilypond/Documentation' make: *** [all] Error 2 That's not pretty. I start to suspect that some of the recent commits introduced a race condition that is only _avoided_ by using a multi-job make (like Patchy does). I'll clean _and_ reconfigure now, and if that does not help, we have a problem. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
On Sat, Jun 30, 2012 at 05:13:04PM +0200, David Kastrup wrote: commit e6a5019c531bbc6663e0eebc645409148dbd8931 Author: John Mandereau - LilyPond development john.mander...@gmail.com Date: Thu Jun 28 18:32:18 2012 +0200 Clean fonts and docs makefiles, trying to fix 'make -j' race conditions That patch is currently on a countdown and should not have been pushed. I wonder if John did a git push intending to update dev/jmanederau, without realizing that this pushes material on *all* branches? I've been bitten by that bug^Wpoor design decision of git. The same problem might apply to the other commits you identified; I haven't checked those. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates to LSR make - problem?
On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote: I suggest reverting recent build commits until git master can compile ok, NB: I'm making this suggestion as a normal developer, not as project manager. If anybody really likes build scripts, sees the problem, and can fix it quickly (recalling one anonymous survey commenting that in the old days everybody could fix everything (or something like that)), then by all means go ahead without reverting anything. I don't have the energy to enjoy dealing with crises in git master; my preference is to reject anything that's questionable and have a very placid and calm git master. Ideally by rejecting questionable material during the countdown phase. But if younger and more enthusiastic developers can fix it quickly, then go ahead. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
Graham Percival gra...@percival-music.ca writes: On Sat, Jun 30, 2012 at 05:13:04PM +0200, David Kastrup wrote: commit e6a5019c531bbc6663e0eebc645409148dbd8931 Author: John Mandereau - LilyPond development john.mander...@gmail.com Date: Thu Jun 28 18:32:18 2012 +0200 Clean fonts and docs makefiles, trying to fix 'make -j' race conditions That patch is currently on a countdown and should not have been pushed. I wonder if John did a git push intending to update dev/jmanederau, without realizing that this pushes material on *all* branches? I've been bitten by that bug^Wpoor design decision of git. URL:http://thread.gmane.org/gmane.comp.version-control.git/192547/focus=192694 but I have no idea how the discussion ended. Yes, it would appear that the above commit is a prime suspect and more likely than not was pushed by accident. By the way: make clean + reconfigure did _not_ do the trick. make all still fails with the same message. Trying with reverting this commit next. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates to LSR make - problem?
On Sat, Jun 30, 2012 at 04:23:02PM +0100, Phil Holmes wrote: in the call to lilypond-book. However, on Mike's machine, build/Doc/snippets/out does not exist - so the makesnippets script hasn't run (or hasn't completed properly). Do we have a missing dependency or something? makesnippets appears to have gotten onto staging by mistake; it patch on rietveld has not addressed your concerns. Presumably it was only intended to go to dev/jmanderau. I suggest reverting recent build commits until git master can compile ok, then we can start looking at the pieces to see which parts are good to commit (and in what order!), and which pieces need further examination. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
- Original Message - From: David Kastrup d...@gnu.org To: Graham Percival gra...@percival-music.ca Cc: lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 4:44 PM Subject: Re: screech-and-boink.ly Graham Percival gra...@percival-music.ca writes: On Sat, Jun 30, 2012 at 05:13:04PM +0200, David Kastrup wrote: commit e6a5019c531bbc6663e0eebc645409148dbd8931 Author: John Mandereau - LilyPond development john.mander...@gmail.com Date: Thu Jun 28 18:32:18 2012 +0200 Clean fonts and docs makefiles, trying to fix 'make -j' race conditions That patch is currently on a countdown and should not have been pushed. I wonder if John did a git push intending to update dev/jmanederau, without realizing that this pushes material on *all* branches? I've been bitten by that bug^Wpoor design decision of git. URL:http://thread.gmane.org/gmane.comp.version-control.git/192547/focus=192694 but I have no idea how the discussion ended. Yes, it would appear that the above commit is a prime suspect and more likely than not was pushed by accident. By the way: make clean + reconfigure did _not_ do the trick. make all still fails with the same message. Trying with reverting this commit next. It'll almost certainly be the makelsr updates that are causing the problem. I'd suggest reverting that first. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates to LSR make - problem?
Graham Percival gra...@percival-music.ca writes: On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote: I suggest reverting recent build commits until git master can compile ok, NB: I'm making this suggestion as a normal developer, not as project manager. If anybody really likes build scripts, sees the problem, and can fix it quickly (recalling one anonymous survey commenting that in the old days everybody could fix everything (or something like that)), then by all means go ahead without reverting anything. I am currently trying a revert of commit e6a5019c531bbc6663e0eebc645409148dbd8931 Author: John Mandereau - LilyPond development john.mander...@gmail.com Date: Thu Jun 28 18:32:18 2012 +0200 Clean fonts and docs makefiles, trying to fix 'make -j' race conditions On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo), make -j3 all repeatedly calls fontforge before needed .pfb files are generated and makeinfo/extract_texi_filenames/texi2omf before .texi file has been generated/copied. Fix this by using order prerequisites and adding targets to WWW-1 (first stage of doc build); order (rather than ordinary) prerequisites avoid having always outdated targets, which would trigger compilation at install. Remove a rule for Info manual that is no longer needed and which might short-circuit .dep file generation. mf/GNUmakefile: also factorize prerequisites in fonts using a macro. which looks totally complex and invasive regarding the build system. If this goes through compilation, I'll push the revert to staging. It will be Patchy-staging's job then to make sure that the revert still passes a multijob make as well. Reverse race conditions reliably occuring only on single CPU builds are one of the few things that patchy-staging is not good at detecting. But since one of the ideas of Patchy is to make good use of impressive CPU power, that's hard to avoid. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates to LSR make - problem?
- Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 4:52 PM Subject: Re: Updates to LSR make - problem? Graham Percival gra...@percival-music.ca writes: On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote: I suggest reverting recent build commits until git master can compile ok, NB: I'm making this suggestion as a normal developer, not as project manager. If anybody really likes build scripts, sees the problem, and can fix it quickly (recalling one anonymous survey commenting that in the old days everybody could fix everything (or something like that)), then by all means go ahead without reverting anything. I am currently trying a revert of commit e6a5019c531bbc6663e0eebc645409148dbd8931 Author: John Mandereau - LilyPond development john.mander...@gmail.com Date: Thu Jun 28 18:32:18 2012 +0200 Clean fonts and docs makefiles, trying to fix 'make -j' race conditions On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo), make -j3 all repeatedly calls fontforge before needed .pfb files are generated and makeinfo/extract_texi_filenames/texi2omf before .texi file has been generated/copied. Fix this by using order prerequisites and adding targets to WWW-1 (first stage of doc build); order (rather than ordinary) prerequisites avoid having always outdated targets, which would trigger compilation at install. Remove a rule for Info manual that is no longer needed and which might short-circuit .dep file generation. mf/GNUmakefile: also factorize prerequisites in fonts using a macro. which looks totally complex and invasive regarding the build system. If this goes through compilation, I'll push the revert to staging. It will be Patchy-staging's job then to make sure that the revert still passes a multijob make as well. Reverse race conditions reliably occuring only on single CPU builds are one of the few things that patchy-staging is not good at detecting. But since one of the ideas of Patchy is to make good use of impressive CPU power, that's hard to avoid. -- David Kastrup See my previous note. Please try reverting Get texidoc translations out of snippets source files first - I can give a cogent reason for why this is causing the problem. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
Phil Holmes m...@philholmes.net writes: Yes, it would appear that the above commit is a prime suspect and more likely than not was pushed by accident. By the way: make clean + reconfigure did _not_ do the trick. make all still fails with the same message. Trying with reverting this commit next. It'll almost certainly be the makelsr updates that are causing the problem. I'd suggest reverting that first. I wonder how: screech-and-boink.ly has only seen an update of the version string and nothing else recently. But I have to admit that reverting the prime suspect did not help. Error still occurs. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: screech-and-boink.ly
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Graham Percival gra...@percival-music.ca; lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 4:55 PM Subject: Re: screech-and-boink.ly Phil Holmes m...@philholmes.net writes: Yes, it would appear that the above commit is a prime suspect and more likely than not was pushed by accident. By the way: make clean + reconfigure did _not_ do the trick. make all still fails with the same message. Trying with reverting this commit next. It'll almost certainly be the makelsr updates that are causing the problem. I'd suggest reverting that first. I wonder how: screech-and-boink.ly has only seen an update of the version string and nothing else recently. But I have to admit that reverting the prime suspect did not help. Error still occurs. -- David Kastrup I think it's the first snippet that the build system tries to build with lilypond-book. On Mike's computer, the directory Doc/snippets/out does not exist, so no snippets would be found. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates to LSR make - problem?
- Original Message - From: Phil Holmes m...@philholmes.net To: lilypond-devel@gnu.org; David Kastrup d...@gnu.org Sent: Saturday, June 30, 2012 4:55 PM Subject: Re: Updates to LSR make - problem? - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Saturday, June 30, 2012 4:52 PM Subject: Re: Updates to LSR make - problem? Graham Percival gra...@percival-music.ca writes: On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote: I suggest reverting recent build commits until git master can compile ok, NB: I'm making this suggestion as a normal developer, not as project manager. If anybody really likes build scripts, sees the problem, and can fix it quickly (recalling one anonymous survey commenting that in the old days everybody could fix everything (or something like that)), then by all means go ahead without reverting anything. I am currently trying a revert of commit e6a5019c531bbc6663e0eebc645409148dbd8931 Author: John Mandereau - LilyPond development john.mander...@gmail.com Date: Thu Jun 28 18:32:18 2012 +0200 Clean fonts and docs makefiles, trying to fix 'make -j' race conditions On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo), make -j3 all repeatedly calls fontforge before needed .pfb files are generated and makeinfo/extract_texi_filenames/texi2omf before .texi file has been generated/copied. Fix this by using order prerequisites and adding targets to WWW-1 (first stage of doc build); order (rather than ordinary) prerequisites avoid having always outdated targets, which would trigger compilation at install. Remove a rule for Info manual that is no longer needed and which might short-circuit .dep file generation. mf/GNUmakefile: also factorize prerequisites in fonts using a macro. which looks totally complex and invasive regarding the build system. If this goes through compilation, I'll push the revert to staging. It will be Patchy-staging's job then to make sure that the revert still passes a multijob make as well. Reverse race conditions reliably occuring only on single CPU builds are one of the few things that patchy-staging is not good at detecting. But since one of the ideas of Patchy is to make good use of impressive CPU power, that's hard to avoid. -- David Kastrup See my previous note. Please try reverting Get texidoc translations out of snippets source files first - I can give a cogent reason for why this is causing the problem. -- FWIW I can confirm that the compile fails on my system when I do a single CPU build. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates to LSR make - problem?
Phil Holmes m...@philholmes.net writes: See my previous note. Please try reverting Get texidoc translations out of snippets source files first - I can give a cogent reason for why this is causing the problem. My computer agrees. Pushing the revert. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: illness
On Fri, Jun 29, 2012 at 10:54 PM, Valentin Villenave valen...@villenave.net wrote: On Thu, Jun 28, 2012 at 8:46 PM, Janek Warchoł janek.lilyp...@gmail.com wrote: I was inactive in the last days because i've contracted pneumonia, argh... :-[ I hope to participate a bit in the discussions, but not as much as i'd like to. Oh dear. Get well soon, I hope this won't be too long and will let you enjoy at least a bit of this summer! :) thanks! Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
cherrypicking our way to 2.16
Hey all, Once the most recent critical issues are squashed, are people up for forking off a stable branch from 2.15? Administratively we'd go into cherrypick mode like we did for 2.13 where we institute a moratorium on pushing to the stable branch and have a cherrypick Czar (like Carl was a year-ish ago) port critical bugfixes to this branch. All release candidates would come from this branch. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
More build oddities
Hey all, Running the regtests on a patch set, make check fails: Dissecting... Writing snippets... Processing... Processing /home/mikesol/lilypond-git/build/out/lybook-testdb/snippet-names--1465161827.ly command failed: /home/mikesol/lilypond-git/build/out/bin/lilypond -I /home/mikesol/lilypond-git/input/regression/ -I ./out-test -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/Documentation/snippets -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out-test -dbackend=eps --formats=ps -dseparate-log-files -dinclude-eps-fonts -dgs-load-lily-fonts --header=texidoc -I /home/mikesol/lilypond-git/Documentation/included/ -ddump-profile -dcheck-internal-types -ddump-signatures -danti-alias-factor=1 -I /home/mikesol/lilypond-git/build/out/lybook-testdb -I . -I .. -I /home/mikesol/lilypond-git/build/input/regression -I /home/mikesol/lilypond-git/input/regression/ -I ./out-test -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/Documentation/snippets -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out-test --formats=eps -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir /home/mikesol/lilypond-git/build/out/lybook-testdb/snippet-names--1465161827.ly Child returned 127 Error ignored by lilylib Error trapped by lilypond-book Please see /home/mikesol/lilypond-git/build/out/lybook-testdb/snippet-names--1465161827.log make[2]: *** [out-test/collated-files.texi] Error 1 make[2]: Leaving directory `/home/mikesol/lilypond-git/build/input/regression' make[1]: *** [local-test] Error 2 make[1]: Leaving directory `/home/mikesol/lilypond-git/build/input/regression' make: *** [test] Error 2 What's strange is that the logfile that it sends me to contains the following line: /bin/sh: /home/mikesol/lilypond-git/build/out/bin/lilypond: not found However,I get: mikesol@mikesol-laptop:~/lilypond-git/build$ ls -l /home/mikesol/lilypond-git/build/out/bin/lilypond lrwxrwxrwx 1 root root 23 2012-06-30 23:18 /home/mikesol/lilypond-git/build/out/bin/lilypond - ../../lily/out/lilypond So the symbolic link exists and I'm not sure why it wouldn't be found given that it's an absolute path. Anyone else seeing this? Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: More build oddities
On 30 juin 2012, at 23:48, m...@mikesolomon.org wrote: Hey all, Running the regtests on a patch set, make check fails: Dissecting... Writing snippets... Processing... Processing /home/mikesol/lilypond-git/build/out/lybook-testdb/snippet-names--1465161827.ly command failed: /home/mikesol/lilypond-git/build/out/bin/lilypond -I /home/mikesol/lilypond-git/input/regression/ -I ./out-test -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/Documentation/snippets -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out-test -dbackend=eps --formats=ps -dseparate-log-files -dinclude-eps-fonts -dgs-load-lily-fonts --header=texidoc -I /home/mikesol/lilypond-git/Documentation/included/ -ddump-profile -dcheck-internal-types -ddump-signatures -danti-alias-factor=1 -I /home/mikesol/lilypond-git/build/out/lybook-testdb -I . -I .. -I /home/mikesol/lilypond-git/build/input/regression -I /home/mikesol/lilypond-git/input/regr! ession/ -I ./out-test -I /home/mikesol/lilypond-git/input -I /home/mikesol/lilypond-git/Documentation -I /home/mikesol/lilypond-git/Documentation/snippets -I /home/mikesol/lilypond-git/input/regression/ -I /home/mikesol/lilypond-git/Documentation/included/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/build/mf/out/ -I /home/mikesol/lilypond-git/Documentation/pictures -I /home/mikesol/lilypond-git/build/Documentation/pictures/./out-test --formats=eps -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir /home/mikesol/lilypond-git/build/out/lybook-testdb/snippet-names--1465161827.ly Child returned 127 Error ignored by lilylib Error trapped by lilypond-book Please see /home/mikesol/lilypond-git/build/out/lybook-testdb/snippet-names--1465161827.log make[2]: *** [out-test/collated-files.texi] Error 1 make[2]: Leaving directory `/home/mikesol/lilypond-git/build/input/regression' make[1]: *** [local-test] Error 2 make[1]: Leaving directory `/home/mikesol/lilypond-git/build/input/regression' make: *** [test] Error 2 What's strange is that the logfile that it sends me to contains the following line: /bin/sh: /home/mikesol/lilypond-git/build/out/bin/lilypond: not found However,I get: mikesol@mikesol-laptop:~/lilypond-git/build$ ls -l /home/mikesol/lilypond-git/build/out/bin/lilypond lrwxrwxrwx 1 root root 23 2012-06-30 23:18 /home/mikesol/lilypond-git/build/out/bin/lilypond - ../../lily/out/lilypond So the symbolic link exists and I'm not sure why it wouldn't be found given that it's an absolute path. Anyone else seeing this? Cheers, MS Problem solved (perhaps). I think that make-clean may now remove the binary whereas it used not to. The ../../lily/out/lilypond mentioned above was deleted. Please confirm if someone knows this to be the case. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: cherrypicking our way to 2.16
On Sat, Jun 30, 2012 at 11:41:49PM +0200, m...@mikesolomon.org wrote: Once the most recent critical issues are squashed, are people up for forking off a stable branch from 2.15? Administratively we'd go into cherrypick mode like we did for 2.13 where we institute a moratorium on pushing to the stable branch and have a cherrypick Czar (like Carl was a year-ish ago) port critical bugfixes to this branch. We never did that for 2.13. You're thinking of 2.14, a few months after 2.14.1. I'm against this for a few reasons: - we'd need a volunteer to handle this cherry-picking (but of course your email may prompt somebody to offer) - we still don't have anybody else who has made a release, and I'm already having trouble running GOP (let alone GLISS). - after a potential branch, git master is not going to get regular regression tests (other than Patchy) -- nobody is going to be making releases from it. I still think that the extra burden should be on people wanting to be unstable, not on people wanting to be stable. That is, if somebody knows that they're doing big hacking (spacing changes, rewriting the parser, etc), then they should stick that on a separate branch. One of the big selling points of git is that it makes branching and merging easier. That said, it would be interesting if somebody analyzed all Critical issues from Feb 2012 onwards (after we started Patchy). How many issues were related to code before 2012? How many issues were from new code where people skipped the countdown? and how many issues were from new code but were not found in the countdown? At a completely wild guess, I'd go with 50% pre-2012, 10% skipping, and 40% new code. But I'd really love to have some hard numbers. (and I don't think we can have a meaningful discussion about this until somebody _does_ go and find those hard numbers. ETA 3 hours to find all issues -- note that google issues can give you a spreadsheet, and/or you can make queries via JSON -- and skim the discussion about each issue to find where it was introduced and how it was resolved) - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: cherrypicking our way to 2.16
m...@mikesolomon.org m...@mikesolomon.org writes: Hey all, Once the most recent critical issues are squashed, are people up for forking off a stable branch from 2.15? Administratively we'd go into cherrypick mode like we did for 2.13 where we institute a moratorium on pushing to the stable branch and have a cherrypick Czar (like Carl was a year-ish ago) port critical bugfixes to this branch. All release candidates would come from this branch. That sounds like a good idea, but the typical death of our release candidates was by regressions more than a month old rather than last-minute work done before the release candidate. Our stable branch basically is the last development release. So while this sounds eminently reasonable, it does not seem to significantly help with out current situation. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: cherrypicking our way to 2.16
On Jun 30, 2012, at 10:26 PM, David Kastrup d...@gnu.org wrote: m...@mikesolomon.org m...@mikesolomon.org writes: Hey all, Once the most recent critical issues are squashed, are people up for forking off a stable branch from 2.15? Administratively we'd go into cherrypick mode like we did for 2.13 where we institute a moratorium on pushing to the stable branch and have a cherrypick Czar (like Carl was a year-ish ago) port critical bugfixes to this branch. All release candidates would come from this branch. That sounds like a good idea, but the typical death of our release candidates was by regressions more than a month old rather than last-minute work done before the release candidate. Our stable branch basically is the last development release. The cherry-picking I did was not in order to get 2.14 out, but rather to backport fixes from 2.15 into 2.14.x. At least, iirc. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: More build oddities
m...@apollinemike.com m...@apollinemike.com writes: Problem solved (perhaps). I think that make-clean may now remove the binary whereas it used not to. The ../../lily/out/lilypond mentioned above was deleted. Please confirm if someone knows this to be the case. It definitely should remove the binary, and most likely always did. If there have been any changes (which I rather doubt), it is more likely that make check used to create the binary when absent. But I can't remember any such behavior. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
