ev3dev-stretch

[dlech]

Following up on #338 (comment)

ev3dev-lang-python is already broken in ev3dev-stretch

How so? That seems pretty important. Can you open a new issue for it?

https://github.com/ev3dev/ev3dev-kpkg/blob/ev3dev-stretch/ev3dev-ev3/changelog

• Breaking change: LEDs are renamed to mainline kernel names
  • Names will be similar to "led0:red:brick-status"

• Breaking change: EV3/EVB input/output port drivers are merged
  • EV3 port names will be similar to "ev3-ports:in1".

[dlech]

Important info for package maintainer:

in debian/changelog, stable in the line

python-ev3dev (0.8.1) stable; urgency=medium

will upload to jessie.

To upload to stretch, use testing.

python-ev3dev (0.8.1) testing; urgency=medium

UPDATE:

Also, things will break if you upload the same version number to both distros, so don't do exactly as shown above.

[dlech]

For all of the ev3dev packages I maintain, I have created an ev3dev-jessie branch and an ev3dev-stretch branch. I've basically adopted (something like) the Debian policy for stable and testing, which is only critical bug/security fixes go into stable (jessie in our case), no new features. You can do what you like, including new features and breaking changes in testing (stretch in our case).

[WasabiFan]

https://github.com/ev3dev/ev3dev-kpkg/blob/ev3dev-stretch/ev3dev-ev3/changelog

Oh, damn... when I originally read that I thought all the changes were on the EVB/BrickPi side. Looks like we'll need to fix those.

For all of the ev3dev packages I maintain, I have created an ev3dev-jessie branch and an ev3dev-stretch branch.

I think we've gotten to the point where that convention would work well here. We'll need to figure out whether we want to maintain a "dev" branch or not. List of things that will be impacted (not necessarily complete):

• CI builds (I think we have some configuration which points to branch names, or at least we did)
• Documentation versions and labels
• Contribution info (somewhere we added an explanation of develop vs. master)

[dwalton76]

So branches and branch names...some options

option 1

• rename master to ev3dev-lang-python-jessie
• create a child branch called ev3dev-lang-python-stretch
• create a ev3dev-lang-python-stretch-develop child branch off of ev3dev-lang-python-stretch
• change the default branch to ev3dev-lang-python-stretch
• delete todays develop branch

option 2 drop the ev3dev-lang-python- part of the branch names

• rename master to jessie
• create a child branch called stretch
• create a stretch-develop child branch off of stretch
• change the default branch to stretch
• delete todays develop branch

I like option 2 myself, the names are much shorter and easier to type and we already know that are are in the ev3dev-lang-python- repo, it feels redundant to also put that in the branch names.

Most future dev would happen in stretch-develop and then we merge into stretch the same we way merge develop -> master today. We then git cherry-pick SHA any commit that also needs to go into jessie.

[ddemidov]

We could just tag the current master with jessie, and promise to never look back (move all development to stretch).

[dwalton76]

@dlech @ddemidov need a pointer here on how to use the ev3dev-lang stuff

For the LEDs I need to make this change...I did the following manually just as a quick test. I did not use the templates

diff --git a/ev3dev/ev3.py b/ev3dev/ev3.py
index 725f713..8639784 100644
--- a/ev3dev/ev3.py
+++ b/ev3dev/ev3.py
@@ -47,10 +47,10 @@ class Leds(object):
 
 # ~autogen led-colors platforms.ev3.led>currentClass
 
-    red_left = Led(name_pattern='ev3:left:red:ev3dev')
-    red_right = Led(name_pattern='ev3:right:red:ev3dev')
-    green_left = Led(name_pattern='ev3:left:green:ev3dev')
-    green_right = Led(name_pattern='ev3:right:green:ev3dev')
+    red_left = Led(name_pattern='led0:red:brick-status')
+    red_right = Led(name_pattern='led1:red:brick-status')
+    green_left = Led(name_pattern='led0:green:brick-status')
+    green_right = Led(name_pattern='led1:green:brick-status')
 
     LEFT = ( red_left, green_left, )
     RIGHT = ( red_right, green_right, )

but to make this permanent I need to use templates so I make this change

