Re: Newbie & running into an error during setup

[todd mitton]

Ok.  Thanks Mohammad.

On Wed, Dec 7, 2016 at 9:47 PM, Mohammad Afaneh <mafa...@gmail.com> wrote:

> Todd, unfortunately I don't have the environment set up. However, I was
> getting the same errors as before:
>
> Error: No testable packages found
>
> Error: Package @apache-mynewt-core/sys/config contains no unit tests
>
> - Mohammad
>
> On Wed, Dec 7, 2016 at 2:22 PM, todd mitton <mit...@runtime.io> wrote:
>
> > Glad the native install is working for you.
> >
> > The updated docker container should have worked though.  Could you paste
> in
> > the test failure if you still have it available?  I'm curious why it
> didn't
> > work.
> >
> > Thanks,
> > -Todd
> >
> > On Tue, Dec 6, 2016 at 7:31 PM, Mohammad Afaneh <mafa...@gmail.com>
> wrote:
> >
> > > Even after that update, the unit tests were still not working. The
> > > directory structure however, I was confused about - the folders I was
> > > looking at in the documentation are in the "repos/apache-mynewt-core",
> > not
> > > the root folder (so I have all the folders).
> > >
> > > I ended up doing a native install instead of the docker method and
> > > everything is working okay.
> > >
> > > Thanks for everyone's help.
> > >
> > > - Mohammad
> > >
> > > On Tue, Dec 6, 2016 at 6:00 PM, todd mitton <mit...@runtime.io> wrote:
> > >
> > > > The docker container has been updated for version 1.0.0-b1.  Run
> > `docker
> > > > pull mynewt/newt:latest` to get the updated version.  Make sure `newt
> > > > version` shows 1.0.0-b1.  That version is working for me.
> > > >
> > > > Thanks,
> > > > -Todd
> > > >
> > > > On Tue, Dec 6, 2016 at 12:13 PM, David G. Simmons <santa...@mac.com>
> > > > wrote:
> > > >
> > > > > I'm looking into this, and here's what happens when I do what is
> > > > described
> > > > > in the docs (by copy/paste from the doc to my terminal on OS X
> > Sierra)
> > > > >
> > > > > TL;DR: There is a major malfunction in running any of the tests:
> > > > > In file included from aes.c:29:0:
> > > > > /Users/dsimmons/test_newt/myproj/repos/apache-mynewt-
> > > > > core/crypto/mbedtls/include/mbedtls/config.h:2522:10: error:
> > #include
> > > > > expects "FILENAME" or 
> > > > >  #include MBEDTLS_USER_CONFIG_FILE
> > > > >
> > > > > Read on to see (if you're interested) how the docs differ from the
> > > actual
> > > > > output (tl;dr: They don't :-) )
> > > > >
> > > > > dsimmons$ newt new myproj
> > > > > Downloading project skeleton from apache/incubator-mynewt-
> blinky...
> > > > > Installing skeleton in myproj...
> > > > > Project myproj successfully created.
> > > > > DSimmons-Pro:test_newt dsimmons$ cd myproj/
> > > > > DSimmons-Pro:myproj dsimmons$ tree
> > > > > .
> > > > > ├── DISCLAIMER
> > > > > ├── LICENSE
> > > > > ├── NOTICE
> > > > > ├── README.md
> > > > > ├── apps
> > > > > │   └── blinky
> > > > > │   ├── pkg.yml
> > > > > │   └── src
> > > > > │   └── main.c
> > > > > ├── project.yml
> > > > > └── targets
> > > > > ├── my_blinky_sim
> > > > > │   ├── pkg.yml
> > > > > │   └── target.yml
> > > > > └── unittest
> > > > > ├── pkg.yml
> > > > > └── target.yml
> > > > >
> > > > > 6 directories, 11 files
> > > > > dsimmons$ newt install -v
> > > > > apache-mynewt-core
> > > > > Downloading repository description for apache-mynewt-core...
> > > > >  success!
> > > > > Downloading repository incubator-mynewt-core (branch: master;
> commit:
> > > > > mynewt_1_0_0_b1_tag) at https://github.com/apache/
> > > > > incubator-mynewt-core.git
> > > > > Cloning into '/var/folders/_l/m5h3k18x0x3f6422p12_
> cpchgp/T/newt-
> > > > > repo730366949'...
> > > > > remote: Counting objects: 45144, done.
> > > > > remote: Compressing objects: 100% (150/150), done.
> > > > > remote: Total 45144 (delta

Re: Newbie & running into an error during setup

[todd mitton]

Hi Mohammad,

I don't think there's a problem.  You should only have the apps, repos, and
targets directly after a `newt new` and `newt install`.  That's expected.
If you look in repos/apache-mynewt-core, you should see all the src for
Mynewt.

The 'warning: unable to access '/root/.config/git/attributes': Permission
denied' message is just a harmless warning from git.  You only see it with
the -v flag.  It just means there's no /root/.config/git/attributes in the
container.

-Todd

On Tue, Dec 6, 2016 at 8:24 AM, marko kiiskila  wrote:

> I have a Linux setup running under VmWare, where I have a mynewt
> dev environment. This is quite possible.
>
> Docker is more of a convenience thing :)
>
> > On Dec 5, 2016, at 2:32 AM, Mohammad Afaneh  wrote:
> >
> > Thanks, Fabio.
> >
> > Yes, I'm aware that I can install on OS X - I just like to keep things
> > isolated in a VM when trying out new projects and frameworks.
> >
> > I guess I'll resort to setting up on my native OS if I don't succeed in
> > getting it working.
> >
> > - Mohammad
> >
> > On Mon, Dec 5, 2016 at 5:05 AM, Fabio Utzig  wrote:
> >
> >> On Sun, Dec 4, 2016, at 10:55 PM, Mohammad Afaneh wrote:
> >>> Thanks, Chris.
> >>>
> >>> I'm running:
> >>> - OS X 10.12.1 (macOS Sierra)
> >>
> >> Hi Mohammad,
> >>
> >> Not sure you are aware but you can build newt/mynewt on OS X too. I'm
> >> myself using Sierra for development. You just need to install some
> >> dependencies like go and gcc-arm-embedded. Easily done with homebrew:
> >>
> >> $ brew install go
> >> $ brew cask install gcc-arm-embedded
> >>
> >> Cheers,
> >> Fabio Utzig
> >>
>
>

Re: Arduino Zero/M0 Pro default serial connection changed

[todd mitton]

Cool.  Works now.  The cause of my problem was VirtualBox mapping the
device into the VM used by docker.

On Thu, Jun 30, 2016 at 10:24 AM, p...@wrada.com <p...@wrada.com> wrote:

> The Edbg serial port build into the arduino zero debug is a cdc serial
> port (not FTDI). Linux and Mac should have support but Windows requires
> some additional drivers
>
> > On Jun 30, 2016, at 10:20 AM, marko kiiskila <ma...@runtime.io> wrote:
> >
> > Hi Todd,
> >
> > my MAC is using USB CDC driver for this, and it names the tty’s as
> > /dev/tty.usbmodemXXX.
> >
> >> On Jun 30, 2016, at 10:01 AM, todd mitton <mit...@runtime.io> wrote:
> >>
> >> I know I'm using the correct port and cable because I'm able to load new
> >> images using newt.  I bet my problem is the USB device is mapped into
> the
> >> virtual machine that's used to run docker containers.
> >>
> >>> On Wed, Jun 29, 2016 at 10:00 PM, Brian Giori <briangi...@gmail.com>
> wrote:
> >>>
> >>> First make sure you're connected to the programming microusb port and
> not
> >>> the native one. If you can't see a new tty look for a cu. I have heard
> of
> >>> some microusb cables providing power only so if all else fails try a
> new
> >>> cable.
> >>>
> >>>> On Wed, Jun 29, 2016 at 8:39 PM, todd mitton <mit...@runtime.io>
> wrote:
> >>>>
> >>>> What /dev device do I use?  I don't seem to get any new tty to talk
> to.
> >>>>
> >>>> Thanks,
> >>>> -Todd
> >>>>
> >>>>> On Wed, Jun 29, 2016 at 3:15 PM, Gavin Jefferies <ga...@vmbed.com>
> >>>> wrote:
> >>>>
> >>>>> Cool! Thanks Brian.
> >>>>> -G
> >>>>>
> >>>>> On Wed, Jun 29, 2016 at 3:08 PM, Brian Giori <briangi...@gmail.com>
> >>>> wrote:
> >>>>>> Hey everyone,
> >>>>>>
> >>>>>> I recently changed the Arduino Zero/M0 Pro's default serial
> >>> connection
> >>>> to
> >>>>>> use the micro USB debugging port rather than the RX-0 and TX-1 pins.
> >>>>>>
> >>>>>> Here's the change:
> >>>>>> https://github.com/runtimeinc/mynewt_arduino_zero/pull/2
> >>>>>>
> >>>>>> Now you can ditch that FTDI cable :)
> >>>>>>
> >>>>>> Brian
> >
>

Re: Arduino Zero/M0 Pro default serial connection changed

[todd mitton]

What /dev device do I use?  I don't seem to get any new tty to talk to.

Thanks,
-Todd

On Wed, Jun 29, 2016 at 3:15 PM, Gavin Jefferies  wrote:

> Cool! Thanks Brian.
> -G
>
> On Wed, Jun 29, 2016 at 3:08 PM, Brian Giori  wrote:
> > Hey everyone,
> >
> > I recently changed the Arduino Zero/M0 Pro's default serial connection to
> > use the micro USB debugging port rather than the RX-0 and TX-1 pins.
> >
> > Here's the change:
> > https://github.com/runtimeinc/mynewt_arduino_zero/pull/2
> >
> > Now you can ditch that FTDI cable :)
> >
> > Brian
>

