Re: Issues to verify

2010-12-15 Thread Phil Holmes
Hi Carl. - Original Message - From: Carl Sorensen c_soren...@byu.edu To: Phil Holmes m...@philholmes.net; lilypond-devel@gnu.org Sent: Tuesday, December 14, 2010 11:53 PM Subject: Re: Issues to verify On 12/14/10 10:26 AM, Phil Holmes m...@philholmes.net wrote: There are

DocBuild fails

2010-12-15 Thread Jonathan Kulp
Doc build is failing since yesterday evening for me. It built in w/o errors in the morning. I've committed new code locally to the CG but I don't think that's the problem. Here's the part of the log that has errors near the end: Converting to PNG...[././62/lily-b9a00701.eps] GPL Ghostscript 8.71

Re: lilybuntu 2

2010-12-15 Thread Jonathan Kulp
On Tue, Dec 14, 2010 at 6:32 AM, Jonathan Kulp jonlancek...@gmail.com wrote: On Mon, Dec 13, 2010 at 9:14 PM, Jonathan Kulp jonlancek...@gmail.com wrote: since most will use it in a VM.  Now I'm running make all and make doc to test it before sharing. Incidentally I'd hate to have to build the

issue classification: priority guidelines

2010-12-15 Thread Janek Warchoł
Hi, I've read Issue classification and i think it would be good to add one more guideline concerning priority: i believe that the priority should depend on how widespread the issue is. Even minor problems concernning some basic elements (that will probably happen many times in even a single

Re: issue classification: priority guidelines

2010-12-15 Thread Dmytro O. Redchuk
On Wed 15 Dec 2010, 12:53 Janek Warchoł wrote: Hi, Hi! I've read Issue classification and i think it would be good to add one more guideline concerning priority: i believe that the priority should depend on how widespread the issue is. Even minor problems concernning some basic elements

Re: issue classification: priority guidelines

2010-12-15 Thread Phil Holmes
- Original Message - From: Janek Warchoł lemniskata.bernoull...@gmail.com To: lilypond-devel lilypond-devel@gnu.org Sent: Wednesday, December 15, 2010 11:53 AM Subject: issue classification: priority guidelines Hi, I've read Issue classification and i think it would be good to add

Re: DocBuild fails

2010-12-15 Thread James
Jonathan, On 15/12/2010 10:35, Jonathan Kulp wrote: Doc build is failing since yesterday evening for me. It built in w/o errors in the morning. I've built my doc with no issues, but it depends on what you call 'yesterday evening'. What is the last commit you have in your source (apart from

Re: DocBuild fails

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 6:40 AM, James james.l...@datacore.com wrote: Doc build is failing since yesterday evening for me. It built in w/o errors in the morning. I've built my doc with no issues, but it depends on what you call 'yesterday evening'. What is the last commit you have in your

Re: sorry about the missing regtests

