vcs export fails to add nesting path prefix to nested repos

Starting with an existing nested repository structure in ~/dev:

repository-group
├── .git
├── nested-repo-one
│   └── .git
└── nested-repo-two
    └── .git

and running

~/dev $ vcs export --nested repository-group

the result is

repositories:
  repository-group:
    type: git
    url: https://<url>.git
    version: master
  nested-repo-one:
    type: git
    url: https://<url>.git
    version: develop
  nested-repo-two:
    type: git
    url: https://<url>.git
    version: develop

but should be

repositories:
  repository-group:
    type: git
    url: https://<url>.git
    version: master
  repository-group/nested-repo-one:
    type: git
    url: https://<url>.git
    version: develop
  repository-group/nested-repo-two:
    type: git
    url: https://<url>.git
    version: develop

I had forgotten about the export command for a while. @dirk-thomas thanks for reminding me. Since we use nested repos in the IHMC build framework, this breaks that convenience for me. I’m guessing it’s an easy fix. 😄

[calvertdw]

Whew.

A source setup.sh did the trick. For some reason I was doing ./setup.sh so the environment changes died with the process. 😅 It’s a Monday.

It worked! The paths prefix correctly and I got my print message. Thanks!

[dirk-thomas]

I wouldn’t recommend to install a version for testing using sudo. Instead you could use a virtual env.

When you invoke vcs-export directly you need to extend the PYTHONPATH to contain the directory of this repository so that it picks up the modified Python modules.

The version number wouldn’t be different on the branch - it is still the same as the latest released version.

You might want to add a simple print call in the export function to confirm that you are actually using the code from the custom branch.