- **Comment**:
Doc: Usage updates done via
https://sourceforge.net/p/testlilyissues/issues/5460/
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Fixed
**Labels:** Fixed_2_19_44 Regression
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Upd
There are several commits for this issue.
But the concerns raised by David in June have not been addressed, right?
Should we change the state from Fixed to Open?
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Fixed
**Labels:** Fixed_2_19_44 Regression
**Cre
- **status**: Accepted --> Fixed
- **Patch**: push -->
- **Comment**:
Just some Tracker housekeeping ...
This looks like
author John Gourlay
Fri, 10 Jun 2016 15:22:41 +0100 (10:22 -0400)
committer John Gourlay
Fri, 10 Jun 2016 15:22:41 +0100 (10:22 -0400)
commit 720
Strictly speaking, this is not blocked since it has already been pushed.
However, I believe this patch requires Python 2.7, and we ship 2.4. As a
result, windows users can no longer use musicxml2ly.
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
*
Phil, does it mean that issue #1079 is blocking this issue?
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
**Labels:** Fixed_2_19_44 Regression
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Wed Jun 22, 2016 11:39 AM UTC
- **labels**: Fixed_2_19_44 --> Fixed_2_19_44, Regression
- **status**: Fixed --> Accepted
- Attachments has changed:
Diff:
--- old
+++ new
@@ -0,0 +1 @@
+02d-Rests-Multimeasure-TimeSignatures.ly (1.2 kB; text/lilypond-source)
- **Comment**:
John,
This causes musicxml2ly to fail bo
- **labels**: --> Fixed_2_19_44
- **status**: Started --> Fixed
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Fixed
**Labels:** Fixed_2_19_44
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Fri Jun 10, 2016 03:25 PM UTC
**Owner
What happened to issue 4781?
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Started
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Thu Jun 09, 2016 07:29 AM UTC
**Owner:** John Gourlay
Import Philomelos enhancements to musicxml2
- **Patch**: countdown --> push
- **Comment**:
Patch counted down - please push.
John if you do not have push access, then send a git formatted patch to me (or
the dev list) and I or someone else can push it for you.
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**S
- **Patch**: review --> countdown
- **Comment**:
Patch on countdown for June 9th.
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Started
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Wed Jun 01, 2016 04:37 PM UTC
**Owner:** Joh
- **Needs**: -->
- **Patch**: new --> review
- **Type**: --> Enhancement
- **Comment**:
Passes make, make check and a full make doc
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Started
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last U
Make additional changes to the new version of musicxml2ly imported
from the Philomelos project. The changes are also uploaded to the
branch dev/johngourlay/issue-4751. After these changes I can run the
following build commands without error:
make
make test-clean
make test
make check
The problems
John,
I'm used to build lilypond following
http://lilypond.org/doc/v2.19/Documentation/contributor/compiling-with-lilydev
If I nuke my build-directory and do all from scratch your branch successfully
builds now.
Though this prevents keeping the test-baseline to run `make check` against, at
least
John,
although your patch is beyond my depth I tried to do some checking. Thus I
checked out your branch. But it failed `make`.
I then reran `sh autogen.sh --noconfigure` on it and `../configure` in \build.
Though it still fails:
[...]
echo /home/hermann/lilypond-git/build/scripts/build/out/
John,
You have to do make, make test-baseline, then apply your patch, then do another
make and them make check.
If you just do make, make test then make check I am not sure what happens.
It depends on where the error happens as to how easy it is to decipher.
Somtimes the name of the file that
- **Patch**: new --> needs_work
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Started
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Sat May 07, 2016 11:40 AM UTC
**Owner:** John Gourlay
Import Philomelos enhancements to music
This passes make but not make check. I cannot fathom why it fails but maybe if
you run the test yourself you can work it out.
See the section:
http://lilypond.org/doc/v2.19/Documentation/contributor-big-page.html#compiling-regression-tests
You don't need to make doc (I'll test that for you when
- **status**: Accepted --> Started
- **Patch**: --> new
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Started
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Fri May 06, 2016 02:15 AM UTC
**Owner:** John Gourlay
Import Philom
The branch dev/johngourlay/issue-4751 should now exist.
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Tue May 03, 2016 05:02 PM UTC
**Owner:** John Gourlay
Import Philomel
Yes, you don't have write access. Either you create a public clone somewhere
so that you can publish your branch, or you ask the lilypond-devel list for
write permission.
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
**Created:** Sun Jan 24, 2016
I tried to create the branch you requested in the lilypond repository but it
didn’t work. I haven’t tried this kind of thing before, so I might be doing
something wrong. Or, maybe I don’t have the rights needed to push anything to
the repository. Do you have any suggestions? Following is my git
Thanks for the patch, but this is very hard to review to its enormous size. I
assume that you got a series of commits, right? Perhaps it is possible to add
this directly to lilypond's git repository as a branch (e.g. into
'origin/dev/johngourlay/issue-4751').
---
** [issues:#4751] Import Ph
Patches are now ready for review:
http://codereview.appspot.com/295120043
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Sun Jan 24, 2016 08:41 PM UTC
**Owner:** John Gourlay
Ahem, where's the patch?
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Sun Jan 24, 2016 08:41 PM UTC
**Owner:** John Gourlay
Import Philomelos enhancements to musicxml2ly
- **status**: New --> Accepted
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** Accepted
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Sun Jan 24, 2016 08:24 PM UTC
**Owner:** John Gourlay
Import Philomelos enhancements to music
---
** [issues:#4751] Import Philomelos enhancements to musicxml2ly**
**Status:** New
**Created:** Sun Jan 24, 2016 02:27 AM UTC by John Gourlay
**Last Updated:** Sun Jan 24, 2016 02:27 AM UTC
**Owner:** John Gourlay
Import Philomelos enhancements to musicxml2ly from
github.com/Philomelos/l
26 matches
Mail list logo
