Re: newest BSP on OSX

[Dr. Juergen Kienhoefer]

Thank you very much, that did it. On MacOS this gets only the old 1.5.0
version with no way to upgrade to 1.7.0

$ brew tap JuulLabs-OSS/mynewt
$ brew install mynewt-newt


Installing the newt binary from your link got the latest 1.7.0 version and
I was able to upgrade and build an example for the Dialog chip.
Cheers


On Mon, Aug 5, 2019 at 2:12 PM Christopher Collins  wrote:

> Hi Juergen,
>
> Run the following:
>
> newt upgrade && newt sync
>
> (instead of `newt install`).  This will download updates for those
> Mynewt repos.
>
> You might also need to upgrade your version of the newt tool.  I am not
> sure how the brew distribution gets updated, but it looks like we have
> fallen behind here.  I will look into getting this updated today.  In
> the meantime, you can download the 1.7.0 macOS binary here:
> https://www.apache.org/dyn/closer.lua/mynewt/apache-mynewt-1.7.0/
>
> (click the top link, then `apache-mynewt-newt-bin-osx-1.7.0.tgz`).
>
> Chris
>
> On Mon, Aug 05, 2019 at 12:53:08PM -0700, Dr. Juergen Kienhoefer wrote:
> > Hi, I was wondering how I can get the latest BSP on a MacOS installation.
> > Installing newt with brew gets version 1.5.0. The bsp is in 1.7.0
> >
> > newt install
> >
> > Skipping "apache-mynewt-core": already installed (1.5.0)
> >
> > Skipping "mcuboot": already installed (0.0.0)
> >
> > Skipping "apache-mynewt-nimble": already installed (1.0.0)
> >
> > Skipping "mynewt_arduino_zero": already installed (0.0.0)
> >
> >
> > then
> >
> >
> > newt target set mytarget
> > bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
> >
> > newt build mytarget
> >
> >
> > gets me that error:
> >
> > Error: Could not resolve BSP package:
> > @apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
> >
> >
> > my project file:
> >
> > repository.apache-mynewt-core:
> >
> > type: github
> >
> > vers: 1-latest
> >
> > user: apache
> >
> > repo: mynewt-core
> >
> >
> > Still does not give me that BSP.
> >
> >
> > Any suggestions would be appreciated.
>

Re: Deprecate "install" and "sync" commands?

[Vipul Rahane]

Hi Chris,

We always needed that. I like 2 better than 3 just because of backwards
compatibility.

3 seems fine as well just that CI setups/scripts will have to change
accordingly.

Regards,
Vipul Rahane

On Mon, Aug 5, 2019 at 2:08 PM Łukasz Rymanowski <
lukasz.rymanow...@codecoup.pl> wrote:

> Hi Chris,
>
> I'm with you on 3)
>
> Best
> Łukasz
>
> On Mon, 5 Aug 2019 at 22:59, Fabio Utzig  wrote:
> >
> >
> > On Mon, Aug 5, 2019, at 3:30 PM, Szymon Janc wrote:
> > > Hi Chris,
> > >
> > > Yes!  I'm also for option 3. Lets deprecate for next (1.8) release
> (make
> > > those print proper warning info when used) and just remove for 1.9.
> >
> > +1
>
-- 

Regards,
Vipul Rahane

Re: newest BSP on OSX

[Christopher Collins]

Hi Juergen,

Run the following:

newt upgrade && newt sync

(instead of `newt install`).  This will download updates for those
Mynewt repos.

You might also need to upgrade your version of the newt tool.  I am not
sure how the brew distribution gets updated, but it looks like we have
fallen behind here.  I will look into getting this updated today.  In
the meantime, you can download the 1.7.0 macOS binary here:
https://www.apache.org/dyn/closer.lua/mynewt/apache-mynewt-1.7.0/

(click the top link, then `apache-mynewt-newt-bin-osx-1.7.0.tgz`).

Chris

On Mon, Aug 05, 2019 at 12:53:08PM -0700, Dr. Juergen Kienhoefer wrote:
> Hi, I was wondering how I can get the latest BSP on a MacOS installation.
> Installing newt with brew gets version 1.5.0. The bsp is in 1.7.0
> 
> newt install
> 
> Skipping "apache-mynewt-core": already installed (1.5.0)
> 
> Skipping "mcuboot": already installed (0.0.0)
> 
> Skipping "apache-mynewt-nimble": already installed (1.0.0)
> 
> Skipping "mynewt_arduino_zero": already installed (0.0.0)
> 
> 
> then
> 
> 
> newt target set mytarget
> bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
> 
> newt build mytarget
> 
> 
> gets me that error:
> 
> Error: Could not resolve BSP package:
> @apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
> 
> 
> my project file:
> 
> repository.apache-mynewt-core:
> 
> type: github
> 
> vers: 1-latest
> 
> user: apache
> 
> repo: mynewt-core
> 
> 
> Still does not give me that BSP.
> 
> 
> Any suggestions would be appreciated.

