Hello, Looks like I am (just about) good to go.
--snip-- --------- Forwarded message ---------- From: <pkx1...@gmail.com> Date: 4 March 2012 07:01 Subject: Patchy email To: pkx1...@gmail.com Cc: pkx1...@gmail.com Begin LilyPond compile, commit: acb4ce2a0927ae1899752c991d1c843f5b01196e Merged staging, now at: acb4ce2a0927ae1899752c991d1c843f5b01196e Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j7 CPU_COUNT=7 Success: nice make -j7 CPU_COUNT=7 Success: nice make test -j7 CPU_COUNT=7 Success: nice make doc -j7 CPU_COUNT=7 --snip-- I don't really understand why I still had the same issues as I had before - git would complain about shallow repositories (I did look it up but it didn't shed any light) so I simply rm -rf'ed my lilypond-git and cloned down another one and it all worked fine. oh well. Anyway, I'm back at home this evening and will have a few more test runs (with cron just to make sure I can leave it unattended) and then by Monday I should be running 'lilypond-patchy-staging.py' as often as people want me to. Any specific schedule? James -- -- James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
