tree f2d58391ed2eacad6d553571a8b14046792704d4
parent 008b388147b5de1b4994919693aaca3734d97c4f
author Naveen Kaje <naveen.kaje@juul.com> 1570816715 -0500
committer ccollins476ad <ccollins476ad@gmail.com> 1571092453 -0700

newt upgrade: Fix Repo Commit Checkout

Checking out various repositories to a particular set of commit versions

is broken. Fix this by looking at the dependency graph's node's
required versions.

Example Usage in repository.yml

```
repo.versions:
    "0.0.0" : "master"
    "1.0.0" : "release_1_0_0"

repo.deps:
    apache-mynewt-core:
        type: git
        url: git@github.com:apache/mynewt-core.git
        vers:
            master: 0-dev
            release_1_0_0: 'f3d0ff2ab8db0da99f6b35938caf25c36950e181-commit'

    apache-mynewt-nimble:
        type: git
        url: git@github.com:apache/mynewt-nimble.git
        vers:
            master: 0-dev
            release_1_0_0: '7624744d90c159b8c9ab0bf3d890b0c3a3c43928-commit'
```

Note that the version specifier (such as `release_1_0_0`) can be a tag.
The project that houses this repository.yml gets checked out to
`release_1_0_0` and the dependencies get checked out to the versions
specified as shown above.

Signed-off-by: Naveen Kaje <naveen.kaje@juul.com>