Re: 2.21.0 released
Great, thanks! That's very good news, and I'm even more excited about it than stable 2.20 release, as there are many new experimental features, and, even if possibly being especially instable at the beginning, I believe many things will happen in the near future. Looking forward to it Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/Dev-f88644.html
Re: 2.21.0 released
Am Do., 9. Apr. 2020 um 20:33 Uhr schrieb Phil Holmes : > > As it says. > > Many, many thanks to Jonas for helping to make this possible. It took 4 > days for us to collaborate to get a successful release. > > -- > Phil Holmes > Great !!
Re: 2.21.0 released
Dan Eble writes: > On Apr 9, 2020, at 14:42, Valentin Villenave wrote: >> >> Here’s to hoping we can get back on track with our once bi-monthly >> development release cycle! > > Oh, you don't like software development on Biblical timescales? > > At the end of every seven years thou shalt make a release > (Deuteronomy 15:1, KJV). I am not sure whether keeping the commandments against one's intentions is counted to one's credits. It's like burglaring a home that you only later find out was yours to start with. No civil liability, but I am not sure about the criminal one. -- David Kastrup
Re: 2.21.0 released
On Apr 9, 2020, at 14:42, Valentin Villenave wrote: > > Here’s to hoping we can get back on track with our once bi-monthly > development release cycle! Oh, you don't like software development on Biblical timescales? At the end of every seven years thou shalt make a release (Deuteronomy 15:1, KJV). — Dan
Changes document, again (Re: 2.21.0 released)
El 9/4/20 a las 21:43, Francisco Vila escribió: El 9/4/20 a las 20:32, Phil Holmes escribió: Many, many thanks to Jonas for helping to make this possible. It took 4 days for us to collaborate to get a successful release. *ThumbsUp* x2 Speaking of. I was almost determined to give up, but there is no harm in asking, Code for a translated changes document 2.18 -> 2.20 is in git. Any clue about why we still have either a 404 or an empty document from http://lilypond.org/changes.es.html ? Also, there is that ugly b' thing before _some_ links and escaped UTF8 characters showing up in every accented letter in links. Does an issue # exist for this? -- Francisco Vila, Ph.D. - Badajoz (Spain) paconet.org , lilypond.es
Re: update documentation symlinks, and use https in RewriteRules (issue 551650043 by v.villen...@gmail.com)
On 4/9/20, 1:17 PM, "lilypond-devel on behalf of v.villen...@gmail.com" wrote: Reviewers: , Message: This seems trivial enough; may I just push onto staging? Cheers, V It appears that this will fix the current situation, but I worry that the next update will break it (without having any actual knowledge of this "fact"). I think that the https: vs http: fix is a separate fix from the Version fixes. I think the version fixes should have happened with the release process, which I worry we haven't followed: http://lilypond.org/doc/v2.19/Documentation/contributor/minor-release-checklist http://lilypond.org/doc/v2.19/Documentation/contributor/major-release-checklist I'm OK to have you push it, but I'd like to hear from those involved in the release whether or not the steps in the CG were followed. Thanks, Carl
Re[2]: 2.21.0 released
Valentin Villenave wrote 09/04/2020 19:42:39 On 4/9/20, Carl Sorensen wrote: Thank you so much for your dedication! Ditto; Phil, you and James may both have the most thankless and yet crucial jobs in the LilyPond community, so praises to you both! (And obviously to Jonas, David, Han-Wen & al.). Hear, hear to that! Well done to you all! Here’s to hoping we can get back on track with our once bi-monthly development release cycle! +1 Trevor
Re: 2.21.0 released
El 9/4/20 a las 20:32, Phil Holmes escribió: Many, many thanks to Jonas for helping to make this possible. It took 4 days for us to collaborate to get a successful release. *ThumbsUp* x2 -- Francisco Vila, Ph.D. - Badajoz (Spain) paconet.org , lilypond.es
Re: deleting dev/translation-* branches
Am Mittwoch, den 08.04.2020, 09:41 +0200 schrieb David Kastrup: > Jonas Hahnfeld < > hah...@hahnjo.de > > writes: > > > Hi David, > > > > I think these have gone via translation to master, so safe to delete? > > I think so. $ git push origin :dev/translation-merge :dev/translation-picking :dev/translation-picking-merge To ssh://git.sv.gnu.org/srv/git/lilypond.git - [deleted] dev/translation-merge - [deleted] dev/translation-picking - [deleted] dev/translation-picking-merge ... and gone. signature.asc Description: This is a digitally signed message part
Web: update documentation symlinks, and use https in RewriteRules (issue 551650043 by v.villen...@gmail.com)
Reviewers: , Message: This seems trivial enough; may I just push onto staging? Cheers, V. Description: Web: update documentation symlinks, and use https in RewriteRules Please review this at https://codereview.appspot.com/551650043/ Affected files (+4, -4 lines): M Documentation/web/server/lilypond.org.htaccess Index: Documentation/web/server/lilypond.org.htaccess diff --git a/Documentation/web/server/lilypond.org.htaccess b/Documentation/web/server/lilypond.org.htaccess index 480fc3d5a795d21afdeb09e9b4d80860245941f4..5b83bfe5213f3e822e7083802fe9890c08adf36c 100644 --- a/Documentation/web/server/lilypond.org.htaccess +++ b/Documentation/web/server/lilypond.org.htaccess @@ -18,7 +18,7 @@ RewriteEngine On # Permanent redirect from www.lilypond.org to lilypond.org RewriteCond "%{HTTP_HOST}" "^www\.(.+)$" [NC] -RewriteRule "^/?(.*)$" "http://%1/$1"; [R=301,L,NE] +RewriteRule "^/?(.*)$" "https://%1/$1"; [R=301,L,NE] # Deny following of symlinks by robots. # HTTrack is a known offender. @@ -52,8 +52,8 @@ RedirectMatch ^/doc/stable/?$ /manuals RedirectMatch ^/doc/development/?$ /development # Allow to use deep links to latest stable or development docs -RedirectMatch ^/doc//*latest/*(.*)$ /doc/v2.19/$1 -RedirectMatch ^/doc//*development/*(.*)$ /doc/v2.19/$1 +RedirectMatch ^/doc//*latest/*(.*)$ /doc/v2.21/$1 +RedirectMatch ^/doc//*development/*(.*)$ /doc/v2.21/$1 RedirectMatch ^/doc//*stable/*(.*)$ /doc/v2.20/$1 RedirectMatch ^/doc//*([^v].*)$ /doc/v2.20/$1 RedirectMatch ^(/Documentation.*)$ /doc/v2.20$1 @@ -96,7 +96,7 @@ RewriteCond %{REQUEST_URI} !^/website # ...and does not start with /doc$ RewriteCond %{REQUEST_URI} !^/doc$ # ...add trailing slash for [menu] and to avoid /web/ in browser url -RewriteRule ^(.+)$ http://%{HTTP_HOST}/$1/ [R,QSA,L] +RewriteRule ^(.+)$ https://%{HTTP_HOST}/$1/ [R,QSA,L] # Request that does not start with /website RewriteCond %{REQUEST_URI} !^/website
Re: 2.21.0 released
On Thu, Apr 9, 2020 at 1:42 PM Valentin Villenave wrote: > > On 4/9/20, Carl Sorensen wrote: > > Thank you so much for your dedication! > > Ditto; Phil, you and James may both have the most thankless and yet > crucial jobs in the LilyPond community, so praises to you both! (And > obviously to Jonas, David, Han-Wen & al.). > Yay!!
Re: 2.21.0 released
On 4/9/20, Carl Sorensen wrote: > Thank you so much for your dedication! Ditto; Phil, you and James may both have the most thankless and yet crucial jobs in the LilyPond community, so praises to you both! (And obviously to Jonas, David, Han-Wen & al.). Here’s to hoping we can get back on track with our once bi-monthly development release cycle! Cheers, V.
Re: 2.21.0 released
> Thank you so much for your dedication! Hear, hear! Congrats to everyone involved with the new release! Werner
Re: 2.21.0 released
"Phil Holmes" writes: > As it says. > > Many, many thanks to Jonas for helping to make this possible. It took > 4 days for us to collaborate to get a successful release. Considering that the "unstable" release routine was a fortnightly pattern outside of the stable prerelease phase, this will hopefully settle comparatively fast into something more amenable. -- David Kastrup
Re: 2.21.0 released
Phil, Thank you so much for your dedication! Carl On 4/9/20, 12:33 PM, "lilypond-devel on behalf of Phil Holmes" wrote: As it says. Many, many thanks to Jonas for helping to make this possible. It took 4 days for us to collaborate to get a successful release. -- Phil Holmes
2.21.0 released
As it says. Many, many thanks to Jonas for helping to make this possible. It took 4 days for us to collaborate to get a successful release. -- Phil Holmes
Re: PATCHES - Countdown for April 9th
Han-Wen Nienhuys writes: > On Thu, Apr 9, 2020 at 9:36 AM wrote: >> Waiting: >> >> 5874 Remove all uses of markup macro from scm/*.scm - David Kastrup >> https://sourceforge.net/p/testlilyissues/issues/5874 >> http://codereview.appspot.com/575930043 > > why is this "waiting"? It's been LGTM'd a while ago. There are comments on the issue telling the first part of the story. It was waiting for issue 5873 until very recently. The missing story part is that then release 2.21.0 was imminent and I did not see the point in sabotaging the release with pushing large-scale changes that, for example, make it much harder to revert unrelated preceding patches with release-critical problems. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
Re: Refactor get/set_property to take the item as first argument (issue 573670043 by d...@gnu.org)
On 2020/04/09 17:07:46, hanwenn wrote: > I'm curious about these optimizations. Can you say more? Properties are currently stored in alists. They can be stored in vectors instead. Give all grob properties a number, then have an array per grob type mapping this number to an index into an array. The first number can be memoized for literal property names, turning a property lookup into two indexing operations. That's the gist. For Scheme code, the memoization could be replaced by macro compilation, but Guilev2 byte compilation of course is sort of a roadblock here, too. https://codereview.appspot.com/573670043/
Re: output-distance: write HTML as UTF-8 (issue 563810043 by hanw...@gmail.com)
commit 146b73cdd061c264b294f58c6bf7f86667505da5 Author: Han-Wen Nienhuys Date: Fri Apr 3 23:32:38 2020 +0200 https://codereview.appspot.com/563810043/
Re: texinfo-rules: generate log files in $(outdir)/ (issue 557480043 by hanw...@gmail.com)
ommit 6cbb3cb617cf3bc0df882dd68af58cc816e292bc (HEAD -> staging, origin/staging) Author: Han-Wen Nienhuys Date: Sun Feb 23 00:09:39 2020 +0100 texinfo-rules: generate log files in $(outdir)/ https://sourceforge.net/p/testlilyissues/issues/5785 http://codereview.appspot.com/557480043 https://codereview.appspot.com/557480043/
Re: Remove references to test-output-distance.ly. (issue 549780044 by hanw...@gmail.com)
commit f342a35bb1f4ab7c85e13a344a126eece38993fb (test-output-dist) Author: Han-Wen Nienhuys Date: Sun Mar 29 18:52:50 2020 +0200 Remove references to test-output-distance.ly. https://codereview.appspot.com/549780044/
Re: python: fix installation of .py files when building in separate dir (issue 549810043 by hanw...@gmail.com)
commit 2fc91caabe6adb61c89915f659e35f3ec8ba5c62 (py-install) Author: Han-Wen Nienhuys Date: Sun Apr 5 23:07:56 2020 +0200 https://codereview.appspot.com/549810043/
Re: Inline scm stepmake templates (issue 575870044 by hanw...@gmail.com)
commit 5e092ee0d9b84d1948dc90e95488e8c9b58576d1 Author: Han-Wen Nienhuys Date: Sat Mar 21 23:46:14 2020 +0100 Inline scm stepmake templates https://sourceforge.net/p/testlilyissues/issues/5859 http://codereview.appspot.com/575870044 https://codereview.appspot.com/575870044/
Re: Trim unused toplevel targets. (issue 547810069 by hanw...@gmail.com)
commit 0755e2f3dbb99ac256fb447d6ed14d3fe87b8ab5 Author: Han-Wen Nienhuys Date: Sun Mar 22 00:16:36 2020 +0100 Trim unused toplevel targets. https://sourceforge.net/p/testlilyissues/issues/5861 http://codereview.appspot.com/547810069 https://codereview.appspot.com/547810069/
Re: Inline executable-* stepmake templates in lily/GNUmakefile (issue 577690043 by hanw...@gmail.com)
commit 429e0e750be3b772f3e432afa22632981ea8fc1e Author: Han-Wen Nienhuys Date: Tue Mar 17 09:38:06 2020 +0100 Inline executable-* stepmake templates in lily/GNUmakefile https://sourceforge.net/p/testlilyissues/issues/5852 http://codereview.appspot.com/577690043 https://codereview.appspot.com/577690043/
Re: Stop installing TFM and Type1 fonts. (issue 577700043 by hanw...@gmail.com)
Reviewers: lemzwerg, Message: commit 28b894cb8d121eb7f531e193d1736b99fe593edf Author: Han-Wen Nienhuys Date: Sun Mar 15 17:02:16 2020 +0100 Stop installing TFM and Type1 fonts. https://sourceforge.net/p/testlilyissues/issues/5855 http://codereview.appspot.com/577700043 Description: Stop installing TFM and Type1 fonts. Please review this at https://codereview.appspot.com/577700043/ Affected files (+1, -10 lines): M GNUmakefile.in Index: GNUmakefile.in diff --git a/GNUmakefile.in b/GNUmakefile.in index 42b62683302441b1fbcb14a8b0a8433397e86d4d..823e82ea964d93b93842c19b2c99fc7a9b99e05c 100644 --- a/GNUmakefile.in +++ b/GNUmakefile.in @@ -226,10 +226,7 @@ $(tree-share-prefix)/lilypond-force: GNUmakefile $(outdir)/VERSION mkdir -p $(tree-share-prefix)/elisp mkdir -p $(tree-share-prefix)/fonts mkdir -p $(tree-share-prefix)/fonts/otf - mkdir -p $(tree-share-prefix)/fonts/tfm - mkdir -p $(tree-share-prefix)/fonts/type1 mkdir -p $(tree-share-prefix)/fonts/svg - mkdir -p $(tree-share-prefix)/fonts/map mkdir -p $(tree-share-prefix)/fonts/enc mkdir -p $(tree-share-prefix)/tex cd $(tree-bin) && \ @@ -270,9 +267,7 @@ $(tree-share-prefix)/mf-link-tree: $(tree-share-prefix)/lilypond-force rm -f $(tree-share-prefix)/fonts/fonts.conf && \ rm -f $(tree-share-prefix)/fonts/00-lilypond-fonts.conf && \ rm -f $(tree-share-prefix)/fonts/99-lilypond-fonts.conf && \ - rm -f $(tree-share-prefix)/fonts/tfm/* && \ - rm -f $(tree-share-prefix)/fonts/type1/* && \ - cd $(tree-share-prefix)/fonts/otf && \ + cd $(tree-share-prefix)/fonts/otf && \ ln -s ../../../../../../mf/$(outconfbase)/*.otf . && \ $(foreach i,$(addprefix $(TEXGYRE_DIR)/,$(TEXGYRE_FILES)), \ ln -s $i . && ) true && \ @@ -286,10 +281,6 @@ $(tree-share-prefix)/mf-link-tree: $(tree-share-prefix)/lilypond-force ln -s ../../../../../../mf/$(outconfbase)/*.svg . -cd $(tree-share-prefix)/fonts/svg && \ ln -s ../../../../../../mf/$(outconfbase)/*.woff . - -cd $(tree-share-prefix)/fonts/tfm && \ - ln -s ../../../../../../mf/$(outconfbase)/*.tfm . - -cd $(tree-share-prefix)/fonts/type1 && \ - ln -s ../../../../../../mf/$(outconfbase)/*.pf? . touch $(tree-share-prefix)/mf-link-tree TAGS.make: dummy
Re: Inline elisp stepmake templates. (issue 563780044 by hanw...@gmail.com)
Reviewers: lemzwerg, Message: commit 7894ae1dcaffe8f741407e962cf57e4481e93085 Author: Han-Wen Nienhuys Date: Sat Mar 21 23:30:38 2020 +0100 Inline elisp templates. https://sourceforge.net/p/testlilyissues/issues/5857 http://codereview.appspot.com/563780044 Description: Inline elisp stepmake templates. Please review this at https://codereview.appspot.com/563780044/ Affected files (+5, -6 lines): M elisp/GNUmakefile D stepmake/stepmake/elisp-rules.make D stepmake/stepmake/elisp-targets.make D stepmake/stepmake/elisp-vars.make Index: stepmake/stepmake/elisp-rules.make diff --git a/stepmake/stepmake/elisp-rules.make b/stepmake/stepmake/elisp-rules.make deleted file mode 100644 index 1bb8bf6d7fd4c8d09aea89b47de20fb8bbb61626.. --- a/stepmake/stepmake/elisp-rules.make +++ /dev/null @@ -1 +0,0 @@ -# empty Index: stepmake/stepmake/elisp-targets.make diff --git a/stepmake/stepmake/elisp-targets.make b/stepmake/stepmake/elisp-targets.make deleted file mode 100644 index 1bb8bf6d7fd4c8d09aea89b47de20fb8bbb61626.. --- a/stepmake/stepmake/elisp-targets.make +++ /dev/null @@ -1 +0,0 @@ -# empty Index: stepmake/stepmake/elisp-vars.make diff --git a/stepmake/stepmake/elisp-vars.make b/stepmake/stepmake/elisp-vars.make deleted file mode 100644 index 5461eaaa3a8a2b7f6b467efe02511072b6c3aa28.. --- a/stepmake/stepmake/elisp-vars.make +++ /dev/null @@ -1,3 +0,0 @@ - -EL_FILES := $(call src-wildcard,*.el) -SOURCE_FILES += $(EL_FILES) Index: elisp/GNUmakefile diff --git a/elisp/GNUmakefile b/elisp/GNUmakefile index 4ad7f87a5d7de92238a800883cb9aa38a645f335..0e5737e10c79754359f988827b3af4d5904cab59 100644 --- a/elisp/GNUmakefile +++ b/elisp/GNUmakefile @@ -8,10 +8,14 @@ INSTALLATION_FILES=$(EL_FILES) INSTALLATION_OUT_DIR=$(elispdir) INSTALLATION_OUT_FILES=$(outdir)/lilypond-words.el -STEPMAKE_TEMPLATES=elisp install install-out + +STEPMAKE_TEMPLATES= install install-out include $(depth)/make/stepmake.make +EL_FILES := $(call src-wildcard,*.el) +SOURCE_FILES += $(EL_FILES) + LILYPOND_WORDS = $(outdir)/lilypond-words.el LILYPOND_WORDS_DEPENDS =\ $(top-src-dir)/lily/lily-lexer.cc \
Re: Cleanup flower/ makefile (issue 577700045 by hanw...@gmail.com)
Reviewers: lemzwerg, Message: commit 719b9352fd8f3fb0a904ba7cfde402d8352e0eac Author: Han-Wen Nienhuys Date: Sat Mar 21 23:37:34 2020 +0100 Cleanup flower/ makefile Description: Cleanup flower/ makefile * Inline library stepmake template * Inline test stepmake template * Drop unused declarations Please review this at https://codereview.appspot.com/577700045/ Affected files (+34, -26 lines): M flower/GNUmakefile D stepmake/stepmake/library-rules.make D stepmake/stepmake/library-targets.make D stepmake/stepmake/library-vars.make Index: stepmake/stepmake/library-rules.make diff --git a/stepmake/stepmake/library-rules.make b/stepmake/stepmake/library-rules.make deleted file mode 100644 index 62c1da1d85826bc9e414443f85db9f25e499e38a.. --- a/stepmake/stepmake/library-rules.make +++ /dev/null @@ -1,11 +0,0 @@ - -$(O_FILES): $(outdir)/config.hh - -$(LIBRARY): $(O_FILES) - $(call ly_progress,Making,$@,) - $(AR) $(ARFLAGS) $@ $(O_FILES) -# thanks to Nelson Beebe for this trick. - $(RANLIB) $@ || $(AR) ts $@ || true - - - Index: stepmake/stepmake/library-targets.make diff --git a/stepmake/stepmake/library-targets.make b/stepmake/stepmake/library-targets.make deleted file mode 100644 index 61bd8f28c010cb5840c4e2b4ba421caf8fad5675.. --- a/stepmake/stepmake/library-targets.make +++ /dev/null @@ -1,3 +0,0 @@ -default: $(LIBRARY) - -lib: $(LIBRARY) Index: stepmake/stepmake/library-vars.make diff --git a/stepmake/stepmake/library-vars.make b/stepmake/stepmake/library-vars.make deleted file mode 100644 index 7c01002d530a4db8a44313e91f4c30f217542757.. --- a/stepmake/stepmake/library-vars.make +++ /dev/null @@ -1,8 +0,0 @@ -LIB_PREFIX = lib -LIB_SUFFIX = .a - -AR=ar - -# LIBRARY = $(outdir)/$(LIB_PREFIX)$(NAME)$(LIB_SUFFIX) -LIBRARY = $(outdir)/$(LIB_PREFIX)rary$(LIB_SUFFIX) -INSTALL_LIBRARY = $(LIB_PREFIX)$(NAME)$(LIB_SUFFIX) Index: flower/GNUmakefile diff --git a/flower/GNUmakefile b/flower/GNUmakefile index 2b5b304cfa083f3c9be18498f5ee7915ac7e38cb..d93a8488b5ade43a356a2ae0534bef9527d27f8c 100644 --- a/flower/GNUmakefile +++ b/flower/GNUmakefile @@ -1,13 +1,43 @@ depth = .. NAME = flower -MODULE_NAME = flower -README_FILES = NEWS-1.0 NEWS-1.1.46 README TODO -STEPMAKE_TEMPLATES=library c++ po test +STEPMAKE_TEMPLATES= c++ po # test uses LILYPOND_DATADIR LOCALSTEPMAKE_TEMPLATES=lilypond -TEST_MODULE_LIBS = ../flower export top-src-dir + include $(depth)/make/stepmake.make + +TEST_O_FILES := $(filter $(outdir)/test%, $(O_FILES)) +O_FILES := $(filter-out $(outdir)/test%, $(O_FILES)) + +TEST_EXECUTABLE = $(outdir)/test-$(NAME) +TEST_LOADLIBES = $(LIBRARY) $(CXXABI_LIBS) + +# yaffut.hh catches all exceptions, so re-enable -fexceptions for the tests. +$(TEST_O_FILES): EXTRA_CXXFLAGS += -fexceptions + +$(TEST_EXECUTABLE): $(TEST_O_FILES) + $(call ly_progress,Making,$@,) + $(CXX) -o $@ $(TEST_O_FILES) $(TEST_LOADLIBES) $(ALL_LDFLAGS) + +.PHONY: check test + +check: test + +test: $(TEST_EXECUTABLE) + $(TEST_EXECUTABLE) + +AR=ar +LIBRARY = $(outdir)/library.a + +$(O_FILES): $(outdir)/config.hh + +$(LIBRARY): $(O_FILES) + $(call ly_progress,Making,$@,) + $(AR) $(ARFLAGS) $@ $(O_FILES) + $(RANLIB) $@ || $(AR) ts $@ || true + +default: $(LIBRARY)
Re: Refactor get/set_property to take the item as first argument (issue 573670043 by d...@gnu.org)
I'm curious about these optimizations. Can you say more? https://codereview.appspot.com/573670043/
Re: Refactor get/set_property to take the item as first argument (issue 573670043 by d...@gnu.org)
I'm curious about these optimizations. Can you say more? https://codereview.appspot.com/573670043/
Re: PATCHES - Countdown for April 9th
On Thu, Apr 9, 2020 at 9:36 AM wrote: > Waiting: > > 5874 Remove all uses of markup macro from scm/*.scm - David Kastrup > https://sourceforge.net/p/testlilyissues/issues/5874 > http://codereview.appspot.com/575930043 why is this "waiting"? It's been LGTM'd a while ago. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Patchy email
14:41:10 (UTC) Begin LilyPond compile, previous commit at 1dd353f70131eabd43a1b6455d6d05b58fb9db79 14:41:19 Merged staging, now at:1dd353f70131eabd43a1b6455d6d05b58fb9db79 14:41:19Success:./autogen.sh --noconfigure 14:41:33Success:/tmp/lilypond-autobuild/configure --enable-checking 14:41:36Success:nice make clean 14:45:54Success:nice make -j9 CPU_COUNT=9 14:47:18 *** FAILED BUILD *** nice make test -j9 CPU_COUNT=9 Previous good commit: 65932b8fde202a95b7fbf9f400c01c75fa53519f Current broken commit: 1dd353f70131eabd43a1b6455d6d05b58fb9db79 14:47:18 *** FAILED STEP *** merge from staging Failed runner: nice make test -j9 CPU_COUNT=9 See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt 14:47:18 Traceback (most recent call last): File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 528, in handle_staging self.build (issue_id=issue_id) File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 328, in build issue_id) File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 266, in runner raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, this_logfilename)) FailedCommand: Failed runner: nice make test -j9 CPU_COUNT=9 See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt
Push direct to staging
I've pushed a very minor update to staging and release/unstable because a missing version was breaking GUB. Thanks to much help from Jonas, I'm hoping that will be the last road block. -- Phil Holmes
PATCHES - Countdown for April 9th
Hello, Here is the current patch countdown list. The next countdown will be on April 11th A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ *** Push: 5877 Use HTTPS for lilypond.org throughout - Han-Wen Nienhuys https://sourceforge.net/p/testlilyissues/issues/5877 http://codereview.appspot.com/575950043 5876 Regtests cleanup: fix texidoc strings - Valentin Villenave https://sourceforge.net/p/testlilyissues/issues/5876 http://codereview.appspot.com/571950043 5873 Refactor \markup \pattern - David Kastrup https://sourceforge.net/p/testlilyissues/issues/5873 http://codereview.appspot.com/549780045 5785 texinfo-rules: generate log files in $(outdir)/ - Han-Wen Nienhuys https://sourceforge.net/p/testlilyissues/issues/5785 http://codereview.appspot.com/557480043 1204 Documentation and regtests needed for external font files - Valentin Villenave https://sourceforge.net/p/testlilyissues/issues/1204 http://codereview.appspot.com/557640051 Countdown: 5881 Fix line comments for new snippets - David Kastrup https://sourceforge.net/p/testlilyissues/issues/5881 http://codereview.appspot.com/549820043 Review: 5882 Refactor get/set_property to take the item as first argument - David Kastrup https://sourceforge.net/p/testlilyissues/issues/5882 http://codereview.appspot.com/573670043 New: No new patches at this time. Waiting: 5874 Remove all uses of markup macro from scm/*.scm - David Kastrup https://sourceforge.net/p/testlilyissues/issues/5874 http://codereview.appspot.com/575930043 5864 improve Rational infinity initialization - Dan Eble https://sourceforge.net/p/testlilyissues/issues/5864 http://codereview.appspot.com/577710043 5811 mf: use python scripting for generating Emmentaler fonts - Han-Wen Nienhuys https://sourceforge.net/p/testlilyissues/issues/5811 http://codereview.appspot.com/553580043 5771 remove unnecessary (descend-to-context ... 'Score) - Dan Eble https://sourceforge.net/p/testlilyissues/issues/5771 http://codereview.appspot.com/557440043 5740 Add \post to defer context actions to end of time step - Dan Eble https://sourceforge.net/p/testlilyissues/issues/5740 http://codereview.appspot.com/581600043 *** Regards, James