Re: somebody needs to run staging before 29 Jan
Hello, On 24 January 2012 22:20, David Kastrup d...@gnu.org wrote: Janek Warchoł janek.lilyp...@gmail.com writes: Keeping the staging-merge going would be about five people committing to 50€ a month. That is, of course, not enough for me to live on. It merely means that taking on this duty will not further reduce the amount of time I can spend on LilyPond in total. That would be a waste of your skills. The skills will eventually become unavailable anyway if nobody pays for either major or minor variants of them, so that should be the smallest worry. I have not offered to do it for free, anyway. If the time I spend on that is paid for, it is no loss to anybody. I don't have a 24/7 computer, Neither is a laptop, but I'd still get some stuff done. but if no one else will volunteer i can run Patchy (the skills necessary are quite like mine). I only need to pass my exams - 9 days left till i have lots of time to investigate and improve Patchy (with Julien's help). I have a machine that I can keep running 24/7 (well I have electricity 24/7, Internet connection probably about 20/7) and have already offered (and been trying) to run patchy but with limited success this week. I haven't bothered Graham as he is on limited time now, which can be better spent I am sure that walking me through python scripts. However when I run patchy I am getting --snip-- james@jameslilydev2:~/Desktop/patchy$ ./run-lilypond-staging.sh remote: Counting objects: 83, done. remote: Compressing objects: 100% (57/57), done. remote: Total 57 (delta 45), reused 0 (delta 0) Unpacking objects: 100% (57/57), done. From ssh://git.sv.gnu.org/srv/git/lilypond 39f5057..5a61803 master - origin/master ad3a9e6..8019ff7 staging- origin/staging From ssh://git.sv.gnu.org/srv/git/lilypond * [new tag] release/2.15.27-1 - release/2.15.27-1 Branch test-master-lock set up to track remote branch master from origin. Branch test-staging set up to track remote branch staging from origin. Initialized empty Git repository in /home/james/Desktop/patchy/lilypond-autobuild/.git/ fatal: attempt to fetch/clone from a shallow repository fatal: The remote end hung up unexpectedly Begin LilyPond compile, commit: 39f50579ff91fdca06acd52a9392ab2874f4723b etc etc. --- and I don't know where I need to look from here. Bear in mind this is on my lilydev machine where I can manually download/git pull/push etc. So I know it is getting the code but not sure what the other message means because it is coming from git (I cannot find the 'fatal' strings in any of the .py files). I'm struggling to find time between my coffee and cornflakes as well as doing doc patches, so if someone can shed any light or point me somewhere I can move on with Patchy. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: somebody needs to run staging before 29 Jan
On Wed, Jan 25, 2012 at 09:10:16AM +, James wrote: Initialized empty Git repository in /home/james/Desktop/patchy/lilypond-autobuild/.git/ fatal: attempt to fetch/clone from a shallow repository fatal: The remote end hung up unexpectedly It wants to have a full git clone git://git.sv.gnu.org/lilypond.git command, as (now) specified in the CG and done in the updated lily-git.tcl. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: somebody needs to run staging before 29 Jan
James pkx1...@gmail.com writes: However when I run patchy I am getting --snip-- james@jameslilydev2:~/Desktop/patchy$ ./run-lilypond-staging.sh remote: Counting objects: 83, done. remote: Compressing objects: 100% (57/57), done. remote: Total 57 (delta 45), reused 0 (delta 0) Unpacking objects: 100% (57/57), done. From ssh://git.sv.gnu.org/srv/git/lilypond 39f5057..5a61803 master - origin/master ad3a9e6..8019ff7 staging- origin/staging From ssh://git.sv.gnu.org/srv/git/lilypond * [new tag] release/2.15.27-1 - release/2.15.27-1 Branch test-master-lock set up to track remote branch master from origin. Branch test-staging set up to track remote branch staging from origin. Initialized empty Git repository in /home/james/Desktop/patchy/lilypond-autobuild/.git/ fatal: attempt to fetch/clone from a shallow repository fatal: The remote end hung up unexpectedly A shallow repository? That's a git problem, not a Python problem. I would have to look that up. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
make doc: 'Command token too long' error
Hello. This error did not break the build process and I don't know exactly what consequences it has. While make doc: ... cd ./out-www; texi2pdf -I ./out-www -I /home/fravd/source/lilypond/Documentation/out -I /home/fravd/source/lilypond/Documentation -I /home/fravd/source/lilypond/Documentation --quiet snippets.texi Error (196): Command token too long Error (196): Command token too long Error (196): Command token too long Error (196): Command token too long /home/fravd/source/lilypond/scripts/build/out/texi2omf --format pdf --location /usr/local/share/doc/lilypond/html/Documentation/usage.pdf --version 2.15.28 usage.tely out-www/usage.pdf.omf cd ./out-www; texi2pdf -I ./out-www -I /home/fravd/source/lilypond/Documentation/out -I /home/fravd/source/lilypond/Documentation -I /home/fravd/source/lilypond/Documentation --quiet usage.texi ... HEAD is 8be61c2 in the lilypond/translation branch. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
Moving to devel: I think this bounty slush fund needs to happen soon-ish - there's been two rounds of talking about it, which is great, but it will remain talk unless someone does something. I also understand that David is in the position of not wanting to do a full court press for organizing the €€ thing because he wants to be earning some of it, which I respect. So I am going to do something - if people have a problem with it, then speak up, but I'm throwing this out there as a solution. 1) Create an e-mail address contrib...@lilypond.org (this I can't do - can someone please do this). 2) Create a PayPal account for said address with one and only one person, the € czar, who has access to it. This should be someone responsible and respectable . In my life, I have drank, lied and listened to a lot of ABBA, so I am out, but there are several people on the list who seem like upstanding individuals who could fill this role. 3) Propositions come in on the devel list from developers in the form of I have project X and I would like Y€ from the slush fund to do it. This will then go up for a private vote (like patch review) where anyone who has git push access can send a vote email to the € czar. If there are more yeas than nays, the person gets the € for doing thing X (in advance of doing it - it'll be a trust system). The € czar has the final say over whether or not to approve the project in order to prevent abuse, and the € czar needs to agree to not be allowed to tap into this fund, lest she give up her role as € czar. Seems simple, effective, and startable in the next two weeks. I'm sure it is not perfect, but LilyPond is not perfect, and it seems better to start something and change it as need be than to not do anything. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, Jan 25, 2012 at 03:01:50AM -0800, m...@apollinemike.com wrote: 1) Create an e-mail address contrib...@lilypond.org (this I can't do - can someone please do this). Can't do. Seems simple, effective, and startable in the next two weeks. I'm sure it is not perfect, but LilyPond is not perfect, and it seems better to start something and change it as need be than to not do anything. Check your email archives for our discussion on 2011 Dec 2 for all the reasons I think this is a bad idea. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, 25 Jan 2012 11:24:40 +, Graham Percival wrote: On Wed, Jan 25, 2012 at 03:01:50AM -0800, m...@apollinemike.com wrote: 1) Create an e-mail address contrib...@lilypond.org (this I can't do - can someone please do this). Can't do. Seems simple, effective, and startable in the next two weeks. I'm sure it is not perfect, but LilyPond is not perfect, and it seems better to start something and change it as need be than to not do anything. Check your email archives for our discussion on 2011 Dec 2 for all the reasons I think this is a bad idea. - Graham Given that several users have already expressed the desire to give money this way and at least one developer has expressed the desire to take money this way, it seems that the only thing missing is the clearinghouse through which the exchange happens. I'll propose a patch in a bit that does this: I think the best way to decide as a community if we want this is to read over a patch, see if we like it, and then either put it on a countdown or not. In the meantime, I think people should take a gander at: http://audacity.sourceforge.net/?lang=fr http://ardour.org/ http://musescore.org/fr They're all music related projects that have a donation system implemented. Especially with MuseScore, we could just ask them how if it has proven to be effective for them. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, Jan 25, 2012 at 03:38:21AM -0800, m...@apollinemike.com wrote: On Wed, 25 Jan 2012 11:24:40 +, Graham Percival wrote: Check your email archives for our discussion on 2011 Dec 2 for all the reasons I think this is a bad idea. Given that several users have already expressed the desire to give money this way and at least one developer has expressed the desire to take money this way, it seems that the only thing missing is the clearinghouse through which the exchange happens. You have not refuted /any/ of the concerns I gave against this idea in that previous email. I think we need to discuss this privately. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
2012/1/25 Graham Percival gra...@percival-music.ca: Check your email archives for our discussion on 2011 Dec 2 for all the reasons I think this is a bad idea. Sorry, but i'm searching for 10 minutes and haven't found relevant thread. Can you be more specific? Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
Werner LEMBERG w...@gnu.org writes: Nice suggestions, Mike! 2) Create a PayPal account for said address with one and only one person, the € czar, who has access to it. This should be someone responsible and respectable. Hmm. This actually means that PayPal is involved two times, stripping of 2x3% or more... What about having two persons, one for US, and one for Europe so that a normal bank transfer can be done? No idea whether this is better, however. Can someone do a survey how other free software projects handle this? We could also set up a Pledgie campaign, however, this also cuts off 3% (or more) of the money. 97% of something is more than 100% of nothing. I do share Graham's concerns which have been previously hashed out in private discussions: an official money channel for LilyPond is not something easy to set up. In the meantime, I have actually received a request for my bank account data from one user and one developer just right now, so there is some support that can be rallied. However, it seems sort of absurd if an active and dedicated developer pays another developer for staying active and dedicated. So while the developer base is certainly a place where one _does_ find dedicated LilyPond friends, in the long run I need to shift the financial responsibility to dedicated LilyPond friends among the end users who find that money is by far the best resource they can contribute for keeping up their end of the project. So while at the moment I can provide one money sink that makes, in my not at all humble opinion, a good place to turn money into LilyPond progress, it does not mean that it is the only one (after all, I am working only on some parts of LilyPond), nor does it mean that this will stay so in perpetuity. And while currently the danger of acquiring a noticeable _buffer_ does not really seem imminent, I would want to avoid the situation where I have money on my hand I can't spend in good conscience. So I would attempt of using the next LilyPond report for fishing for _personal_ LilyPond funds, trying to present the results of the previous discussions about official channels and see what the responses in turns of better ideas as well as actual donations are. Once we get in the situation where I would tell prospective _personal_ _account_ donators that I already got myself covered, or where we find that people are willing to provide money for LilyPond developments that someone else would be better suited to take up, we might have to rethink about putting something up that is less personal than currently you can support some LilyPond developments by supporting David. I also would find it nice if we have, say, a developer saying that he wants to hold a talk at some conference but it would unduly strain his personal budget to do so, to be able to connect him to users willing to sponsor such work. Basically have a place where software users and money users can meet. But at the current point I don't see that we can reasonably set up a _fund_ where the in- and outflow of money are dealt with in separation. While it is a strength of the abstraction money, it requires additional administration and legal infrastructure. We are too small yet for that to make much sense, I think. I should certainly love to be proven wrong, though. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, Jan 25, 2012 at 02:29:22PM +0100, Janek Warchoł wrote: 2012/1/25 Graham Percival gra...@percival-music.ca: Check your email archives for our discussion on 2011 Dec 2 for all the reasons I think this is a bad idea. Sorry, but i'm searching for 10 minutes and haven't found relevant thread. Can you be more specific? The title was [lilypond private] sponsorships for programming It was sent to the email address that you have listed in this email. Hopefully it's in your archive mailbox, rather than being deleted. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
Can someone do a survey how other free software projects handle this? We could also set up a Pledgie campaign, however, this also cuts off 3% (or more) of the money. 97% of something is more than 100% of nothing. Indeed. What about setting up a whole bunch of lilypond crowdfunding campaigns, one for each developer, and all of them under a `lilypond umbrella'? Announcements for `I'm working on feature XXX' could be sent to a central list, and interested people could contribute money. If a certain amount of money has been reached, the developer starts with his stuff. Note that there are two models of funding sites: . kickstarter.com (and clones): Within a certain amount of time, a certain amount of money must be collected. If this goal hasn't been reached, the money is sent back to the donators. . pledgie.com (and clones): There's a time limit, but it is rather a soft one, and donations are not paid back. I have no idea whether such an `umbrella' structure is possible at all with the setup of current crowdfunding sites. A special campaign to have financial support for attending conferences would also fit in such scheme. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patchy email
Begin LilyPond compile, commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c Merged staging, now at: f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467 Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:nice make clean -j3 CPU_COUNT=3 Success:nice make -j3 CPU_COUNT=3 Success:nice make test -j3 CPU_COUNT=3 *** FAILED BUILD *** nice make doc -j3 CPU_COUNT=3 Previous good commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c Current broken commit: f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
lilypond.patchy.gra...@gmail.com writes: Begin LilyPond compile, commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c Merged staging, now at: f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467 Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:nice make clean -j3 CPU_COUNT=3 Success:nice make -j3 CPU_COUNT=3 Success:nice make test -j3 CPU_COUNT=3 *** FAILED BUILD *** nice make doc -j3 CPU_COUNT=3 Previous good commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c Current broken commit: f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467 That would be the 2240 work. I did a full make check and a build of the info documentation which in my experience is pretty much the same as a make doc but somewhat faster. Seems that the similarity does not go deep enough. My guess is that translations may not be covered. Apologies. I'll be fixing this, but it will take several hours to make a doc build on my current setup. Do you have the log files for the failed runs, perchance? Thanks -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
David Kastrup d...@gnu.org writes: *** FAILED BUILD *** nice make doc -j3 CPU_COUNT=3 Previous good commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c Current broken commit: f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467 That would be the 2240 work. I did a full make check and a build of the info documentation which in my experience is pretty much the same as a make doc but somewhat faster. Seems that the similarity does not go deep enough. My guess is that translations may not be covered. Apologies. I'll be fixing this, but it will take several hours to make a doc build on my current setup. Do you have the log files for the failed runs, perchance? Sorry again for the problem, but I am actually at a loss what to do if my guess about the translations is correct: do I copy over the relevant @lilypond passages and keep everything else the same (namely unupdated, and do I leave the @example code passages unchanged or do I copy them over as well?) including this is a translation of committish ..., but change the \version string? Basically, do I simulate having applied a remarkably clever convert-ly rule? -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
David Kastrup d...@gnu.org writes: David Kastrup d...@gnu.org writes: *** FAILED BUILD *** nice make doc -j3 CPU_COUNT=3 Previous good commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c Current broken commit: f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467 That would be the 2240 work. I did a full make check and a build of the info documentation which in my experience is pretty much the same as a make doc but somewhat faster. Seems that the similarity does not go deep enough. My guess is that translations may not be covered. Apologies. I'll be fixing this, but it will take several hours to make a doc build on my current setup. Do you have the log files for the failed runs, perchance? Sorry again for the problem, but I am actually at a loss what to do if my guess about the translations is correct: do I copy over the relevant @lilypond passages and keep everything else the same (namely unupdated, and do I leave the @example code passages unchanged or do I copy them over as well?) including this is a translation of committish ..., but change the \version string? Basically, do I simulate having applied a remarkably clever convert-ly rule? I decided that this probably makes the most sense. I apologize for the stupidity of totally overlooking that without covering the translations this can't possibly work. I will be committing translations with fixed code in the next hour or so to staging. My testing setup is not capable of providing feedback for them in a timely manner; James has offered to do that for me. I hope to rectify this ASAP and get staging back into orderly state. Sorry again. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Wed, Jan 25, 2012 at 08:29:51PM +0100, David Kastrup wrote:
That would be the 2240 work. I did a full make check and a build of the
info documentation which in my experience is pretty much the same as a
make doc but somewhat faster.
If it wasn't a build from scratch, it doesn't count.
I'll be fixing this, but it will take several hours to make a doc build
on my current setup. Do you have the log files for the failed runs,
perchance?
this fails:
\sourcefileline 99
tonic=fis'
{ \tonic \transpose c g \tonic }
I tried it manually:
foo.ly:101:10: error: not a rhythmic event
{ \tonic
\transpose c g \tonic }
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
2012/1/25 David Kastrup d...@gnu.org: Sorry again for the problem, but I am actually at a loss what to do if my guess about the translations is correct: do I copy over the relevant @lilypond passages and keep everything else the same (namely unupdated, and do I leave the @example code passages unchanged or do I copy them over as well?) including this is a translation of committish ..., but change the \version string? Basically, do I simulate having applied a remarkably clever convert-ly rule? convert-ly what you want but don't touch the IDs after this is a translation of committish ... because they could point to old originals. Updating them would be possible for full updated translations only. We'll take kare of ID strings in our files. updating code in @example or @lilypond blocks is welcome. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, 25 Jan 2012, David Kastrup wrote: I do share Graham's concerns which have been previously hashed out in private discussions: an official money channel for LilyPond is not something easy to set up. There are already existing free software umbrella organizations that do this: one is SPI[1], another SFC[2]. I'm not sure about the particulars of them paying out bounties, but ISTR it happening or at least being discussed in the past. This would require a bit of organization on the part of the lilypond project to become an associated project, but the actual intake and disbursement of funds would be handled by SFC or SPI in an open manner.[3] I believe the overhead for both SPI and SFC are on the order of 5% (though I think SFC has a non-mandatory overhead), with additional overhead for transfer fees. Don Armstrong 1: http://www.spi-inc.org; full disclosure: I'm a Debian Developer and SPI contributing member, and know most of the board members. 2: http://www.sfconservancy.org/; full disclosure: I'm friends of Bradley Kuhn, the executive director of SFC, and know some of the board members. 3: http://www.spi-inc.org/projects/associated-project-howto/ for example. -- Let the victors, when they come, When the forts of folly fall Find thy body by the wall! -- Matthew Arnold http://www.donarmstrong.com http://rzlab.ucr.edu ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
2012/1/25 Francisco Vila paconet@gmail.com: 2012/1/25 David Kastrup d...@gnu.org: Sorry again for the problem, but I am actually at a loss what to do if my guess about the translations is correct: do I copy over the relevant @lilypond passages and keep everything else the same (namely unupdated, and do I leave the @example code passages unchanged or do I copy them over as well?) including this is a translation of committish ..., but change the \version string? updating the \version string is also welcome as long as it matches that of @lilypond code. Usually code and version is made to match originals at once. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, Jan 25, 2012 at 12:09:25PM -0800, Don Armstrong wrote: There are already existing free software umbrella organizations that do this: one is SPI[1], another SFC[2]. Yes, I've considered suggesting (after Valentin suggested it to me) that we might want to approach SFC, but it hasn't been the right time yet. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
Graham Percival gra...@percival-music.ca writes:
On Wed, Jan 25, 2012 at 08:29:51PM +0100, David Kastrup wrote:
That would be the 2240 work. I did a full make check and a build of the
info documentation which in my experience is pretty much the same as a
make doc but somewhat faster.
If it wasn't a build from scratch, it doesn't count.
I'll be fixing this, but it will take several hours to make a doc build
on my current setup. Do you have the log files for the failed runs,
perchance?
this fails:
\sourcefileline 99
tonic=fis'
{ \tonic \transpose c g \tonic }
I tried it manually:
foo.ly:101:10: error: not a rhythmic event
{ \tonic
\transpose c g \tonic }
WTF? That's definitely something in the changes file. I checked this
and it compiled and I had code that made sure it compiled. With all the
rebasing to make this fit better I must have displaced the relevant
commit that explicitly makes this compile somehow after all. I'll be
pushing that ASAP and check the translations afterwards.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Wed, Jan 25, 2012 at 09:20:18PM +0100, David Kastrup wrote: WTF? That's definitely something in the changes file. I checked this and it compiled and I had code that made sure it compiled. With all the rebasing to make this fit better I must have displaced the relevant commit that explicitly makes this compile somehow after all. I'll be pushing that ASAP and check the translations afterwards. I see your fix. However, I'm reluctant to run patchy-staging right now, since it would leave master broken in 1f0a00b69403290b7fc7527b9ab100f95533f954 and fixed in 75d0e8cf509685df2e0ed5722803622258673c07 True, we're unlikely to have git-bisect stop in between those two commits, but would it be possible for you to include the parser.yy fix in the relevant branch merge so that there isn't any danger when running git-bisect? - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
David Kastrup d...@gnu.org writes: Seems like I really got mixed up with my builds. Turns out that my changes.tely entry depends on the patch in URL:http://code.google.com/p/lilypond/issues/detail?id=2247 so I pushed that as well as it is reasonably simple and well-contained. No idea how this could get through testing, but with my setup I probably took one this-is-equivalent shortcut too many to get this made in a humanly acceptable time frame. And it does not look like there would have been any backward-incompatible doc change (though there are some changes that really are not related to the EventChord stuff but were basically done on-the-fly) that would require transferring to the translations. So Patchy should have a good chance of being happy now. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
Graham Percival gra...@percival-music.ca writes: On Wed, Jan 25, 2012 at 09:20:18PM +0100, David Kastrup wrote: WTF? That's definitely something in the changes file. I checked this and it compiled and I had code that made sure it compiled. With all the rebasing to make this fit better I must have displaced the relevant commit that explicitly makes this compile somehow after all. I'll be pushing that ASAP and check the translations afterwards. I see your fix. However, I'm reluctant to run patchy-staging right now, since it would leave master broken in 1f0a00b69403290b7fc7527b9ab100f95533f954 and fixed in 75d0e8cf509685df2e0ed5722803622258673c07 True, we're unlikely to have git-bisect stop in between those two commits, but would it be possible for you to include the parser.yy fix in the relevant branch merge so that there isn't any danger when running git-bisect? I'll try doing this without messing up again. 15 minutes or so at least. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
David Kastrup d...@gnu.org writes: Graham Percival gra...@percival-music.ca writes: On Wed, Jan 25, 2012 at 09:20:18PM +0100, David Kastrup wrote: WTF? That's definitely something in the changes file. I checked this and it compiled and I had code that made sure it compiled. With all the rebasing to make this fit better I must have displaced the relevant commit that explicitly makes this compile somehow after all. I'll be pushing that ASAP and check the translations afterwards. I see your fix. However, I'm reluctant to run patchy-staging right now, since it would leave master broken in 1f0a00b69403290b7fc7527b9ab100f95533f954 and fixed in 75d0e8cf509685df2e0ed5722803622258673c07 True, we're unlikely to have git-bisect stop in between those two commits, but would it be possible for you to include the parser.yy fix in the relevant branch merge so that there isn't any danger when running git-bisect? I'll try doing this without messing up again. 15 minutes or so at least. Go ahead. No diff to last staging regarding the result, but the fix commit has been pulled into the side branch. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
David Kastrup d...@gnu.org writes: David Kastrup d...@gnu.org writes: I'll try doing this without messing up again. 15 minutes or so at least. Go ahead. No diff to last staging regarding the result, but the fix commit has been pulled into the side branch. James was so kind to check the previous fix I committed, and it built cleanly. Since the work tree state is identical to the current fix (I checked that it is), this would seem to imply I can now go to bed without more of a bad conscience. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly: Better formatted error messages (issue 803). (issue 5564043)
LGTM http://codereview.appspot.com/5564043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: change bugreports expected response time (issue 5575047)
I'm not certain if 2 days is a good number. Phil, after examining the specific issues, would you say that 95% of real bug reports are handled within 2 days? or should we make that 3 or 4 days instead? http://codereview.appspot.com/5575047/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Run regression tests for lilypond-book (issue 2223). (issue 5569045)
LGTM http://codereview.appspot.com/5569045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
On Wed, Jan 25, 2012 at 02:29:28PM +0100, David Kastrup wrote: I would want to avoid the situation where I have money on my hand I can't spend in good conscience. In that case, only accept transfers which you feel cover existing work (provided the sender realizes this), or transfers which are an advance payment of future work. So I would attempt of using the next LilyPond report for fishing for _personal_ LilyPond funds, As long as nobody else has put their name on the Sponsorship page, sounds good to me. trying to present the results of the previous discussions about official channels and see what the responses in turns of better ideas as well as actual donations are. No. I am not interested in setting up any official channels for this. That is a barrel of worms that we do *not* need right now. :/ Once we get in the situation where I would tell prospective _personal_ _account_ donators that I already got myself covered, ... which will happen shortly after a princess reads my blog, falls madly in love with me, marries me, and gives me an allowance of a few million dollars. In short, it's not going to happen. Oh, but if it does, here's a message for my future bride: hey babe, I'm not proud. I'll happily be your kept man! or where we find that people are willing to provide money for LilyPond developments that someone else would be better suited to take up, we might have to rethink about putting something up that is less personal than currently you can support some LilyPond developments by supporting David. maybe. I would rather have interested parties add their name to the Sponsorship page. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: change bugreports expected response time (issue 5575047)
- Original Message - From: gra...@percival-music.ca To: janek.lilyp...@gmail.com Cc: re...@codereview-hr.appspotmail.com; lilypond-devel@gnu.org Sent: Wednesday, January 25, 2012 10:10 PM Subject: Re: change bugreports expected response time (issue 5575047) I'm not certain if 2 days is a good number. Phil, after examining the specific issues, would you say that 95% of real bug reports are handled within 2 days? or should we make that 3 or 4 days instead? http://codereview.appspot.com/5575047/ As a Brit, I would write it slightly less definitively. Please allow a few days. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bounties
2012/1/24 Janek Warchoł janek.lilyp...@gmail.com: Xavier, may i ask you an unusual question? Feel free to ignore it. Why could you want to become bounty hunter (i.e. person that organizes bounties and sponsorship)? This topic is not that easy, as expresses the numerous replies showing the different concerns of everyone. On 25 January 2012 02:06, Tim McNamara tim...@bitstream.net wrote: As a user, I would tend to prefer to just kick money into a general fund and let someone figure out how it gets utilized One or two French users also made a similar proposition and asked where they could send such donations to a general (LilyPond Develoment) fund. This is a different approach than the pay-per-feature/fix. On 25 January 2012 12:38, m...@apollinemike.com wrote: In the meantime, I think people should take a gander at: http://audacity.sourceforge.net/?lang=fr http://ardour.org/ http://musescore.org/fr They're all music related projects that have a donation system implemented. Especially with MuseScore, we could just ask them how if it has proven to be effective for them. I think MuseScore funding relies (mainly?) on musescore.com Pro Account, providing an enhanced version of musescore.com storage site for scores. http://musescore.com/upgrade IIRC lasconic (Nicolas Froment) said the 3 main developers (Werner Schweer, Thomas Bonte and himself) are now working full-time on MuseScore. Actually I planned to speak with them about that point at FOSDEM. Does someone have some specific questions I could ask? I'd say also that a project like Open Goldberg is not bad for MuseScore. I don't know if they earn a lot of money from it but at least it brings MuseScore a nice visibility. http://www.kickstarter.com/projects/293573191/open-goldberg-variations-setting-bach-free AFAIK LilyPond has not been involved in such kind of projects. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc: 'Command token too long' error
On 25/01/2012 5:21 AM, Francisco Vila wrote: Hello. This error did not break the build process and I don't know exactly what consequences it has. While make doc: ... cd ./out-www; texi2pdf -I ./out-www -I /home/fravd/source/lilypond/Documentation/out -I /home/fravd/source/lilypond/Documentation -I /home/fravd/source/lilypond/Documentation --quiet snippets.texi Error (196): Command token too long Error (196): Command token too long Error (196): Command token too long Error (196): Command token too long /home/fravd/source/lilypond/scripts/build/out/texi2omf --format pdf --location /usr/local/share/doc/lilypond/html/Documentation/usage.pdf --version 2.15.28 usage.tely out-www/usage.pdf.omf cd ./out-www; texi2pdf -I ./out-www -I /home/fravd/source/lilypond/Documentation/out -I /home/fravd/source/lilypond/Documentation -I /home/fravd/source/lilypond/Documentation --quiet usage.texi ... HEAD is 8be61c2 in the lilypond/translation branch. If I recall correctly this is the bug in texi2pdf that goes away if you set the environment variable LC_ALL=C. We do this when calling texi2pdf from within lilypond-book, maybe we should also do it in the build. -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
