Hey, On 4/2/16 12:37 PM, Christopher Collins wrote:
I agree that that is a compatibility break, but that change was made at the same time as a host of other backwards-incompatible changes (0.8.0-b2). I think this particular problem is a bit more complicated, so strap yourself in for some mind-numbing post-mortem analysis.The root of this issue is that the arduino repository.yml file incorrectly pointed to the develop branch rather than an appropriate tag on the master branch. Under these conditions, everything worked for a while, because the arduino bsp's pkg.yml file on the develop branch does specify the correct package type ("bsp"). Eventually, a change was made to the arduino develop branch which was incompatible with the core master branch [*], which is not surprising. This incompatible change exposed the bug in the arduino repository.yml file. As a consequence, the arduino repository.yml file was modified to point to the master branch. The mistake here was in assuming the repository.yml change would be sufficient for fixing the arduino build issues.
Yes, I was bitten by this the other day. Which is why I created a tag to switch to 0-dev.
In my opinion, temporarily removing the package type restrictions is not the right thing to do here. We would need to re-release newt for that fix to have any effect. Instead, I believe we should create a new tag on the arduino repo with the pkg.yml fix. I can make this change and ensure arduino apps build properly. However, I don't have an arduino with me, so I can't actually test image upload or debug.
I'll test once you make the fix. If you can get it to compile, I'll make sure it loads on the board.
Sterling
