Re: Still cannot build GUB with stable/2.20 branch
On 19.03.19 00:00, David Kastrup wrote: I cherry-picked those commits now but have no idea what I am actually doing here. During the work on gub it was discoved that lilypond required etex on the build system although it never really used it. Gub pull request 59 (that worked around the problem) was abandoned and a proper fix for lilypond was implemented. Now you cherry-picked those commits ... Knut ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
Knut Petersen writes:
> On 21.03.19 12:04, Phil Holmes wrote:
>
>> Anyway - it would seem easiest just to create a 'lilypond' group.
>> Does that seem the best way forward?
>
> In rsync-lily-doc.py we have:
>
> system ('rsync --exclude "*.signature" --hard-links
> --delay-updates --delete --delete-after --stats --progress -pgorltvu
> -e ssh . %s/%s/' % (options.destination, branch_dir))
>
> In rsync-test.py we have:
>
> system ('rsync --hard-links --delay-updates --delete --delete-after
> --stats --progress -pgorltvu -e ssh . %s/%s/' % (options.destination,
> target))
>
> Group and ownership are preserved here. But "preserved" means that the
> numeric group / user id is preserved, not the literal name mapped to
> the GID/UID on the two systems.
Sure about that?
-o, --owner
This option causes rsync to set the owner of the
destination file to be the same as the source file, but
only if the receiving rsync is being run as the
super-user (see also the --super and --fake-super
options). Without this option, the owner of new and/or
transferred files are set to the invoking user on the
receiving side.
The preservation of ownership will associate matching
names by default, but may fall back to using the ID
number in somecircumstances (see also the
--numeric-ids option for a full discussion).
-g, --group
This option causes rsync to set the group of the
destination file to be the same as the source file. If
the receiving program is not running as the super-user
(or if --no-super was specified), only groups that the
invoking user on the receiving side is a member of will
be preserved. Without this option, the group is set to
the default group of the invoking user on the receiving
side.
The preservation of group information will associate
matching names by default, but may fall back to using
the ID number in some circumstances (see also the
--numeric-ids option for a full discussion).
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
On 21.03.19 12:04, Phil Holmes wrote:
Anyway - it would seem easiest just to create a 'lilypond' group. Does that seem the best way forward?
In rsync-lily-doc.py we have:
system ('rsync --exclude "*.signature" --hard-links --delay-updates
--delete --delete-after --stats --progress -pgorltvu -e ssh . %s/%s/' %
(options.destination, branch_dir))
In rsync-test.py we have:
system ('rsync --hard-links --delay-updates --delete --delete-after --stats
--progress -pgorltvu -e ssh . %s/%s/' % (options.destination, target))
Group and ownership are preserved here. But "preserved" means that the numeric
group / user id is preserved, not the literal name mapped to the GID/UID on the two
systems.
I think you first need to find out what numeric UID/GID is expected for the
files on the upload server. Then create a lilypond group with the proper GID
and try again ... maybe something similar is necessary if a specific UID is
expected.
Knut
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC in contemporary notations
Hi Urs, Thank you for your reply, and thank you so much for asking about my name. On Thu, 21 Mar 2019 at 17:58, Urs Liska wrote: > Hi Tsz Kiu Pang (which of these names would you like to be called, or > should I use all of them like I did?) > Tsz Kiu Pang is fine, though people usually call me Tsz Kiu, which is my first name. > > I was just looking at the project suggestions, and am interested in > working > > on contemporary notations. > > This would be great. While all of our GSoC suggestions would be very > welcome additions this one would maybe provide the most "visible" and > spectacular addition, opening up LilyPond for a whole range of > applications and therefore potential users. > I am glad to hear that my interests align with you guys. A specific composer's package would be a secondary package built on top > of a general package, and I think it would be great to aim at starting > one for one specific composer (the one I had always thought of as a > basis was Lachenmann, but Xenakis or Carter are equally valid choices), > although it is not a requirement to achieve /comprehensive/ coverage of > a composer. > Yes, I agree that the secondary package would have to be build on top of a general package, and this is great since I hope this project can make contemporary notation accessible to LilyPond users in a general sense, but not just focusing on one or two composers. The Scheme/Guile part has three steps for you to consider: > > * "Counting parentheses" (i.e. the language basics) > Depending on how far you've got https://scheme-book.ursliska.de > might be a useful resource for you. It goes only that far but it > specifically addresses a) the Scheme language from a dedicated > LilyPond perspective and b) users counting parentheses (i.e. giving > a pretty slow-paced introduction) > * Understanding how Scheme is hooked into LilyPond (on a general level) > * (Learning how openLilyLib ist structured) > * Learning how to retrieve the relevant information about score > elements and how to modify them in appropriate places. > > The last one is probably the hardest one since it is pretty opaque and > terribly documented. But it's the crucial one for a contemporary > notation package - and it's the one where such a package will make it > hugely easier for people to work with non-standard notation. > They all sound pretty hard, but your website seems like a great resource. I will definitely have a look at it. Regarding learning how Scheme is hooked into LilyPond, what is some other good resource for it, apart from your website? Just last week I've decided to start with a new openLilyLib package: > https://github.com/openlilylib/grob-tools. The repository on Github is > empty, and right now I only have one single uncommited function locally, > but the idea is to create building blocks for recurring tasks like > getting the exact position of objects relative to the staff or to > another object, enumerating all NoteColumns included in a slur or > similar things. This will be very much relevant for a contemporary > notation package. One could either say that you should put much of your > results in that package, or we can try to make development of that > package a community effort so that would take work from you, giving you > the freedom to go further with the specific challenges. > Making the development as a community effort sounds great, though I cannot say for sure until I have a solid proposal. What you should do now is: > > * [of course dive more into Scheme] > * get an understanding of openLilyLib with > a) https://github.com/openlilylib/oll-core/wiki > b) the code in that repository > c) looking at how other openLilyLib packages are built within that > infrastructure > * Form an idea how a contemporary notation package could be approached > and discuss that with us > * Find some small things you could do to openLilyLib package(s) to a) > practice and b) give us an opportunity to assess your work. If we > have some idea about your current familiarity with the matter we can > find some suggestions for that. > Thank you for your concrete and useful suggestions. I will definitely learn how to count parentheses and all that, and also try to familiarise myself with openLilyLib. Though if you do not mind, please except a lot of questions from me in these couple of weeks. Regards, Tsz Kiu > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES - Countdown for March 21st
Hello, Here is the current patch countdown list. The next countdown will be on March 24th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Push: 5498 Revert the changes of issue 4914 - David Kastrup https://sourceforge.net/p/testlilyissues/issues/5498 http://codereview.appspot.com/554550043 5497 Change hardcoded pair to cons call for return -- remove ugh comment - Carl Sorensen https://sourceforge.net/p/testlilyissues/issues/5497 http://codereview.appspot.com/574530043 5496 Clean up problems with fret-diagram-terse markups - Carl Sorensen https://sourceforge.net/p/testlilyissues/issues/5496 http://codereview.appspot.com/546560043 Countdown: 5495 Add warning message for unknown code in fret-diagram-verbose - Carl Sorensen https://sourceforge.net/p/testlilyissues/issues/5495 http://codereview.appspot.com/570540043 Review: No patches in Review at this time. New: No new patches at this time. *** Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" [...] >>> I believe GUB upload uses rsync. >> >> Then it depends on the options used. Some versions Oops. Some options >> of rsync try to preserve group/owner. > > It looks like the command is this from upload.py: > > cmds += ['rsync --delay-updates --progress %s %s' > > % tup for tup in src_dests] As long as those %s fields don't interpolate additional options, this would not appear to try transferring/preserving group ownership. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "John Mandereau" ; "Lily devel" Sent: Thursday, March 21, 2019 10:58 AM Subject: Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch] "Phil Holmes" writes: - Original Message - From: "David Kastrup" [...] I believe GUB upload uses rsync. Then it depends on the options used. Some versions Oops. Some options of rsync try to preserve group/owner. It looks like the command is this from upload.py: cmds += ['rsync --delay-updates --progress %s %s' % tup for tup in src_dests] As long as those %s fields don't interpolate additional options, this would not appear to try transferring/preserving group ownership. So I wonder why upload is changing the ownership of the files? Anyway - it would seem easiest just to create a 'lilypond' group. Does that seem the best way forward? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "John Mandereau" ; "Lily devel" Sent: Thursday, March 21, 2019 10:24 AM Subject: Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch] "Phil Holmes" writes: - Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "John Mandereau" ; "Lily devel" Sent: Wednesday, March 20, 2019 8:27 PM Subject: Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch] "Phil Holmes" writes: - Original Message - From: "David Kastrup" Not sure why it wants to change group to a non-existent entity. Does it copy the permissions (and memberships) to the remote server? Depends on what commands are used for copying. I believe GUB upload uses rsync. Then it depends on the options used. Some versions of rsync try to preserve group/owner. It looks like the command is this from upload.py: cmds += ['rsync --delay-updates --progress %s %s' % tup for tup in src_dests] -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Phil Holmes" > Cc: "John Mandereau" ; "Lily devel" > > Sent: Wednesday, March 20, 2019 8:27 PM > Subject: Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB > with stable/2.20 branch] > > >> "Phil Holmes" writes: >> >>> - Original Message - >>> From: "David Kastrup" > >>> Not sure why it wants to change group to a non-existent entity. Does >>> it copy the permissions (and memberships) to the remote server? >> >> Depends on what commands are used for copying. > > > I believe GUB upload uses rsync. Then it depends on the options used. Some versions of rsync try to preserve group/owner. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "John Mandereau" ; "Lily devel" Sent: Wednesday, March 20, 2019 8:27 PM Subject: Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch] "Phil Holmes" writes: - Original Message - From: "David Kastrup" Not sure why it wants to change group to a non-existent entity. Does it copy the permissions (and memberships) to the remote server? Depends on what commands are used for copying. I believe GUB upload uses rsync. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC in contemporary notations
Hi Tsz Kiu Pang (which of these names would you like to be called, or should I use all of them like I did?) Am 21.03.19 um 06:58 schrieb Tsz Kiu Pang: Hi all, I am writing to express my interest in working on LilyPond as part of GNU in the Google Summer of Code. I was just looking at the project suggestions, and am interested in working on contemporary notations. This would be great. While all of our GSoC suggestions would be very welcome additions this one would maybe provide the most "visible" and spectacular addition, opening up LilyPond for a whole range of applications and therefore potential users. As a composer myself, I do find using Lilypond a very steep learning curve, especially for contemporary music, where a lot of workarounds are needed. That's true, and one major issue with that (which a package would address) is that so many things have to be done from scratch over and over again, for each new project, or at least by each new user dealing with them. I hope I can use this opportunity to create an infrastructure for contemporary notations that will make composers' life easier. I am also interested in creating a package that covers the style of composers such as Iannis Xenakis or Elliott Carter. A specific composer's package would be a secondary package built on top of a general package, and I think it would be great to aim at starting one for one specific composer (the one I had always thought of as a basis was Lachenmann, but Xenakis or Carter are equally valid choices), although it is not a requirement to achieve /comprehensive/ coverage of a composer. I am just wondering if there are any suggestions in applying for GSoC and writing a project proposal? Basically you'd have to discuss a proposal on this list or in a somewhat more private circle (although generally as much as possible communication should be in public space) and find a way to show us your qualification, potential and way of communication until April 9. A bit more on that below. As for qualifications, I did my undergraduate in Music, majored in Composition during my honours year, so I have good knowledge in contemporary notation techniques and the capacity to research further if required. I am currently a Master student in electrical engineering at the University of Melbourne. I have only started programming last year but now I am a tutor in programming/computing in C at the University. Though scheme/guile is not my strong suit yet (I know the basic syntax and list operations, but still struggling to count the parentheses), I am willing to learn more and I believe I will have a good command in scheme/guile in a few weeks. The Scheme/Guile part has three steps for you to consider: * "Counting parentheses" (i.e. the language basics) Depending on how far you've got https://scheme-book.ursliska.de might be a useful resource for you. It goes only that far but it specifically addresses a) the Scheme language from a dedicated LilyPond perspective and b) users counting parentheses (i.e. giving a pretty slow-paced introduction) * Understanding how Scheme is hooked into LilyPond (on a general level) * (Learning how openLilyLib ist structured) * Learning how to retrieve the relevant information about score elements and how to modify them in appropriate places. The last one is probably the hardest one since it is pretty opaque and terribly documented. But it's the crucial one for a contemporary notation package - and it's the one where such a package will make it hugely easier for people to work with non-standard notation. Just last week I've decided to start with a new openLilyLib package: https://github.com/openlilylib/grob-tools. The repository on Github is empty, and right now I only have one single uncommited function locally, but the idea is to create building blocks for recurring tasks like getting the exact position of objects relative to the staff or to another object, enumerating all NoteColumns included in a slur or similar things. This will be very much relevant for a contemporary notation package. One could either say that you should put much of your results in that package, or we can try to make development of that package a community effort so that would take work from you, giving you the freedom to go further with the specific challenges. ### What you should do now is: * [of course dive more into Scheme] * get an understanding of openLilyLib with a) https://github.com/openlilylib/oll-core/wiki b) the code in that repository c) looking at how other openLilyLib packages are built within that infrastructure * Form an idea how a contemporary notation package could be approached and discuss that with us * Find some small things you could do to openLilyLib package(s) to a) practice and b) give us an opportunity to assess your work. If we have some idea about your current familiarity with the matter we can