Re: Deprecate "install" and "sync" commands?

[Łukasz Rymanowski]

Hi Chris,

I'm with you on 3)

Best
Łukasz

On Mon, 5 Aug 2019 at 22:59, Fabio Utzig  wrote:
>
>
> On Mon, Aug 5, 2019, at 3:30 PM, Szymon Janc wrote:
> > Hi Chris,
> >
> > Yes!  I'm also for option 3. Lets deprecate for next (1.8) release (make
> > those print proper warning info when used) and just remove for 1.9.
>
> +1

Re: Deprecate "install" and "sync" commands?

[Fabio Utzig]

On Mon, Aug 5, 2019, at 3:30 PM, Szymon Janc wrote:
> Hi Chris,
> 
> Yes!  I'm also for option 3. Lets deprecate for next (1.8) release (make
> those print proper warning info when used) and just remove for 1.9.

+1

newest BSP on OSX

[Dr. Juergen Kienhoefer]

Hi, I was wondering how I can get the latest BSP on a MacOS installation.
Installing newt with brew gets version 1.5.0. The bsp is in 1.7.0

newt install

Skipping "apache-mynewt-core": already installed (1.5.0)

Skipping "mcuboot": already installed (0.0.0)

Skipping "apache-mynewt-nimble": already installed (1.0.0)

Skipping "mynewt_arduino_zero": already installed (0.0.0)


then


newt target set mytarget
bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro

newt build mytarget


gets me that error:

Error: Could not resolve BSP package:
@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro


my project file:

repository.apache-mynewt-core:

type: github

vers: 1-latest

user: apache

repo: mynewt-core


Still does not give me that BSP.


Any suggestions would be appreciated.

Re: Deprecate "install" and "sync" commands?

[Szymon Janc]

Hi Chris,

Yes!  I'm also for option 3. Lets deprecate for next (1.8) release (make
those print proper warning info when used) and just remove for 1.9.




On Mon, 5 Aug 2019 at 18:47, Christopher Collins  wrote:

> Hello all,
>
> The newt tool supports three "project commands":
>
> * install
> * upgrade
> * sync
>
> I always have a hard time remembering the particulars of commands like
> these.  For example, when other package management systems support both
> "update" and "upgrade", I inevitably mix them up.  I propose we remove
> "install" and "sync", reducing the list to just one command.
>
> First, here is a refresher for each of these three commands:
>
> INSTALL: Downloads repos that aren't installed yet.  The downloaded
> version matches what `project.yml` specifies.
>
> UPGRADE: Performs an INSTALL, and then ensures the installed version of
> each repo matches what `project.yml` specifies.  This is similar to
> INSTALL, but it also operates on already-installed repos.
>
> SYNC: Fetches and pulls the latest for each repo, but does not change
> the branch (version).  Only necessary for Mynewt repo versions that
> point to a git branch (e.g., 0.0.0 usually points to "master").
>
> The distinction between these commands is somewhat subtle, so please
> ask if it isn't clear.
>
> I would like to remove INSTALL and SYNC.  I propose we do this as
> follows:
>
> A. Remove SYNC:
> A recent newt change allows us to deprecate SYNC:
> https://github.com/apache/mynewt-newt/pull/312.  With this change,
> `newt upgrade` always grabs the latest commit for repos with
> branch-versions.  So UPGRADE now subsumes SYNC.
>
> B. Remove INSTALL:
> I have never found the INSTALL to be very useful.  I find it easier to
> simply use UPGRADE instead.  It's just my experience, but there is never
> a time when I want to install new repos without updating existing ones.
> If you don't want to upgrade existing repos, then you can just not
> change their versions in `project.yml`.
>
> Alternatively, we don't have to go so far as to deprecate and remove
> these commands.  We could keep them, but just make them synonyms for
> `upgrade`.  This is a less disruptive option.
>
> So I see three options:
>
> 1. Change nothing.
> 2. Make "install" and "sync" synonyms for "upgrade".
> 3. Deprecate "install" and "sync"
>
> My vote is for 3, but I would be happy with 2.
>
> Thoughts?
>
> Chris
>


-- 
pozdrawiam
Szymon K. Janc

Deprecate "install" and "sync" commands?

[Christopher Collins]

Hello all,

The newt tool supports three "project commands":

* install
* upgrade
* sync

