|
From: | Phil Holmes |
Subject: | Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch] |
Date: | Thu, 21 Mar 2019 11:04:04 -0000 |
To: "Phil Holmes" <address@hidden>Cc: "John Mandereau" <address@hidden>; "Lily devel" <address@hidden>
Sent: Thursday, March 21, 2019 10:58 AMSubject: Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]
"Phil Holmes" <address@hidden> writes:----- Original Message ----- From: "David Kastrup" <address@hidden>[...]I believe GUB upload uses rsync.Then it depends on the options used. Some versionsOops. Some optionsof 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
[Prev in Thread] | Current Thread | [Next in Thread] |