Re: installing the Newt

[todd mitton]

I should have said that new users will be able to 'go get
mynewt.apache.org/newt/...' once Chris's changes have been merged onto
master.

On Thu, Mar 3, 2016 at 10:53 AM, todd mitton <mit...@runtime.io> wrote:

> Sorry.  I was waiting to switch to the vanity import domain until all the
> other rename changes were done.  I didn't realize we were ready.
>
> New users can now do this:
>
> go get mynewt.apache.org/newt/newt
> go get mynewt.apache.org/newt/newtmgr
> go get mynewt.apache.org/newt/newtvm
>
> The user won't need to manually clone the repo.  go get will clone it into
> $GOPATH/src/mynewt.apache.org/newt.  By default the user will be on the
> master branch. If the user wishes to be on develop, they can:
>
> cd $GOPATH/src/mynewt.apache.org/newt
> git checkout develop
>
> -Todd
>
> On Wed, Mar 2, 2016 at 11:46 PM, Christopher Collins <ch...@runtime.io>
> wrote:
>
>> I have committed the changes to the develop branch.  Now all go imports
>> use the vanity domain.
>>
>> Unfortunately, this is going cause a bit of pain for the current users
>> because the newt sources are now in the wrong directory.  To correct
>> this problem, you will need to move the old newt path to the new one:
>>
>> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>>   mv $GOPATH/src/
>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
>> mynewt.apache.org/newt
>>
>> If you plan on building older versions of newt, you should link the path
>> rather than move it:
>>
>> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>>   ln -s $GOPATH/src/
>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
>> mynewt.apache.org/newt
>>
>> Sorry for the hassle.  Yes, we definitely need to include convenience
>> binaries in the next release :).
>>
>> Chris
>>
>> On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
>> > Nice!  That seems to work.  I guess I completely glossed over those
>> > vanity URL emails.  I will make the necessary changes to the develop
>> > branch.  Unfortunately, I'm afraid it is too late to fix 0.8.0-b1.
>> >
>> > Chris
>> >
>> > On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
>> > >
>> > > >
>> > > > When pointed at the apache server, on the other hand, "go get"
>> seems to
>> > > > require the ".git" suffix.  An I mentioned earlier, this results in
>> the
>> > > > creation of a directory that also has the ".git" suffix.
>> > > >
>> > > > The problem is: the behavior of "git clone" is in conflict with the
>> > > > behavior of "go get", at least with regards to the apache git
>> server.
>> > > > At one point the installation documentation was accurate, but it
>> seems
>> > > > we have since opted for git-friendliness rather than
>> > > > go-get-friendliness.
>> > > >
>> > > > We will need to find a simpler workaround.  In the meantime, we
>> should
>> > > > at least update the documentation.  Also, soon newt binaries will be
>> > > > available for download which help to alleviate problems with go.
>> > > >
>> > >
>> > > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path,
>> > > that would point to the proper Apache git repository?   I thought this
>> > > would solve that problem?
>> > >
>> > > Sterling
>>
>
>