2010-12-15 Thread Carl Sorensen
On 12/15/10 12:28 AM, Marc Hohl m...@hohlart.de wrote: Am 15.12.2010 00:18, schrieb Carl Sorensen: On 12/14/10 4:15 PM, Graham Percivalgra...@percival-music.ca wrote: I only just realized that I should have done git add input/regression/*.ly after apply Neil's patches with patch

Re: DocBuild fails

2010-12-15 Thread James
Jonathan On 15/12/2010 13:19, Jonathan Kulp wrote: On Wed, Dec 15, 2010 at 6:40 AM, Jamesjames.l...@datacore.com wrote: Doc build is failing since yesterday evening for me. It built in w/o errors in the morning. I've built my doc with no issues, but it depends on what you call 'yesterday

Re: DocBuild fails

2010-12-15 Thread Carl Sorensen
On 12/15/10 6:42 AM, James james.l...@datacore.com wrote: Jonathan On 15/12/2010 13:19, Jonathan Kulp wrote: On Wed, Dec 15, 2010 at 6:40 AM, Jamesjames.l...@datacore.com wrote: Doc build is failing since yesterday evening for me. It built in w/o errors in the morning. I've built my

Re: dynamic alignment

2010-12-15 Thread Marek Klein
Hi Jan-Peter, 2010/12/13 Jan-Peter Voigt jp.vo...@gmx.de Hello list, I wrote a script to align dynamics centered on the corresponding note: --snip-- \version 2.12.3 % calculate x-alignment based on attribute text + dynamic text #(define-markup-command (center-dyn layout props atr-text

Re: lilybuntu 2

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 12:11 PM, Jonathan Kulp jonlancek...@gmail.com wrote: The new .iso file is ready. You can brows for it at this address: http://files.lilynet.net/ or download directly using this one: http://files.lilynet.net/lilybuntu2.iso http://files.lilynet.net/lilybuntu2.iso.md5

Re: issue classification: priority guidelines

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 12:31:02PM -, Phil Holmes wrote: - Original Message - From: Janek Warchoł I've read Issue classification and i think it would be good to add one more guideline concerning priority: i believe that the priority should depend on how widespread the issue is.

Re: lilybuntu 2

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 05:11:46AM -0600, Jonathan Kulp wrote: The new .iso file is ready. You can brows for it at this address: Great! If you want to test it, please feel free. Note that the lily-git.tcl script is already in the user's home directory, ready to grab the source code.

Re: issue classification: priority guidelines

2010-12-15 Thread Valentin Villenave
2010/12/15 Graham Percival gra...@percival-music.ca: In the mean time, go ahead and twiddle the definitions of priorities (as long as you leave Critical alone).  But be aware that you're rearranging deck chairs on the titanic. ROTFL -- my point exactly :-) Cheers, V.

Re: lilybuntu 2

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 8:41 AM, Valentin Villenave valen...@villenave.net wrote: I've added a bitTorrent tracker and server as well: http://torrents.lilynet.net Cheers, Valentin. Excellent! Thanks Valentin. I'm set up to be a seeder. Jon -- Jonathan Kulp http://www.jonathankulp.com

Re: issue classification: priority guidelines

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 1:31 PM, Phil Holmes m...@philholmes.net wrote: * Priority-High: An issue which produces output which does not accurately reflect the input (e.g where the user would expect an accidental, but none is shown) or which produces aesthetically poor output in a situation which

Re: issue classification: priority guidelines

2010-12-15 Thread Phil Holmes
What I'm trying to do is document a categorisation that makes the job of the bug squad easier. Unless anyone says no, I'll ask for the changes proposed to be made. -- Phil Holmes - Original Message - From: Valentin Villenave valen...@villenave.net To: Graham Percival

Regtests for 13.43

2010-12-15 Thread Phil Holmes
No significant changes that I can see, except the missing initial bar in the skipTypesetting tests, which is expected new behaviour. I'll run my checker when I'm not otherwise using the PC. -- Phil Holmes Bug Squad ___ lilypond-devel mailing

Re: issue classification: priority guidelines

2010-12-15 Thread Janek Warchoł
2010/12/15 Graham Percival gra...@percival-music.ca Look, the ugly truth is that the priority field -- other than critical -- has no effect on lilypond development.  I've been heavily involved since 2003 (before this issue tracker in 2006), and that's my observation.  It has no statistically

Re: lilybuntu 2

2010-12-15 Thread James
hello, On 15/12/2010 14:58, Graham Percival wrote: With that in mind, could James (continue) to test it, making sure that he looks at the docs in current git rather than relying on his own knowledge? The iso is now downloaded. I'll look at the CG in Git (once I can compile the docs again :)

Re: lilybuntu 2

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 3:48 PM, James james.l...@datacore.com wrote: Or I can use the CG on the website which seems to be Development for LilyPond 2.13.43 Actually, that's fine for you. Nothing has changed since .43 yet. I'm halfway done downloading it, and I'll make small tweaks as I go

Re: Regtests for 13.43

2010-12-15 Thread Phil Holmes
Phil Holmes m...@philholmes.net wrote in message news:iealqb$3k...@dough.gmane.org... No significant changes that I can see, except the missing initial bar in the skipTypesetting tests, which is expected new behaviour. I'll run my checker when I'm not otherwise using the PC. -- Phil Holmes

Re: issue classification: priority guidelines

2010-12-15 Thread Graham Percival
2010/12/15 Janek Warchoł lemniskata.bernoull...@gmail.com: Ok, this means i have to fix some (lots of?) stuff myself (you got me hooked perhaps, however i don't know how all this will turn out)... Yes. The following is for anyone interested in helping me in this task. I have some basic

Re: issue classification: priority guidelines

2010-12-15 Thread James
Janek On 15/12/2010 15:32, Janek Warchoł wrote: but i struggle with unbelieveably low VirtualBox resolution - 800x600, it annoys me extremely on my big monitor. Maybe i'll find an answer on the web Look in the help. 9.6. Advanced display configuration James

Re: issue classification: priority guidelines

2010-12-15 Thread Carl Sorensen
On 12/15/10 8:32 AM, Janek Warchoł lemniskata.bernoull...@gmail.com wrote: 2010/12/15 Graham Percival gra...@percival-music.ca  Fighting about whether a bug should be high vs. low does NOTHING to get it fixed sooner or later.  This is a volunteer project, and lilypond developers do not appear

keep git master clean

2010-12-15 Thread Graham Percival
We have a lot of newbie contributors now. That's great! However, newbie contributors aren't confident, and aren't able to figure out why the build is failing. Especially when they're trying to build lilypond for the first time, and automatically assume that if git master can't build it's their

next few weeks of development

2010-12-15 Thread Graham Percival
We have one Critical issue remanining: http://code.google.com/p/lilypond/issues/detail?id=1290 I'm estimating a 4-line patch to one file. Once such a patch has been pushed, I'm branching off stable/2.14, releasing the first release candidate, and starting the two-week timer. During that period,

Re: lilybuntu 2

2010-12-15 Thread James
hello, On 14/12/2010 03:14, Jonathan Kulp wrote: I made a new .iso with fontforge 20100501 built from source, as well as dblatex. ./autogen.sh now runs with no warnings or errors. Yes I can confirm this too. Am starting a make ; make doc now. Now if we could configure LilyGit.tcl to have

Re: keep git master clean

2010-12-15 Thread Carl Sorensen
On 12/15/10 10:19 AM, Graham Percival gra...@percival-music.ca wrote: We have a lot of newbie contributors now. That's great! However, newbie contributors aren't confident, and aren't able to figure out why the build is failing. Especially when they're trying to build lilypond for the

Re: Regtests for 13.43

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 5:17 PM, Phil Holmes m...@philholmes.net wrote: Only significant changes shown with my comparator are the skipTypesetting tests.  Not only have we lost the bat mark, but the tests are somewhat further left and lower.  See attached image as an example. Nooo! I can't

Re: keep git master clean

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 10:34:59AM -0700, Carl Sorensen wrote: We've got to have some better process to handle this. Agreed. I don't know what it is. For a symptomatic treatment, this particular case could be checked with make test instead of make doc. That'd be 5-10 minutes instead of an

Re: keep git master clean

2010-12-15 Thread Ralf Wildenhues
delurking for a moment ... * Carl Sorensen wrote on Wed, Dec 15, 2010 at 06:34:59PM CET: In order to be sure a one-line patch doesn't break the build, we need to to make doc-clean make doc, That simply means that there is a bug in the build system, in that it doesn't track all dependencies.

Re: keep git master clean

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 6:34 PM, Carl Sorensen c_soren...@byu.edu wrote: We've got to have some better process to handle this.  I don't know what it is.  Maybe a correct build system, so we don't need to do make doc-clean to ensure things aren't broken.  Maybe an english-only make doc, so we

Re: keep git master clean

2010-12-15 Thread Ralf Wildenhues
* Graham Percival wrote on Wed, Dec 15, 2010 at 07:14:37PM CET: On Wed, Dec 15, 2010 at 6:09 PM, Ralf Wildenhues wrote: * Carl Sorensen wrote on Wed, Dec 15, 2010 at 06:34:59PM CET: In order to be sure a one-line patch doesn't break the build, we need to to make doc-clean make doc,

Re: keep git master clean

2010-12-15 Thread Carl Sorensen
On 12/15/10 10:34 AM, Carl Sorensen c_soren...@byu.edu wrote: On 12/15/10 10:19 AM, Graham Percival gra...@percival-music.ca wrote: Carl: I killed your 713aeac92c2bd06a9ae0ed38d13f4b20fba3f9a8 which was the regtest for 1440. Dunno why it was failing; building it from the command-line

Re: keep git master clean

2010-12-15 Thread Carl Sorensen
On 12/15/10 10:57 AM, Graham Percival gra...@percival-music.ca wrote: On Wed, Dec 15, 2010 at 10:34:59AM -0700, Carl Sorensen wrote: We've got to have some better process to handle this. Agreed. I don't know what it is. For a symptomatic treatment, this particular case could be checked

Re: next few weeks of development

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 11:24 AM, Graham Percival gra...@percival-music.ca wrote: Despite the excitement about 2.14, I'm going to be working on lilybuntu and the early CG chapters since we've had a surge of new contributors.  I won't be working on a patch for 1290, but rest Just a reminder

Re: lilybuntu 2

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 11:50 AM, James james.l...@datacore.com wrote: Now if we could configure LilyGit.tcl to have another button to 'compile (doc) for the first time' It could run ./autogen.sh and then make ; make doc. I rarely make install personally. But thanks again Jonathan! No

Re: lilybuntu 2

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 7:40 PM, Jonathan Kulp jonlancek...@gmail.com wrote: I'm working on a slight improvement right now. I've made a desktop launcher for lily-git.tcl and I want to see if I can make it appear on the user's desktop by default instead of in the home directory. Trying to make

Re: next few weeks of development

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 6:24 PM, Graham Percival gra...@percival-music.ca wrote: You might feel an urge to rush to push stuff onto master right now to get it in before 2.14.0.  Don't.  There will be plenty of other releases.  We have way too much new stuff in 2.14.0 as it is.  The world will

Re: next few weeks of development

2010-12-15 Thread Carl Sorensen
On 12/15/10 12:15 PM, Jonathan Kulp jonlancek...@gmail.com wrote: On Wed, Dec 15, 2010 at 11:24 AM, Graham Percival gra...@percival-music.ca wrote: Despite the excitement about 2.14, I'm going to be working on lilybuntu and the early CG chapters since we've had a surge of new

Re: lilybuntu 2

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 1:46 PM, Graham Percival gra...@percival-music.ca wrote: On Wed, Dec 15, 2010 at 7:40 PM, Jonathan Kulp jonlancek...@gmail.com wrote: I'm working on a slight improvement right now. I've made a desktop launcher for lily-git.tcl and I want to see if I can make it appear on

Re: next few weeks of development

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 1:56 PM, Carl Sorensen c_soren...@byu.edu wrote: Just a reminder that I've prepared an addition to CG with steps to creation of lilybuntu and am only waiting to test doc-build after Carl's regtest is sorted. Graham's reversion solved the doc-build problem. I'm

Re: next few weeks of development

2010-12-15 Thread Carl Sorensen
On 12/15/10 1:24 PM, Jonathan Kulp jonlancek...@gmail.com wrote: On Wed, Dec 15, 2010 at 1:56 PM, Carl Sorensen c_soren...@byu.edu wrote: Just a reminder that I've prepared an addition to CG with steps to creation of lilybuntu and am only waiting to test doc-build after Carl's regtest is

Re: next few weeks of development

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 08:56:15PM +0100, Valentin Villenave wrote: However there's a bunch of patches that have been sitting there for a while: off the top of my head, I really hope you just did a label:patch search in the issue tracker to find that liast. Do we really want to ship a new

Re: next few weeks of development

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 02:24:15PM -0600, Jonathan Kulp wrote: Thanks Carl, I'm in the middle of a make-doc after doing exactly as you said. Assuming it compiles without errors, do I do: you read the lily-git.tcl section in the CG. git push origin or is it something else? ... if you

Re: next few weeks of development

2010-12-15 Thread Jonathan Kulp
On Wed, Dec 15, 2010 at 2:35 PM, Graham Percival gra...@percival-music.ca wrote: ... if you have git push access (which I think you do), and if you haven't changed anything since last year, then yes. Got it. Pushed. Thanks guys, Jon -- Jonathan Kulp http://www.jonathankulp.com

Re: next few weeks of development

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 9:33 PM, Graham Percival gra...@percival-music.ca wrote: I really hope you just did a  label:patch search in the issue tracker to find that liast. Nope. Some of these are untracked. Yes.  Because the VERY FIRST gop policy debate is about how we deal with patches. Do

Re: next few weeks of development

2010-12-15 Thread Carl Sorensen
On 12/15/10 12:56 PM, Valentin Villenave valen...@villenave.net wrote: ... and that's but what I could come up with with a quick search on Rietveld. How did you do your search on Rietveld? I've never been able to find a decent method to search Rietveld. Thanks, Carl

Re: sorry about the missing regtests

2010-12-15 Thread Neil Puttock
On 14 December 2010 23:18, Carl Sorensen c_soren...@byu.edu wrote: On 12/14/10 4:15 PM, Graham Percival gra...@percival-music.ca wrote: I only just realized that I should have done   git add input/regression/*.ly after apply Neil's patches with patch -p1 foo.diff Sorry about that.

Re: next few weeks of development

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 10:25 PM, Carl Sorensen c_soren...@byu.edu wrote: How did you do your search on Rietveld?  I've never been able to find a decent method to search Rietveld. There isn't. All I could do was to browse the user's pages for a few known associates of the LilyPond project: e.g.