Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]

[Knut Petersen]

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