I always have a hard time remembering the particulars of commands like
these.  For example, when other package management systems support both
"update" and "upgrade", I inevitably mix them up.  I propose we remove
"install" and "sync", reducing the list to just one command.

First, here is a refresher for each of these three commands:

INSTALL: Downloads repos that aren't installed yet.  The downloaded
version matches what `project.yml` specifies.

UPGRADE: Performs an INSTALL, and then ensures the installed version of
each repo matches what `project.yml` specifies.  This is similar to
INSTALL, but it also operates on already-installed repos.

SYNC: Fetches and pulls the latest for each repo, but does not change
the branch (version).  Only necessary for Mynewt repo versions that
point to a git branch (e.g., 0.0.0 usually points to "master").

The distinction between these commands is somewhat subtle, so please
ask if it isn't clear.

I would like to remove INSTALL and SYNC.  I propose we do this as
follows:

A. Remove SYNC:
A recent newt change allows us to deprecate SYNC:
https://github.com/apache/mynewt-newt/pull/312.  With this change,
`newt upgrade` always grabs the latest commit for repos with
branch-versions.  So UPGRADE now subsumes SYNC.

B. Remove INSTALL:
I have never found the INSTALL to be very useful.  I find it easier to
simply use UPGRADE instead.  It's just my experience, but there is never
a time when I want to install new repos without updating existing ones.
If you don't want to upgrade existing repos, then you can just not
change their versions in `project.yml`.

Alternatively, we don't have to go so far as to deprecate and remove
these commands.  We could keep them, but just make them synonyms for
`upgrade`.  This is a less disruptive option.

So I see three options:

1. Change nothing.
2. Make "install" and "sync" synonyms for "upgrade".
3. Deprecate "install" and "sync"

My vote is for 3, but I would be happy with 2.

Thoughts?

Chris

Download page

[Private List Moderation]

Hi,

I've accepted this announcement, and for future releases, please change all of 
the links on the download page to be https: instead of http:. The checksums and 
signatures already have the correct https prefix and the artifact links should 
too.

Regards,

Craig

> Begin forwarded message:
> 
> From: announce-reject-1565008365.32381.algijjojijfmhlfak...@apache.org
> Subject: MODERATE for annou...@apache.org
> Date: August 5, 2019 at 5:32:45 AM PDT
> To: Recipient list not shown: ;
> Cc: 
> announce-allow-tc.1565008365.elmcccommemccjfpbnkj-janc=apache@apache.org
> Reply-To: announce-accept-1565008365.32381.algijjojijfmhlfak...@apache.org
> 
> 
> To approve:
>   announce-accept-1565008365.32381.algijjojijfmhlfak...@apache.org
> To reject:
>   announce-reject-1565008365.32381.algijjojijfmhlfak...@apache.org
> To give a reason to reject:
> %%% Start comment
> %%% End comment
> 
> 
> From: Szymon Janc 
> Subject: [ANNOUNCE] Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0 released
> Date: August 5, 2019 at 5:32:42 AM PDT
> To: dev@mynewt.apache.org, annou...@apache.org
> 
> 
> Hello all,
> 
> The Apache Mynewt team is pleased to announce the release of
> Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0.
> 
> Apache Mynewt is a community-driven module OS for constrained, embedded
> applications.  Mynewt provides a real-time operating system, flash file
> system, network stacks, and support utilities for real-world embedded
> systems.
> 
> The releases are available here:
> http://mynewt.apache.org/download/
> 
> Release notes for Apache Mynewt are available here:
> https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.7.0
> 
> Release notes for Apache NimBLE are available here:
> https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.2.0
> 
> We welcome your help and feedback. For more information on the project
> and how to get involved, visit the project website at
> http://mynewt.apache.org/
> 
> Regards,
> The Apache Mynewt team
> 
> 
> 
> 
> 

Craig L Russell
Assistant Secretary, Apache Software Foundation
c...@apache.org  http://db.apache.org/jdo 

[ANNOUNCE] Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0 released

[Szymon Janc]

Hello all,

The Apache Mynewt team is pleased to announce the release of
Apache Mynewt 1.7.0 and Apache NimBLE 1.2.0.

Apache Mynewt is a community-driven module OS for constrained, embedded
applications.  Mynewt provides a real-time operating system, flash file
system, network stacks, and support utilities for real-world embedded
systems.

The releases are available here:
http://mynewt.apache.org/download/

Release notes for Apache Mynewt are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.7.0

Release notes for Apache NimBLE are available here:
https://cwiki.apache.org/confluence/display/MYNEWT/RN-NimBLE-1.2.0

We welcome your help and feedback. For more information on the project
and how to get involved, visit the project website at
http://mynewt.apache.org/

Regards,
The Apache Mynewt team