Updating the project.yml file to point to 0.0.1 resolved this, and a
clean setup now pulls master instead of develop.
I agree minimum version checks would be extremely useful, though, since
the newt/newtmgr tools and apache-mynewt-core are quite tightly coupled.
On 05/12/16 18:29, Kevin
Hi Chris,
Thanks for the reply. I usually pull the tools and mynewt core at the
same time. We're running the latest version of both repos from master,
or at least that's what I thought ... it seems when I did a 'newt
install -v' we ended up in 'develop' in repos/apache-mynewt-core
This is
Hi Kevin,
This issue tends to happen if you are using a version of newt that is
incompatible with your core repo. You mentioned you are using the
master branch of core; is it possible that you are using develop of the
newt repo?
Specifically, I think this issue is caused by this commit from
Just as a follow up, for some reason a clean install set me to 'develop'
not 'master', though it isn't clear to me why yet ... but this resolves
the issue with the missing config file:
* cd repos
* cd apache-mynewt-core
* git branch # To show that I'm on develop not master which is what I
