----- Original Message -----
From: "David Kastrup" <d...@gnu.org>
To: "Phil Holmes" <m...@philholmes.net>
Cc: "John Mandereau" <john.mander...@gmail.com>; "Lily devel"
<lilypond-devel@gnu.org>
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" <m...@philholmes.net> writes:
----- Original Message -----
From: "David Kastrup" <d...@gnu.org>
To: "Phil Holmes" <m...@philholmes.net>
Cc: "John Mandereau" <john.mander...@gmail.com>; "Lily devel"
<lilypond-devel@gnu.org>
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" <m...@philholmes.net> writes:
----- Original Message -----
From: "David Kastrup" <d...@gnu.org>
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
