You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2019/11/19 05:18:32 UTC

[GitHub] [mynewt-core] hostilefork commented on issue #2102: `vers: 0-latest` not accepted by newt 1.7.0

hostilefork commented on issue #2102: `vers: 0-latest` not accepted by newt 1.7.0
URL: https://github.com/apache/mynewt-core/issues/2102#issuecomment-555337720
 
 
   This appears related to the issue here:
   
   https://github.com/apache/mynewt-newt/issues/297#issuecomment-492760479
   
   Hence the problem is that the `https://github.com/runtimeco/mynewt_stm32f3` has not had its `repository.yml` updated to follow the rule.  Unfortunately, there seems to be nothing that can be done at the repository usage site...because newt seems to be doing a kind of whole-file validation of repository.yml.
   
   So I forked the repository to change the line, and it got past that.  The next problem is under the apache GitHub, `mcumgr`, which maps 0.0.0 to `master`
   
   https://github.com/apache/mynewt-mcumgr/blob/8e20176e38dad0815ce6f51abad565bda747f936/repository.yml#L22

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services