dwalton@laptop ~/l/e/e/autogen> git diff
diff --git a/spec.json b/spec.json
index 0891772..ea708c2 100644
--- a/spec.json
+++ b/spec.json
@@ -1482,10 +1482,10 @@
         "ev3": {
             "led": {
                 "instances": [
-                    { "name" : "Red Left", "systemName": "ev3:left:red:ev3dev" },
-                    { "name" : "Red Right", "systemName": "ev3:right:red:ev3dev" },
-                    { "name" : "Green Left", "systemName": "ev3:left:green:ev3dev" },
-                    { "name" : "Green Right", "systemName": "ev3:right:green:ev3dev" }
+                    { "name" : "Red Left", "systemName": "led0:red:brick-status" },
+                    { "name" : "Red Right", "systemName": "led1:red:brick-status" },
+                    { "name" : "Green Left", "systemName": "led0:green:brick-status" },
+                    { "name" : "Green Right", "systemName": "led1:green:brick-status" }
                 ],
                 "groups" : [
                     { "name" : "Left", "entries" : ["Red Left", "Green Left"] },
dwalton@laptop ~/l/e/e/autogen> 

I then reverted the changes I made to ev3dev/ev3.py and now want to make those changes using the templates. The README at ev3dev-lang does not have instructions on how to use the contents of the repo. The README in the autogen directory has a little...I cced to the autgen directory and ran npm install and it installed some stuff. I thought maybe I'm supposed to run the following but thats not it

dwalton@laptop ~/l/ev3dev-lang-python> node ev3dev-lang/autogen/autogen.js 
module.js:328
    throw err;
    ^

Error: Cannot find module 'liquid-node'
    at Function.Module._resolveFilename (module.js:326:15)
    at Function.Module._load (module.js:277:25)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/home/dwalton/lego/ev3dev-lang-python/ev3dev-lang/autogen/autogen.js:13:25)
    at Module._compile (module.js:410:26)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:442:10)
dwalton@laptop ~/l/ev3dev-lang-python> 

How do I the use contents of ev3dev-lang to build a new ev3dev/ev3.py using my new spec.json?

[dwalton76]

@dlech I installed https://oss.jfrog.org/list/oss-snapshot-local/org/ev3dev/brickstrap/2017-09-02/snapshot-ev3dev-stretch-bone-generic-2017-09-01.img.xz on my EVB but it is kernel 4.9.41 instead of 4.9.42

robot@evb[ev3dev-lang-python]# ev3dev-sysinfo 
Image file:         ev3dev-stretch-bone-generic-2017-09-01
Kernel version:     4.9.41-ev3dev-1.4.0-bb.org
/usr/bin/ev3dev-sysinfo: line 68: warning: command substitution: ignored null byte in input
Board:              TI AM335x BeagleBone Black
Revision:           000c
Brickman:           0.10.0
ev3devKit:          0.5.2
robot@evb[ev3dev-lang-python]# 

Will the the next binary be 4.9.42? If so I'll hold off for it to work on

Breaking change: EV3/EVB input/output port drivers are merged
EV3 port names will be similar to "ev3-ports:in1".

[dlech]

The important part of the kernel version is ev3dev-1.4.0. The 4.9.x comes from the upstream kernels for the various devices, so they don't always match. You can also find a BeagleBone specific changelog at https://github.com/ev3dev/ev3dev-kpkg/blob/ev3dev-stretch/ev3dev-bb.org/changelog.

[WasabiFan]

node ev3dev-lang/autogen/autogen.js

That's the right command. I'm guessing that the npm install command didn't succeed. Can you post the output?

[dwalton76]

attempting to run from root of ev3dev-lang-python but it needs package.json

dwalton@laptop ~/l/ev3dev-lang-python> npm install
npm WARN enoent ENOENT: no such file or directory, open '/home/dwalton/lego/ev3dev-lang-python/package.json'
npm WARN ev3dev-lang-python No description
npm WARN ev3dev-lang-python No repository field.
npm WARN ev3dev-lang-python No README data
npm WARN ev3dev-lang-python No license field.
dwalton@laptop ~/l/ev3dev-lang-python> 

so running from ev3dev-lang/autogen/ where there is a package.json but the postintsall barfs

dwalton@laptop ~/l/ev3dev-lang-python> cd ev3dev-lang/autogen/
dwalton@laptop ~/l/e/e/autogen> sudo npm install
[sudo] password for dwalton: 
npm WARN lifecycle ev3dev-lang-autogen@1.0.0~postinstall: cannot run in wd %s %s (wd=%s) ev3dev-lang-autogen@1.0.0 cd node_modules/liquid-node && npm install && npm run compile /home/dwalton/lego/ev3dev-lang-python/ev3dev-lang/autogen
npm WARN liquid-node@2.4.0 requires a peer of bluebird@^2.1.3 but none was installed.
npm WARN ev3dev-lang-autogen@1.0.0 No repository field.
npm WARN ev3dev-lang-autogen@1.0.0 No license field.
dwalton@laptop ~/l/e/e/autogen> 
dwalton@laptop ~/l/e/e/autogen> ls
autogen-core.js  autogen.js  config.js  node_modules/  package.json  README.rst  utils.js
dwalton@laptop ~/l/e/e/autogen> cat package.json 
{
  "name": "ev3dev-lang-autogen",
  "version": "1.0.0",
  "description": "Dependencies for ev3dev-lang autogen",
  "main": "autogen.js",
  "dependencies": {
    "liquid-node": "git://github.com/WasabiFan/liquid-node.git",
    "yargs": "~3.29.0"
  },
  "devDependencies": {},
  "scripts": {
    "test": "echo \"TODO\" && exit 1",
    "postinstall":  "cd node_modules/liquid-node && npm install && npm run compile"
  },
  "homepage": "https://github.com/ev3dev/ev3dev-lang"
}
dwalton@laptop ~/l/e/e/autogen> 

there is a node_modules in the root dir of ev3dev-lang-python but it is empty

dwalton@laptop ~/l/ev3dev-lang-python> ls -l node_modules/
total 0
dwalton@laptop ~/l/ev3dev-lang-python> 

[dwalton76]

"The important part of the kernel version" everything on my EVB is working though, touch sensors work, motors work, etc....it feels like I don't have the Breaking change