David,

I've tried what you suggested I'm getting this error:

*apache-mynewt-core**
**Error: Get https://api.github.com/repos/apache/incubator-mynewt-core/contents/repository.yml?ref=master: dial tcp: lookup api.github.com on 10.0.2.3:53: read udp 172.17.0.2:38728->10.0.2.3:53: i/o timeout*


My project file looks like this now:

project.name: "my_project"

project.repositories:
    - apache-mynewt-core

# Use github's distribution mechanism for core ASF libraries.
# This provides mirroring automatically for us.
#
repository.apache-mynewt-core:
    type: github
    vers: 0-dev
    user: apache
    repo: incubator-mynewt-core


Am I missing something?

Thanks,
Cris

On 1/6/2017 12:05 PM, David G. Simmons wrote:
You could do that, but if you don't want to remake the whole Docker instance, 
you should be able to simply edit the project.yml file and change the vers 
strin for repository.apache-mynewt-core to 0-dev and then run newt install

Best regards,
dg

On Jan 6, 2017, at 5:23 AM, Fabio Utzig <[email protected]> wrote:

I'm not using the docker version myself, but I think you could try
rebuilding the docker image:

https://github.com/runtimeinc/newt-docker 
<https://github.com/runtimeinc/newt-docker>

Inside the Makefile, change the branch that is checked out from "-b
mynewt_1_0_0_b1_tag" to "-b develop":

https://github.com/runtimeinc/newt-docker/blob/master/Makefile#L15 
<https://github.com/runtimeinc/newt-docker/blob/master/Makefile#L15>

Att,
Fabio Utzig
--
David G. Simmons
(919) 534-5099
Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • Linkedin 
<http://linkedin.com/in/davidgsimmons> • Twitter <http://twitter.com/TechEvangelist1> • GitHub 
<http://github.com/davidgs>
/** Message digitally signed for security and authenticity.
* If you cannot read the PGP.sig attachment, please go to
  * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!!
  * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/>
**/
♺ This email uses 100% recycled electrons. Don't blow it by printing!

There are only 2 hard things in computer science: Cache invalidation, naming 
things, and off-by-one errors.




Reply via email to