Re: installing the Newt

[todd mitton]

Sorry.  I was waiting to switch to the vanity import domain until all the
other rename changes were done.  I didn't realize we were ready.

New users can now do this:

go get mynewt.apache.org/newt/newt
go get mynewt.apache.org/newt/newtmgr
go get mynewt.apache.org/newt/newtvm

The user won't need to manually clone the repo.  go get will clone it into
$GOPATH/src/mynewt.apache.org/newt.  By default the user will be on the
master branch. If the user wishes to be on develop, they can:

cd $GOPATH/src/mynewt.apache.org/newt
git checkout develop

-Todd

On Wed, Mar 2, 2016 at 11:46 PM, Christopher Collins 
wrote:

> I have committed the changes to the develop branch.  Now all go imports
> use the vanity domain.
>
> Unfortunately, this is going cause a bit of pain for the current users
> because the newt sources are now in the wrong directory.  To correct
> this problem, you will need to move the old newt path to the new one:
>
> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>   mv $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
> "$GOPATH"/src/mynewt.apache.org/newt
>
> If you plan on building older versions of newt, you should link the path
> rather than move it:
>
> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>   ln -s $GOPATH/src/
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
> mynewt.apache.org/newt
>
> Sorry for the hassle.  Yes, we definitely need to include convenience
> binaries in the next release :).
>
> Chris
>
> On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
> > Nice!  That seems to work.  I guess I completely glossed over those
> > vanity URL emails.  I will make the necessary changes to the develop
> > branch.  Unfortunately, I'm afraid it is too late to fix 0.8.0-b1.
> >
> > Chris
> >
> > On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
> > >
> > > >
> > > > When pointed at the apache server, on the other hand, "go get" seems
> to
> > > > require the ".git" suffix.  An I mentioned earlier, this results in
> the
> > > > creation of a directory that also has the ".git" suffix.
> > > >
> > > > The problem is: the behavior of "git clone" is in conflict with the
> > > > behavior of "go get", at least with regards to the apache git server.
> > > > At one point the installation documentation was accurate, but it
> seems
> > > > we have since opted for git-friendliness rather than
> > > > go-get-friendliness.
> > > >
> > > > We will need to find a simpler workaround.  In the meantime, we
> should
> > > > at least update the documentation.  Also, soon newt binaries will be
> > > > available for download which help to alleviate problems with go.
> > > >
> > >
> > > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path,
> > > that would point to the proper Apache git repository?   I thought this
> > > would solve that problem?
> > >
> > > Sterling
>

