Hi @calbzam,
I just retested this with the latest version (cm version => 11.0.16.7608), and the issue is still present.
Our repo's are
- "Development Fellowship Shared" (which is succesfully synced with Github using SSH)
- "Development Organimmo Cloud V2" (which contains an xlink to the above repo, but fails)
The output/error we get is:
PS Z:\SCM\OrganimmoCloud> cm sync "Development Organimmo Cloud V2@Organimmo@cloud" git git@github.com:Organimmo/OXPortal.git
Receiving references... /
- /main: Local changes
... (branches removed for brevity)
- 0 changesets to pull
- 3392 changesets to push
Receiving references... OK
There are changes to push.
The equivalent Git repository for 'Development Fellowship Shared@Organimmo@cloud' has not been defined. The xlink cannot be pushed. Please add the equivalence inside the submodules section in the configuration file 'C:\Program Files\PlasticSCM5\client\gitsync.conf'.
gitsync.conf:
[email-mapping]
person1 = person1@ourcompany.tld
person2 = person2@ourcompany.tld
[submodules]
#ignore.xlinkRepository=Development Fellowship Shared
#git://github.com/Organimmo/FellowshipShared.git -> Development Fellowship Shared@Organimmo@cloud writable:false relativeserver:true
#git://github.com/Organimmo/FellowshipShared.git -> Development%20Fellowship%20Shared@Organimmo@cloud writable:false relativeserver:true
#git://github.com/Organimmo/FellowshipShared.git -> 'Development Fellowship Shared@Organimmo@cloud' writable:false relativeserver:true
git://github.com/Organimmo/FellowshipShared.git -> "Development Fellowship Shared@Organimmo@cloud" writable:false relativeserver:true
#git://github.com/Organimmo/FellowshipShared.git -> "Development Fellowship Shared@Organimmo@cloud"
- this is the original file, but email-mapping anonymized
- all mappings shown above under submodules are failing, with the exact same error.
- the "workaround" with ignore.xlinkRepository is succeeding, but renders the xlink/submodules functionality useless.
So my question is:
- If the above syntax for specifying spaces is wrong, what do we need to use?
- If the above syntax for specifying spaces is correct, could you please fix this bug?
- If this is a bug, and you are short on resources to get this fixed, is it possible to open up the gitsync logic?
Thanks for helping us with this. We are a "Plastic Cloud" customer, trying to open up (one-way) a "sample-part" of our code to specific customers using GIT.
Best regards,
Wim
