Re: can't upload a patch
Do you have ca-certificates installed? Il 6 marzo 2017 01:23:26 CET, David Nalesnikha scritto: >Not too long ago, I wrote to the list about an inability to upload >patches. A Rietveld tracker issue is created, but the process >terminates before all of the base files can be uploaded. An Allura >issue is never created. > >I was using a VirtualBox VM on a Windows 10 system. > >Now, on a different machine, no Windows, with Ubuntu 16.10 and LilyDev >4.1 running (also in VirtualBox), I get the same result. > >Here is what happens when I attempt to upload a patch: > >[lilypond-git (dev/bracket_reorganization)]$ git-cl upload >origin/master >lily/bracket.cc| 151 >+ > lily/enclosing-bracket.cc | 16 ++-- > lily/horizontal-bracket.cc | 73 +- > lily/include/bracket.hh| 40 ++ > lily/include/horizontal-bracket.hh | 5 -- > lily/include/tuplet-bracket.hh | 4 - > lily/ottava-bracket.cc | 11 ++- > lily/piano-pedal-bracket.cc| 10 +-- > lily/tuplet-bracket.cc | 78 +++ > lily/volta-bracket.cc | 9 +-- > 10 files changed, 227 insertions(+), 170 deletions(-) >Upload server: codereview.appspot.com (change with -s/--server) >Your browser has been opened to visit: > >https://codereview.appspot.com/get-access-token?port=8001 > >If your browser is on a different machine then exit and re-run >upload.py with the command-line parameter > > --no_oauth2_webbrowser > >Issue created. URL: http://codereview.appspot.com/313670043 >Uploading base file for lily/include/horizontal-bracket.hh >Uploading base file for lily/include/tuplet-bracket.hh >Traceback (most recent call last): > File "/home/david/git-cl/git-cl", line 628, in >sys.exit(main(sys.argv)) > File "/home/david/git-cl/git-cl", line 622, in main >return func(argv[2:]) > File "/home/david/git-cl/git-cl", line 335, in CmdUpload >issue, patchset = upload.RealMain(['upload'] + upload_args + args) > File "/home/david/git-cl/upload.py", line 2693, in RealMain >vcs.UploadBaseFiles(issue, rpc_server, patches, patchset, options, >files) > File "/home/david/git-cl/upload.py", line 1220, in UploadBaseFiles >print t.get(timeout=60) > File "/usr/lib/python2.7/multiprocessing/pool.py", line 558, in get >raise self._value >urllib2.URLError: >[lilypond-git (dev/bracket_reorganization)]$ > >_ > >Does anybody have an idea of what could be happening? Has anybody >experienced this problem? > >At my wit's end :( > >David > >___ >lilypond-devel mailing list >lilypond-devel@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: nest GSOC project ideas under subsection/h3 (issue 314530043 by paulwmor...@gmail.com)
Sorry for the delay. My tool isn't public yet (hopefully tomorrow or Tuesday), but I just ran it on the lilypond website and it looks fine. This change LGTM. https://codereview.appspot.com/314530043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC 2017
>> Not yet :-) I can only second what Urs said. > > I think we (i.e. Abraham and you) should give Matthew some more > concrete pointers on where to start investigating. Can you send him our e-mail conversation regarding this topic? Currently, I'm abroad, not having time to do that by myself. >> BTW, where are the current instructions to install a font compliant >> to the SMuFL layout? > > What context are you talking about here? This context: http://lilypondblog.org/2014/01/smufl-fonts-in-lilypond/ I don't know whether this is still up to date. > For LilyPond there *are* of course no such instructions yet, and > otherwise you can install them like regular fonts, it's then up to > the notation application to properly use it. Well, yes. But music fonts are handled specially in lilypond... Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC 2017
Hi Matthew, Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: > >> The first thing will be to get an idea about what happens when >> LilyPond uses glyphs from the notation font. How does it locate the >> font, how does it identify the glyph to choose? And on the other >> side, how is the notation font created during LilyPond's build >> process? I think this is what you'll want to go for first, as a >> basis to shape a project description. >> >> I assume that Werner Lemberg and Abraham Lee will have to say some >> more on the technical parts of this project > Not yet :-) I can only second what Urs said. I think we (i.e. Abraham and you) should give Matthew some more concrete pointers on where to start investigating. > > BTW, where are the current instructions to install a font compliant to > the SMuFL layout? What context are you talking about here? For LilyPond there *are* of course no such instructions yet, and otherwise you can install them like regular fonts, it's then up to the notation application to properly use it. Urs -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Obsolete GSoC page (was: GSoC 2017)
Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: > PS: If I do a google search for `lilypond gsoc', the first hit is the > old > > http://lilypond.org/gsoc.html > > and only the second hit is the current > > http://lilypond.org/google-summer-of-code.html > > Any chance to fix this quickly, for example, to copy the latter to > the former? I'm very surprised and didn't even know such a page exists! ~/git/lilypond/source$ git grep gsoc Documentation/es/web/community.itexi:@uref{https://developers.google.com/open-source/gsoc/, GSoC} es un Documentation/es/web/news.itexi:@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012, El Documentation/fr/web/community.itexi:@uref{https://developers.google.com/open-source/gsoc/resources/manual, Documentation/it/web/community.itexi:@uref{https://developers.google.com/open-source/gsoc/, GSoC} è un programma Documentation/ja/web/community.itexi:@uref{https://developers.google.com/open-source/gsoc/, GSoC} is a global Documentation/web/community.itexi:@uref{https://developers.google.com/open-source/gsoc/resources/manual, Documentation/web/news.itexi:@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012, Documentation/zh/web/news-front.itexi:@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012, This indicates that the GSoC page's translation hasn't been properly updated for a number of languages, but it doesn't really show how a gsoc.html should have been triggered. Is it possible that the HTML file is a leftover that simply hasn't been removed when uploading the updated site (how is that actually done)? If so, I suggest to use a permanent redirect instead of copying over the content. Anyway, this should (urgently) be looked at by someone familiar with the website build process. Urs -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC 2017
>> I also would appreciate any help defining this project so I can >> write an effective proposal. I am new to LillyPond development, but >> I have used the program many years ago. s/LillyPond/LilyPond/ > The first thing will be to get an idea about what happens when > LilyPond uses glyphs from the notation font. How does it locate the > font, how does it identify the glyph to choose? And on the other > side, how is the notation font created during LilyPond's build > process? I think this is what you'll want to go for first, as a > basis to shape a project description. > > I assume that Werner Lemberg and Abraham Lee will have to say some > more on the technical parts of this project Not yet :-) I can only second what Urs said. BTW, where are the current instructions to install a font compliant to the SMuFL layout? Werner PS: If I do a google search for `lilypond gsoc', the first hit is the old http://lilypond.org/gsoc.html and only the second hit is the current http://lilypond.org/google-summer-of-code.html Any chance to fix this quickly, for example, to copy the latter to the former? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
can't upload a patch
Not too long ago, I wrote to the list about an inability to upload patches. A Rietveld tracker issue is created, but the process terminates before all of the base files can be uploaded. An Allura issue is never created. I was using a VirtualBox VM on a Windows 10 system. Now, on a different machine, no Windows, with Ubuntu 16.10 and LilyDev 4.1 running (also in VirtualBox), I get the same result. Here is what happens when I attempt to upload a patch: [lilypond-git (dev/bracket_reorganization)]$ git-cl upload origin/master lily/bracket.cc| 151 + lily/enclosing-bracket.cc | 16 ++-- lily/horizontal-bracket.cc | 73 +- lily/include/bracket.hh| 40 ++ lily/include/horizontal-bracket.hh | 5 -- lily/include/tuplet-bracket.hh | 4 - lily/ottava-bracket.cc | 11 ++- lily/piano-pedal-bracket.cc| 10 +-- lily/tuplet-bracket.cc | 78 +++ lily/volta-bracket.cc | 9 +-- 10 files changed, 227 insertions(+), 170 deletions(-) Upload server: codereview.appspot.com (change with -s/--server) Your browser has been opened to visit: https://codereview.appspot.com/get-access-token?port=8001 If your browser is on a different machine then exit and re-run upload.py with the command-line parameter --no_oauth2_webbrowser Issue created. URL: http://codereview.appspot.com/313670043 Uploading base file for lily/include/horizontal-bracket.hh Uploading base file for lily/include/tuplet-bracket.hh Traceback (most recent call last): File "/home/david/git-cl/git-cl", line 628, in sys.exit(main(sys.argv)) File "/home/david/git-cl/git-cl", line 622, in main return func(argv[2:]) File "/home/david/git-cl/git-cl", line 335, in CmdUpload issue, patchset = upload.RealMain(['upload'] + upload_args + args) File "/home/david/git-cl/upload.py", line 2693, in RealMain vcs.UploadBaseFiles(issue, rpc_server, patches, patchset, options, files) File "/home/david/git-cl/upload.py", line 1220, in UploadBaseFiles print t.get(timeout=60) File "/usr/lib/python2.7/multiprocessing/pool.py", line 558, in get raise self._value urllib2.URLError: [lilypond-git (dev/bracket_reorganization)]$ _ Does anybody have an idea of what could be happening? Has anybody experienced this problem? At my wit's end :( David ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Move older news to the attic page (issue 318630043 by paulwmor...@gmail.com)
I've updated the tracker to use this Rietveld https://codereview.appspot.com/320290043/ I'll make sure Paul gets the credit when the patch is eventually pushed. https://codereview.appspot.com/318630043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Move older news to the attic page (issue 318630043 by paulwmor...@gmail.com)
On 2017/03/05 00:25:33, pwm wrote: On 2017/03/04 20:52:49, pkx166h wrote: > > I'll have a go at fixing this now. Thanks, I haven't had a chance to work on this yet. Sorry I didn't try a 'make doc' before uploading for review. Since 'make website' succeeded I thought it was good to go... but that's not the case. Don't worry, it wouldn't be the first time this kind of thing has happened :) One simple solution would be: Instead of renaming those two files (which breaks the translations), effectively create copies of them and rename the copies. Then later after the translations have been updated to use the new files, delete the old copies with the old names. (Of course building on patch set 1, one would copy the new versions and give them the old names...) No I think probably the simplest thing is to just add/change the @include references as Jean-Charles and Federico pointed out. I did a quick and dirty test last night when I saw Jean-Charle's comment [1] and I replaced the links in the community.texi files from the other languages - well, all but one - that I had missed in my haste - and it of course failed on that one, which just confirmed Jean-Charle's diagnoses. What I will do is take your checkin, add my bits and pieces and re-submit the tracker and Rietveld to save you the bother - obviously when the patch is pushed I'll make sure you get the credit in the authorship. Then the translator-people can make sure it is OK as well. Because of the nature of how different translations get further and further away at different rates compared to the English version the addition of the 'old news' link - which I think is important, is just a simple @include at the end of the community.itexi file. As I cannot speak all the languages that are being translated, there will be no 'if you want to see the new news go to @ref{}' but just the @include statement which is better than nothing. Although the translators may disagree. I'll ge to work on that now. James [1] Thanks Jean-Charles, I should have thought of that, at least now I know why when I make some test patches on my side it's always the Catalan translation that seems to cause problems (i.e. it isn't, it's just that that is the first one in the list of translated languages), so now I know this it will help me in the future to diagnose problems more quickly. https://codereview.appspot.com/318630043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel