2.15.26 is released, containing the fix for issue 1933
lilypond-book on windows. This marks the end of my active
development work for the next ten weeks: until the end of March, I
am reducing my lilypond time from 10 hours a week to 5 hours a
week. In practice this means that I can reply to
On Sun, Jan 15, 2012 at 02:47:23PM -, Phil Holmes wrote:
OK - so I don't think anyone has looked at this.
Quick check:
- what does 61 do? is that a named pipe?
- in general all the symbols looks a bit iffy... if we hadn't just
had a huge issue with python subprocess on windows, I'd
On Mon, Jan 16, 2012 at 04:31:33PM +0100, m...@apollinemike.com wrote:
Instead, I will end with a plea for more automation.
I have dabbled in this, mostly because I do not know what is
needed. Python is my native language, so if people could start
an automation wishlist, I can get things
On Mon, Jan 16, 2012 at 04:26:04PM -, Phil Holmes wrote:
@example
[remote origin]
fetch = +refs/heads/*:refs/remotes/origin/*
url = ssh://git.sv.gnu.org/srv/git/lilypond.git
@end example
This is precisely what we should avoid. Explaining how to modify
.git/config by hand is tedious,
On Mon, Jan 16, 2012 at 08:07:25PM +, Carl Sorensen wrote:
I'm open to hearing everybody's opinion. If we can get consensus it might
be a powerful motivation for moving to 2.16.
My position is well-known: version numbers are cheap, stable
releases gets new features and bugfixes into the
I believe this will work out-of-the-box for any .TELY file,
regardless of whether texi2pdf is in the path or not. Please
test.
http://lilypond.org/~graham/lilypond-2.15.25-4.mingw.exe
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On Sun, Jan 15, 2012 at 08:59:58AM -, Trevor Daniels wrote:
Graham Percival wrote Sunday, January 15, 2012 8:23 AM
http://lilypond.org/~graham/lilypond-2.15.25-4.mingw.exe
Well, not quite. Two problems:
1. should be output_filename in lines 224 and 226 in book_texinfo.py
Whoops
I believe this will at least produce the default line-widths
out-of-the-box for any texinfo or latex file, regardless of
whether texi2pdf is in the path or not. Please test.
http://lilypond.org/~graham/lilypond-2.15.25-5.mingw.exe
I am hopeful (though I am not optimistic) that it will work with
On Sun, Jan 15, 2012 at 12:18:57PM +, carl.d.soren...@gmail.com wrote:
I think you misunderstand what git rebase does. git rebase
origin/staging does *not* bring origin/staging into dev/cg;
really? wow, I completely misunderstood that.
If origin/staging is bad, and then deleted, and
On Sat, Jan 14, 2012 at 09:01:21AM -0800, lilypond.patchy.ja...@gmail.com wrote:
Begin LilyPond compile, commit: e25565e23b6e7a219c594d359495817d7076eff5
*** FAILED STEP ***
sorry, I forgot to warn you to about lines 45-46 in
compile_lilypond_test.py. You may want to comment those out for
On Sun, Jan 15, 2012 at 11:12:49PM +, carl.d.soren...@gmail.com wrote:
Yes, but I wouldn't leave it in that state. The full set of commands is
git rebase origin/staging dev/cg~0
git push origin HEAD:staging
git checkout dev/cg
LGTM
At this point, you have pushed dev/cg to staging
I've just realized that I've been debugging this a very silly way;
there's no reason to produce a new binary each time.
Could somebody on windows send me lilypond-book.py ? I only need
that file... actually, I only need the first 20 lines or so of
that file. But you might as well send me the
On Sat, Jan 14, 2012 at 09:28:08AM -, Trevor Daniels wrote:
Graham, you wrote Saturday, January 14, 2012 8:07 AM
Could somebody on windows send me lilypond-book.py ? I only need
that file... actually, I only need the first 20 lines or so of
that file. But you might as well send me
On Sat, Jan 14, 2012 at 10:31:43AM -, Trevor Daniels wrote:
Graham, you wrote Saturday, January 14, 2012 9:43 AM
I expect 1 and 2 to work. If 3 works, we're golden. If 4
succeeds then something weirder than I think is happening.
Well, 1 works fine, printing out the directory and
On Sat, Jan 14, 2012 at 10:35:55AM -, Trevor Daniels wrote:
Further to this, if I delete the wait() before the print 2 ... then
2 and 3 work fine, with ret code 0. 4 fails in threading as
expected. Here's the output in this case:
curiouser and curiouser. Please try the attached
On Sat, Jan 14, 2012 at 10:50:03AM -, Trevor Daniels wrote:
cmd = dir log.txt
ret = os.system(cmd)
print 0. return code: , ret
No go. This falls foul of the ant-hacking measures in Windows.
Program Files is a protected directory:
oh mao... ok, does window still have a
On Sat, Jan 14, 2012 at 12:19:24PM -, Trevor Daniels wrote:
c:\Program Files\LilyPond\usr\bin'sleep' is not recognized as an
internal or ex
ternal command, operable program or batch file.
oops, I'm an idiot. I left debugging stuff in there.
Please change line 36:
cmd = sleep 1 dir
On Sat, Jan 14, 2012 at 09:28:08AM -, Trevor Daniels wrote:
Here it is, from usr/bin.
ok, here's a new method. os.system() seems much more reliable
than subprocess for python 2.4.2 in windows, so let's see if we
can get that working.
- Graham
#!/usr/bin/python
# -*- coding: utf-8 -*-
On Thu, Jan 12, 2012 at 09:02:51AM -, Trevor Daniels wrote:
IOError: (0, 'Error')
Lilypond-book returned code 1
Thanks, working on fixes.
As a cheap experiment, could you add this:
### EXPERIMENTAL HACK: see if this makes mingw behave better?
time.sleep(1)
immediately between the
On Fri, Jan 13, 2012 at 08:41:14AM +, Graham Percival wrote:
I don't expect it to work, so I'm writing a more intrusive hack to
hopefully avoid this... but I'd be delighted to junk the larger
hack if that can make it work.
sorry, ignore that. I'm building a new binary with a better fix
I believe that this should work out of the box on any windows
computer which does **NOT** have texi2pdf or texi2dvi installed.
http://lilypond.org/~graham/lilypond-2.15.25-3.mingw.exe
Trevor, if you have latex set up, you may wish to test it with a
different user account (if you didn't install
On Fri, Jan 13, 2012 at 09:02:21AM +, Graham Percival wrote:
I believe that this should work out of the box on any windows
computer which does **NOT** have texi2pdf or texi2dvi installed.
http://lilypond.org/~graham/lilypond-2.15.25-3.mingw.exe
Colin has tested this and found a problem
On Thu, Jan 12, 2012 at 06:50:56PM +0100, Reinhold Kainhofer wrote:
The problem is just that the subprocess module needs msvcrt on Windows,
but that python as provided by lilypond does not ship that module.
This does not appear to have been a problem for the past few
releases.
I would rather
On Thu, Jan 12, 2012 at 07:00:27PM +0100, David Kastrup wrote:
Reinhold Kainhofer reinh...@kainhofer.com writes:
However, even for HTML we need some kind of line width so that we can
line-break all lilypond snippets.
That line width should be based on a pixel width (1024 is probably
On Wed, Jan 11, 2012 at 08:47:51AM +0100, m...@apollinemike.com wrote:
1784 Enhancement mtsolo Adds epsilon to Bezier range calculations Sep
14, 2011 09:33:20
I could add a comment to the code with a TODO for this - there was no
consensus for how to fix it, but it is a bug and at
On Wed, Jan 11, 2012 at 09:41:01AM -, Trevor Daniels wrote:
File out/book_texinfo.py, line 213, in get_texinfo_width_indent
File /usr/lib/python2.4/subprocess.py, line 549, in __init__
OSError: [Errno 22] Invalid argument
Lilypond-book returned code 1
excellent, I can fix that.
Just
On Wed, Jan 11, 2012 at 02:42:19PM -, Trevor Daniels wrote:
It's all a bit academic if no one can point me to a Windows implementation
of texi2pdf or texi2dvi, though.
www.pinteric.com/miktex.html
?
Cygwin also has latex. I see a bunch of hits in google for
texi2pdf windows, although I
I expect to have that sleep(0.001) error. I do not expect any
other errors.
http://lilypond.org/~graham/lilypond-2.15.25-2.mingw.exe
What's the exact error you see when you try this one? I
know/expect that it barfs in threading.py, but I need to know what
in the lilypond code calls that.
On Wed, Jan 11, 2012 at 12:19:27PM +0100, Janek Warchoł wrote:
2012/1/10 Xavier Scheuer x.sche...@gmail.com:
I guess this message would be more appropriate on lilypond-u...@gnu.org
rather than on the bug reports mailing list. May I suggest you to send
it (again) to this address, thus
On Wed, Jan 11, 2012 at 06:52:38AM +0100, Janek Warchoł wrote:
I guess i don't know how to write curly braces in texinfo. Should it be
@example
PATH=~/type-here-directory-containing-git-cl:$\{PATH\}
@end example
escape with @
i.e. @{PATH@}
this is in the CG.
How do i proceed? I
ok, I'm really confused with all the reports about what happens on
all sorts of different lilypond versions.
Please test this version:
http://lilypond.org/~graham/lilypond-2.15.25-1.mingw.exe
add it to your PATH, then me exactly what you see when you try to
call lilypond-book. I have various
On Wed, Jan 11, 2012 at 07:28:18AM +0100, Janek Warchoł wrote:
This might be a stupid question, but i never used lilypond-book
before: should i call it without any input file? If no, can you
provide example input?
Read the Usage manual. Specifically the lilypond-book chapter.
- Graham
On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
nice make doc -j3 CPU_COUNT=3
Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
Current broken commit: 42984d05239a3c3be1ea859ba5214ce140448afc
The
On Mon, Jan 09, 2012 at 08:22:50AM +, Graham Percival wrote:
On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
nice make doc -j3 CPU_COUNT=3
Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
On Mon, Jan 09, 2012 at 02:24:45PM -, Phil Holmes wrote:
It
actually looks like the only substantive change if with the
Documentation/snippets/bar-chords-notation-for-guitar--with-text-spanner.ly
which is duplicated in snippets/new. Mike - you only need to edit
the one in snippets/new -
On Mon, Jan 09, 2012 at 02:10:24PM +, plros...@gmail.com wrote:
I totally share your sentiment, but we depend on an external entity
here, which we cannot control. Suppose we go from 2.15.x to 2.17.x and
put the documentation under v2.17. For some time, Google won't have
the new location
On Tue, Jan 10, 2012 at 12:15:43AM -0500, Pavel Roskin wrote:
Quoting Graham Percival gra...@percival-music.ca:
Great point! Could you add a comment to this effect to the top of
this file? there's no way that I'll remember otherwise.
I believe the comment belongs to some other file
Patchy has helped us avoid breaking git master a few times
recently, but each time involves a certain amount of my time and
energy. I need to check the logs to see if it was just an
accident, look through the git history to see if there's any
particularly suspicious commits that may have caused
On Sun, Jan 08, 2012 at 01:46:44PM +, James wrote:
If somebody else could
take over Patchy -- even if only the staging stuff, not the new
patches -- that would free up time I could spend solving
release-critical bugs. If somebody could handle the new patches
as well, that would be
On Sun, Jan 08, 2012 at 09:53:16PM +, James wrote:
http://lilypond.org/doc/v2.15/Documentation/contributor/unsorted-policies
thanks, run.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On Sun, Jan 08, 2012 at 09:36:22PM +, James wrote:
It isn't as trivial as you think - and can end up a lot of work, and
while I understand the request, there are more pressing items I think
we need to do with the doc before we start to move huge sections
around.
+1
I'm not opposed to
On Sun, Jan 08, 2012 at 10:04:59PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
Current broken commit: cf023c3d5b03b333cb5e5c3c50ab8d6635efdc60
oops, fixed. My fault.
- Graham
On Sat, Jan 07, 2012 at 11:24:18PM +, janek.lilyp...@gmail.com wrote:
I don't know how to check for --enable-double but this patch assures
that fontforge 20110222 is a requirement, not an option.
It's a start, but not enough. You need to check for
--enable-double. It's given by the
On Sun, Jan 08, 2012 at 01:52:41AM +0100, Łukasz Czerwiński wrote:
As for all the emails that were written it the last two days, I believe
that a sort of coordination is needed in each project.
We have the amount of coordination that we have chosen.
* Let's assume that I would like
On Fri, Jan 06, 2012 at 11:42:32AM +0100, Janek Warchoł wrote:
i've created a patch (on a separate local branch), committed it and
uploaded with new git-cl; this created new tracker issue (2175). i
did some more changes, committed them and called 'git cl upload
...
We were not able to
hmm, I think I forgot to do something while reconfiguring my
desktop. Anyway, make doc fails.
I see **tons** of messages like
Defined column-markup function in #directory (lily) 411399f0
which doesn't look like it should exist in production code. It's
certainly not helpful when trying to
On Fri, Jan 06, 2012 at 10:01:00PM +0100, Janek Warchoł wrote:
I've uploaded a documentation patch using git-cl and it was added as
[1]http://code.google.com/p/lilypond/issues/detail?id=2175Â From what
i understand, patchy should check it and set patch status to review,
but it
On Fri, Jan 06, 2012 at 04:38:05PM +, Ian Hulin wrote:
On 06/01/12 12:38, Graham Percival wrote:
I see **tons** of messages like
Defined column-markup function in #directory (lily) 411399f0
which doesn't look like it should exist in production code. It's
certainly not helpful when
Guys,
We've had a bunch of patches breaking staging now. This is
problematic because it holds up other patches from getting into
master. In turn, this holds up a release because I feel weird
about making a release when there's half a dozen patches waiting
to go into master. And right now, this
I've branched current staging -- unfortunately *after* removing
two patches which seemed to break stuff -- to staging-broken-jan7.
I picked one patch, Mike's non-negativity check, to put into the
new staging on the theory that it was the least likely to be
breaking stuff.
If somebody wants to
On Sat, Jan 07, 2012 at 06:16:45AM +, Keith OHara wrote:
Sorry that was probably me.
Not just you -- out of the 7 commits in staging when I began
today, 2 are now known to have problems (one of those was yours).
However, at least one of the 5 in staging-broken-jan7 *also*
breaks the doc
On Wed, Jan 04, 2012 at 09:38:57AM +0100, David Kastrup wrote:
lilypond.patchy.gra...@gmail.com writes:
nice make doc -j3 CPU_COUNT=3
Previous good commit: 2fd5a378f5d883536b1aac57583d261ce60a4043
Current broken commit: c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a
My guess
On Wed, Jan 04, 2012 at 12:48:49AM -0800, Graham Percival wrote:
Since there isn't much interest in cleaning
up compiler warnings[1] so that we can use automatic tools to
identify such problematic occurrences, I guess we'll just stumble
forward as usual.
[1] if your version of g++ doesn't
On Wed, Jan 04, 2012 at 01:04:06PM +0100, m...@apollinemike.com wrote:
*** Stage: package (lilypond-doc, linux-x86)
invoking false
Command barfed: false
This might be related to Carl's suggestion that GUB cannot
correctly download netpbm / samba / rsync / something like that.
I've never
Hey guys,
It seems like we've got solutions for 1933, 1943, and 1948. 2160
was fixed as a side note to the website pdf patch by Alberto.
Dealing with git branches (issue 2100) is the only one that isn't
either finished or really close to being finished, but I expect
that patch just needs
. Check the CC headers of your
email client.
- Graham Percival
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, Jan 03, 2012 at 08:09:10PM +0100, m...@apollinemike.com wrote:
I decided to download GUB and I think I've compiled everything (it ran for
several hours and did not complain).
I have no clue how it works, though. Is there any documentation beside the
README? The thing I understand
On Tue, Jan 03, 2012 at 09:26:48PM +0100, m...@apollinemike.com wrote:
I slavishly follow the instructions in the minor release
subsection or subsubsection. Every single devel release is
created by me copypasting from those steps. If you follow those
steps as well, you should have
On Tue, Jan 03, 2012 at 06:31:54PM +, hashas...@gmail.com wrote:
Sorry, didn't understand what you mean by add issue 2166 to track this
It's not relevant unless you're going to be making other patches.
If you are, read the summary for experienced developers again in
more detail. The git-cl
On Tue, Jan 03, 2012 at 02:57:24PM +0100, David Kastrup wrote:
James pkx1...@gmail.com writes:
My question to David, because I am not getting where the 'ire' is
coming from, why do you care if we release dev after dev release vs
stable?
Yeah, especially since Carl was *already* making
On Tue, Jan 03, 2012 at 10:00:01PM +0100, m...@apollinemike.com wrote:
Any ideas as to why gub hates me so early?
GUB hates you because you skipped over point 3 under pre-release
on:
http://lilypond.org/doc/v2.15/Documentation/contributor/minor-release-checklist
Cheers,
- Graham
On Tue, Jan 03, 2012 at 08:45:45PM +0100, Janek Warchoł wrote:
I guess i should change it into this:
[core]
[branch master]
It's not a bad thing that we can ask git wizards to give us custom
advice on our .git/config, but this shouldn't be necessary. I
mean, the only time I've ever edited
On Tue, Jan 03, 2012 at 10:44:57PM +0100, m...@apollinemike.com wrote:
Ah, I missed it cuz of the layout - my eyes are attracted by things in boxes.
So my lilypond development for the day is...
heh, I've wondered about doing something like that.
I'm not wild about the idea, since the
On Mon, Jan 02, 2012 at 09:59:47PM +0100, David Kastrup wrote:
I see the following critical issues:
-snip-
There is, actually, a wagonload of other changes underfoot that does not
appear quite compatible with releasing a version called stable to me.
It seems strange to me that the _above_
On Mon, Jan 02, 2012 at 11:50:07AM -, Phil Holmes wrote:
I'd like to push
this to staging, but would appreciate someone else (David, Graham?)
looking at it just to check. I'd prefer not to go to a Rietveld for
this simple change.
LGTM.
Cheers,
- Graham
On Mon, Jan 02, 2012 at 10:23:28PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
This was the result of between 25 to 40 emails in August 2011 on
lilypond-devel. A quick scan didn't reveal your name amongst
those emails, but we simply cannot afford
On Tue, Jan 03, 2012 at 01:03:08AM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
We could certainly consider dropping support for OSX or windows.
That sort of token solidarity is actually counterproductive:
if you believe that non-releases lead to non-users
On Tue, Jan 03, 2012 at 04:15:06AM +, Carl Sorensen wrote:
Graham Percival graham at percival-music.ca writes:
[*] after installing libmpfr-dev, which is mentioned in the
README.
In looking at my notes, it appears that I may have failed on my lilydev
install because I didn't install
On Tue, Jan 03, 2012 at 06:24:19AM +0100, Janek Warchoł wrote:
By the way, do we have a policy about regressions?
Yes, they're bad? :)
I remember that
reverting bad commits was discussed in the past, and i'm quite for
this solution.
I don't see information about which commits caused our
On Sun, Jan 01, 2012 at 06:10:00PM -, Phil Holmes wrote:
This is a live and learn. I typically don't add untracked files to patches,
because there are loads of them - git-cl; the aborted_edits from lily-git,
etc., etc. I'd not realised that updates from the LSR could also add files
and
On Sun, Jan 01, 2012 at 06:50:33PM +0100, David Kastrup wrote:
obviously I have been too
clever about this change done automatically and half-reverted. I did
not commit the convert-ly rule since it was somewhat fishy IIRC and
while it worked, I checked the results manually.
I probably
On Sun, Jan 01, 2012 at 08:43:05PM +, Carl Sorensen wrote:
I have made one change to the spec files (the location of netpm
on lilypond.org has changed), and I did a couple of manual
downloads, so I'm not sure yet that GUB is ready to build
out-of-the-box. But I have demonstrated that I
On Sun, Jan 01, 2012 at 09:49:33PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
2) make the changes manually, then put those updated files in
Documentation/snippets/new
Whichever way you choose, I would like to see a local makelsr.py
update after
On Sat, Dec 31, 2011 at 11:27:38AM +0100, David Kastrup wrote:
My guess is that two incantations of Patchy were at work here, and one
of them copied a tested staging to master while the other one was still
working with older material.
There's only one version of Patchy doing the staging stuff,
On Sun, Jan 01, 2012 at 03:18:53AM +, Carl Sorensen wrote:
building package: darwin-ppc::lilypond
*** Stage: compile (lilypond, darwin-ppc)
and now nothing seems to be happening. It's staying here forever, no disk
activity, no change in memory.
Well, it might be that the build system
On Sat, Dec 31, 2011 at 12:10:14AM +, carl.d.soren...@gmail.com wrote:
On 2011/12/30 20:57:02, Graham Percival wrote:
I'm still concerned about this type of automatic pushing. The revised
CG
material on branches
http://codereview.appspot.com/5484043/
makes a bit deal about always
On Fri, Dec 30, 2011 at 01:12:30PM -, Phil Holmes wrote:
I'm not too fussed about that, but the second line should be indented by
two spaces to indicate that it's a continuation of the previous line
(i.e. not starting its own bar). I certainly wouldn't object to having
an explicit
On Thu, Dec 29, 2011 at 12:22:17PM +0100, Federico Bruni wrote:
I have a final draft (see files attached):
I'm quite happy with this version.
Given my time constraints, I am happy to trust you. I fully
expect that you'll get complaints whenever this makes its way into
the actual docs, but
On Thu, Dec 29, 2011 at 05:21:34PM +, carl.d.soren...@gmail.com wrote:
The Push button is disabled by default; an experienced user can enable
it with a simple edit to the script.
By disabled, do you mean commented out ? If new contributors
see a greyed-out button, they'll get confused and
On Thu, Dec 29, 2011 at 11:03:43AM -0700, Aleksandr Andreev wrote:
Aha. Some Googling reveals that:
Exit code 137: The job was killed because it exceeded the time limit.
Don't top-post.
Any ideas how to up the time limit?
Unless you have an incredibly under-powered computer (say, 10
years
On Fri, Dec 30, 2011 at 06:12:58AM +, Carl Sorensen wrote:
More information: When I ran the command by hand, I got this message:
carl@carl-lilydev:~/gub/target/darwin-ppc/build/cross/gcc-4.1.1$ make
tooldir='/usr/powerpc-apple-darwin7' gcc_tooldir='/usr/powerpc-apple-darwin7'
Be aware
On Fri, Dec 30, 2011 at 06:05:17AM +, Carl Sorensen wrote:
I am interested in getting a new stable release of LilyPond out, so I want to
work on Critical issues.
Great! We have definitely suffered from having those critical
issues.
There are 3 critical issues, all of which will require
On Tue, Dec 27, 2011 at 05:14:41PM -, Phil Holmes wrote:
More looking at make doc output. This set of error messages
(Error: Illegal entry in bfrange block in ToUnicode CMap) has been
discussed before, and it's not a Lilypond issue, it's to do with
texi2pdf on Ubuntu.
If you can find
On Mon, Dec 26, 2011 at 12:32:51PM -, Phil Holmes wrote:
Official comparison looks good. Only oddity is 3 logfiles with:
-warning: cannot fit music on page: ragged-spacing was requested,
but page was compressed
which ostensibly seems good, since we've lost a warning. I'm still
On Sat, Dec 24, 2011 at 02:38:31PM -0600, Michael Walker wrote:
Having upgraded to OSX Lion, I quickly noticed that LilyPond isn't
functional yet. I know you guys are aware of this and probably working
on it, but could you possibly give me a date that I could look forward
to using
On Mon, Dec 26, 2011 at 06:21:35PM +, James wrote:
debug1: Next authentication method: publickey
debug1: Offering public key: /home/james/.ssh/id_rsa
shouldn't that be id_rsa.pub ?
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/james/.ssh/identity
On Mon, Dec 26, 2011 at 06:33:20PM +, James wrote:
james@jameslilydev2:~/lilypond-git$ ls -al /home/james/.ssh/
total 20
drwx-- 2 james james 4096 2011-12-26 18:17 .
drwxr-xr-x 37 james james 4096 2011-12-26 18:15 ..
-rw--- 1 james james 1743 2011-12-26 18:15 id_rsa
-rw-r--r--
On Mon, Dec 26, 2011 at 06:50:11PM +, James wrote:
Well that was the first thing I thought. I have copied this from the
terminal and when that didn't work I deleted my whole /.ssh dir,
deleted the key from savannah, waited an hour and then redid the whole
process (get a new key, paste it
On Mon, Dec 26, 2011 at 10:23:55PM +, hashas...@gmail.com wrote:
Let me know if this is what you are thinking:
1. upload those files to github (tell me the folder, I create a pull
request)
Let's make a new folder, pdf/
2. make makefiles copy the files to the correct place
yes.
3.
I've isolated a build-breaking commit to at least one of the 3
that's in the
staging-broken-dec-26
branch. Tomorrow I'll do some more experiments on the other build
patches to see if any of those can be merged to master.
origin/staging should be empty right now, so other patches to it
are
On Sat, Dec 24, 2011 at 07:16:47PM +0100, m...@apollinemike.com wrote:
On Dec 24, 2011, at 1:43 AM, Graham Percival wrote:
Patchy is running every 6 hours at the moment (GMT / 6), and
there's no rush to get another release out, so let's just put
stuff into staging gradually.
Could you
On Sat, Dec 24, 2011 at 05:13:29PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Patchy is running every 6 hours at the moment (GMT / 6), and
there's no rush to get another release out, so let's just put
stuff into staging gradually.
to see about a day's
On Sat, Dec 24, 2011 at 11:07:59PM +0100, David Kastrup wrote:
git log another..branch
Of course, things that have been cherry-picked already are still listed.
Can't that be avoided by looking at the difference between current
master (or current staging) and staging-broken-dec23 ?
Cheers,
-
Hey all,
In order to remove the blockage to development, I've made a copy
of the previous staging branch: it's now called
staging-broken-dec23. I've replaced staging with
master+release/unstable, and Patchy is testing that right now.
Once that's been accepted to master, people are invited to
On Thu, Dec 22, 2011 at 12:54:23PM +0100, David Kastrup wrote:
Instead use
git cl upload
for it. I think the details should be in the Contributor's Guide.
The details are in the CG, the details are in exactly one of the
three pages I linked to in one of the emails I sent him, but he
On Thu, Dec 22, 2011 at 01:35:27PM +0100, David Kastrup wrote:
David Kastrup d...@gnu.org writes:
In file included from
/home/jlowe/lilypond-git/lily/lily-lexer-scheme.cc:21:
/home/jlowe/lilypond-git/lily/include/lily-lexer.hh:69: error: ISO C++
forbids declaration of 'YYSTYPE' with no
On Thu, Dec 22, 2011 at 06:17:57AM -0800, Graham Percival wrote:
That order of commands suggests that lily-lexer-scheme.cc does not
depend on parser.cc. I see that it contains such an #include, so
I would assume that make would catch it... but apparently not.
Skimming through lily/GNUmakefile
On Thu, Dec 22, 2011 at 04:17:23PM +, hashas...@gmail.com wrote:
2) I would not accept this solution even if it worked, because it
involves weird
hard-coding for the old website.
Agreed. But solves an issue that is hanging around for.. one year?
I am not selling this as the salvation
On Thu, Dec 22, 2011 at 05:28:44PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Skimming through lily/GNUmakefile, this makes sense. There's a
couple of explicit dependencies for parser.hh, but these don't
mention lily-lexer-scheme.cc, which is the file
On Thu, Dec 22, 2011 at 07:19:55PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
No problem; I'm quite happy that Patchy is pulling his weight so
soon. :)
Never mind Patchy... After the problematic commit, you made a release
tag and everything
801 - 900 of 5586 matches
Mail list logo
