Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Status: Accepted Owner: Labels: Type-Documentation New issue 2346 by colingh...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Thomas Morley suggested a documentation improvement here: http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg00982.html http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/33878 Original posting follows: Hi, In Contributor Guide 7.7 Updating LSR to a new version, below the paragraph: " To update LSR, perform the following steps: 1.Download the latest snippet tarball, extract it, and run convert-ly on all files using the command-line option ‘--to=version’ to ensure snippets are updated to the correct stable version. " please add: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Example:LSR-version: 2.12.2 intended LSR-update to 2.14.2 latest release 2.15.30 Use convert-ly from 2.15.30 and the following terminal command for all files: convert-ly -e -t2.14.2 *.ly Regards, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: Patch-new Comment #1 on issue 2346 by janek.li...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346#c1 CG: Use latest convert-ly for LSR updates (fix 2346) Suggested by Thomas Morley: Use convert-ly from latest development release for LSR updates http://codereview.appspot.com/5696069 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: Patch-review Comment #3 on issue 2346 by julien.r...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346#c3 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: Patch-needs_work Comment #4 on issue 2346 by julien.r...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346#c4 Patchy the autobot says: Failed runner: nice make -j2 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: -Patch-needs_work Patch-review Comment #5 on issue 2346 by julien.r...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Sorry, wrong issue number on the previous comment. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: -Patch-countdown Patch-push Comment #7 on issue 2346 by colinpkc...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Counted down to 20120228, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_31 Comment #8 on issue 2346 by janek.li...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 pushed as 2411d0e11c5ca03997122c905bc2e58ea6a8682e ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #9 on issue 2346 by colingh...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 I don't think this patch made it into 2.15.31. The commit is in the repo but I had a look at the web site and there's no sign of the text about using the latest convert-ly in the CG here: http://lilypond.org/doc/v2.15/Documentation/contributor/updating-lsr-to-a-new-version Not verified. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: -Fixed_2_15_31 Fixed_2_15_32 Comment #10 on issue 2346 by d...@gnu.org: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 git log origin --decorate --graph shows the following: * commit 55d9ad39acee4288ee0d36230f70110b02546ab3 | Author: Graham Percival | Date: Wed Feb 29 15:59:44 2012 + | | Release: bump version. | * commit 4493eb4584f92123ebacf51541ace8c0e20f5e5a |\ Merge: 2411d0e ea270d9 | | Author: Graham Percival | | Date: Wed Feb 29 15:59:33 2012 + | | | | Merge branch 'release/unstable' into HEAD | | | * commit ea270d91e363a855827930c7b5b71a105aed922a (tag: release/2.15.31-1, ori | | Author: Graham Percival | | Date: Wed Feb 29 12:09:32 2012 + | | | | Release: update news. | | * | commit 2411d0e11c5ca03997122c905bc2e58ea6a8682e |/ Author: Janek Warchoł | Date: Sat Feb 25 08:11:10 2012 +0100 | | CG: Use latest convert-ly for LSR updates (fix 2346) | | Suggested by Thomas Morley: | Use convert-ly from latest development release for LSR updates | * commit c8be1e28e0dab3c7707242336d76350c2f2f19eb (test-staging, ledger) So this fix missed the release branch and has not made it into 2.15.31 even though it is in current master. This small time window is the rare exception where git show 2411d0e11c5ca03997122c905bc2e58ea6a8682e:VERSION displays an inaccurate result: it is after the branch of the release, but before the bump in VERSION happened. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #11 on issue 2346 by colingh...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 My mistake builds/lilypond-git$ builds/lilypond-git$ git checkout release/2.15.31-1 HEAD is now at ea270d9... Release: update news. builds/lilypond-git$ git log origin --pretty=oneline | grep 2411d0e11c5ca03997122c905bc2e58ea6a8682e 2411d0e11c5ca03997122c905bc2e58ea6a8682e CG: Use latest convert-ly for LSR updates (fix 2346) builds/lilypond-git$ git log --pretty=oneline | grep 2411d0e11c5ca03997122c905bc2e58ea6a8682e builds/lilypond-git$ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #12 on issue 2346 by janek.li...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Umm, sorry, i don't get it - can i help in any way, as the pusher of the change? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #13 on issue 2346 by pkx1...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 I think what is being said here is that it *is* in the tree but missed the window of opportunity to be in 2.15.31-1 but will be in 2.15.31-2 (or whatever the next version is). is that correct? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #14 on issue 2346 by d...@gnu.org: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 2.15.32-1 will very likely be next, and there is nothing to be done with this issue (I corrected the tag when I posted my explanation) until 2.15.32 gets released. After that, the issue needs to be verified. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Status: Verified Comment #15 on issue 2346 by elu...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #16 on issue 2346 by janek.li...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Thanks, David, James, Colin and Eluze! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Status: Fixed Comment #17 on issue 2346 by philehol...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Reverted to fixed, since this needs reverifying by checking the source as pulled from git, not just the commitish. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Status: Verified Comment #18 on issue 2346 by elu...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