Re: Request committer access

[todd mitton]

Oh, cool.  I find it easier to keep track of proposed changes using the
dedicated pull requests page than searching through email.  Could you setup
a mirror for
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git?  Let me
know if I should submit a request ticket someplace.

Thanks Justin,
-Todd


On Tue, Feb 9, 2016 at 1:28 PM, Justin Mclean 
wrote:

> Hi,
>
> > It looks like other Apache projects do pull requests using github, but
> mynewt isn't doing
> > that.
>
> You can create git patches on ttp://
> git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git or pull
> requests on the github mirrors of the mynewt repos
> https://github.com/apache/incubator-mynewt-larva.
>
> Thanks,
> Justin

Request committer access

[todd mitton]

Hi,

I'm a backend engineer at runtime.io.  I'd like to become a committer so I
can help with infrastructure and website related tasks.

Thanks,
-Todd

Automate http://mynewt.incubator.apache.org generation

[todd mitton]

Hi,

Here's a simple script to automate the generation of the static content for
http://mynewt.incubator.apache.org. It basically captures the steps Aditi
takes when updating the site.

Thanks,
-Todd


diff --git a/build.sh b/build.sh
new file mode 100755
index 000..f810ac8
--- /dev/null
+++ b/build.sh
@@ -0,0 +1,34 @@
+#!/bin/bash -e
+
+if [[ "$1" != "build"  ]]; then
+echo "Build the mynewt website"
+echo "Make sure git status is claen and run from the master branch"
+echo
+echo "Usage: $0 build"
+exit
+fi
+
+echo mkdocs clean build:
+mkdocs build --clean
+
+echo Remove unwanted html templates
+find site -name "*.html" | xargs grep '{%.*%}' -l | xargs rm
+
+echo Copy extras into site
+cp -a extras/ site/
+
+echo Change git branch to asf-site
+git checkout asf-site
+
+echo Remove old content
+ls | grep -v site | xargs rm -rf
+
+echo Copy contents of site directory for serving
+cp -a site/ .
+
+echo ---
+echo --- You are now on the asf-site branch
+echo --- Review git diffs before commiting
+echo ---
+git status
+

