Yeah, it looks like that file hasn't been touched since May, and the version string hasn't been changed. I'm going to guess that's an oversight and/or a bug. :-)
Thanks! dg > On Oct 7, 2016, at 10:25 AM, Kevin Townsend <[email protected]> wrote: > > I haven't tried 0.10.0 but it's probably in the source. > > It seems to be defined here so you can look at that file: > https://github.com/apache/incubator-mynewt-newtmgr/blob/develop/newt/newtutil/newtutil.go > > K. > > On 07/10/16 16:22, David G. Simmons wrote: >> Outstanding! Thanks. Am I to understand then that the version number has not >> changed and should still report 0.9.0 after this? I would think that it >> would give me 0.10.0 >> >> % git branch >> * develop >> master >> % git checkout >> Your branch is up-to-date with 'origin/0_10_0_dev >> % go install >> % newt >> Apache Newt (incubating) version: 0.9.0 >> >> dg >> >>> On Oct 7, 2016, at 10:10 AM, Kevin Townsend <[email protected]> wrote: >>> >>> Hi David, >>> >>> These are the notes I made for myself on updating newt and newtmgr: >>> >>> # Updating `newt` and `newtmgr` >>> >>> To update the `newt` and `newtmgr` tools: >>> >>> - Go to `$GOPATH/src/mynewt.apache.org/newt/` >>> - Run `git pull` to get the latest source code for the tools >>> - Switch branches if necessary (ex. `git checkout develop`) >>> - Go into the `newtmgr` sub-folder >>> - Run `go install` >>> - Repeat the process from the `newt` and `newtvm` folders >>> >>> This will cause the tools in $GOPATH/bin to be rebuilt, which you can see >>> by running `ls -l $GOPATH/bin` >>> >>> K. >>> >>> >>> On 07/10/16 16:07, David G. Simmons wrote: >>>> Hi all, >>>> >>>> I know there must be an easy way to do this, but I haven't found it yet. >>>> >>>> I'm trying to get newt up to the latest version in the develop branch. >>>> Here's what I've done so far: >>>> >>>> % cd /Users/dsimmons/dev/go/src/mynewt.apache.org/newt >>>> <http://mynewt.apache.org/newt> >>>> % newt version >>>> Apache Newt (incubating) version: 0.9.0 >>>> % git branch --set-upstream-to=origin/0_10_0_dev >>>> Branch develop set up to track remote branch 0_10_0_dev from origin. >>>> % git rebase >>>> Fast-forwarded develop to refs/remotes/origin/0_10_0_dev. >>>> % git pull >>>> Already up-to-date. >>>> >>>> That last part doesn't seem right to me. >>>> >>>> % ./build.sh >>>> Building newt. This may take a minute... >>>> Successfully built executable: >>>> /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt >>>> <http://mynewt.apache.org/newt/newt/newt> >>>> $ /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt >>>> <http://mynewt.apache.org/newt/newt/newt> version >>>> Apache Newt (incubating) version: 0.9.0 >>>> >>>> And that part definitely isn't right. >>>> >>>> If I can get some help in how to actually update newt, then I'll write up >>>> a doc on how to do it for others. >>>> >>>> dg >>>> -- >>>> 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. >>>> >>>> >>>> >> -- >> 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. >> >> >> > -- 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.
