|
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 10:52:08 -0000 |
To: "Phil Holmes" <address@hidden>Cc: "John Mandereau" <address@hidden>; "Lily devel" <address@hidden>
Sent: Thursday, March 21, 2019 10:24 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>To: "Phil Holmes" <address@hidden> Cc: "John Mandereau" <address@hidden>; "Lily devel" <address@hidden> 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" <address@hidden> writes:----- Original Message ----- From: "David Kastrup" <address@hidden>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
[Prev in Thread] | Current Thread | [Next in Thread] |