Re: Vanity import domain

[todd mitton]

I think the transparency concern is valid.  I definitely did not intend to
make things less transparent.

I'm not as worried about the security of the domain.  There's similar
concerns with all the dependencies we pull in.  At least I have higher
confidence in the domains we have some control over.

I want to mention a couple of the benefits of using the vanity domain.  I
didn't even mention the main benefit in my initial email.

1.) The main benefit is to avoid confusion.  The current import paths are a
little unusual.  Should the import paths include ".git" or not?  Why does
this import path include ".git"

https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;a=blob;f=newt/newt.go;h=86d32b44b6d4bea064e4628c8456c1c98316474e;hb=HEAD#l20

and why does this import path not include ".git"?


https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;a=blob;f=newtmgr/newtmgr.go;h=7244efa474692b91b99ccc7825ec3167f5b58e63;hb=HEAD#l26

In your $GOPATH directory do you have src/
git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git or do you have
src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt?

These types of questions don't help people who are new to go.  These
questions can be avoided by using a vanity domain.

2.) I already mentioned this, but a vanity domain decouples the code from
the hosting location.  We're going to work very hard to remove the
"incubator", so lets make an easy change now instead of a potentially
painful change later.

3.) There's precedent for using vanity import domains.  For example,
https://github.com/kubernetes/kubernetes, a successful open source project,
uses k8s.io.


I think using mynewt.apache.org sounds good.  Aditi and I should be able to
get that working.

Thanks,
-Todd


On Thu, Feb 4, 2016 at 8:12 PM, Sterling Hughes  wrote:

> Well, all the cool kids are doing it. :-)
>
> As the import paths are kinda a PITA (not just the typing, without some
> redirect go get/go install seem to be giving people problems depending on
> machine), let's start with seeing if we can do this on mynewt.apache.org,
> and then if we decide as a project to adopt mynewt.io, we can do that
> then.
>
> Sterling
>
>
> On 2/4/16 7:24 PM, Greg Stein wrote:
>
>> I see no reason for using an external domain (or even if it was
>> transferred
>> to the ASF). mynewt.apache.org works today. Why can't that be used, with
>> the same redirect scheme?
>>
>> On Thu, Feb 4, 2016 at 9:19 PM, Sterling Hughes 
>> wrote:
>>
>> Hi Justin,
>>>
>>> mynewt.io would be a vanity domain to make git imports simpler, so
>>> instead of doing:
>>>
>>> import (
>>>  "git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt/cli
>>> "
>>> )
>>>
>>> You'd do:
>>>
>>> import (
>>>  "mynewt.io/newt/cli"
>>> )
>>>
>>> And for installation of packages, you would do:
>>>
>>> go install mynewt.io/newt
>>>
>>> Instead of:
>>>
>>> go install
>>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt
>>>
>>> All the cool kids are doing it :-)
>>>
>>> mynewt.io would just provide a set of go metadata.
>>>
>>> We (runtime) have purchased and set this up, because we are lazy and
>>> don't
>>> like typing things.  We'd be happy to gift this to the ASF, and run it on
>>> ASF infrastructure (perhaps redirect to mynewt.incubator.apache.org).
>>>
>>> I'd be interested in your view, but to me, I feel like this is a nice
>>> developer convenience that makes us agnostic to git structure, and if the
>>> Mynewt project ever decided Runtime were being bad citizens, it's a very
>>> quick change to the source code to remove these references.
>>>
>>> Sterling
>>>
>>>
>>>
>>> On 2/4/16 1:11 PM, Justin Mclean wrote:
>>>
>>> Hi,

 I may be missing something but this may not be the best idea from a
 being
 open point of view. Who has access to mynewt.io? How are changes
 tracked? How do committers make changes?

 Justin



>>