You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by Li-Chun Ko <li...@gmail.com> on 2017/07/04 14:53:58 UTC
ReadDesc: No matching branch for apache-mynewt-core repo
Hi all,
When I was following the instructions of the "Create your first project"
tutorial today, I got "ReadDesc: No matching branch for apache-mynewt-core
repo" right after I enter "newt install" (no problem on the "newt new
myproj" part).
Is this a problem of the repo or my local computer? The example used to
work before I upgrade to go 1.7. I tried vers: 1-latest and vers: 0-dev and
neither worked.
Br,
Lichun
Re: ReadDesc: No matching branch for apache-mynewt-core repo
Posted by Christopher Collins <ch...@runtime.io>.
I don't think this problem will come up anymore with any version of
newt. Older versions of newt will download the develop branch of
blinky, which correctly references the new URLs now.
Going forward, new versipns of newt will retrieve the blinky tag which
corresponds to the version of newt being used. Assuming we create the
1.1.0 tag of blinky off of master, this will also reference the correct
URLs.
Chris
On Tue, Jul 04, 2017 at 10:26:13AM -0700, Sheela Kiiskila wrote:
> Would this work for someone who is trying to download say released version1.0? Newt1.0 pulls from blinky1.0 so who ever is downloading version1.0 might still have to manually change the project.yml and remove “incubator”?
>
>
>
> > On Jul 4, 2017, at 8:55 AM, Christopher Collins <ch...@runtime.io> wrote:
> >
> > Li-Chun, could you try again? Delete your project directory, then run
> > "newt new" and "newt install". I believe the problem should be fixed
> > now.
> >
> > Some more details: this is a confusing problem. The "incubator-..."
> > github URLs are supposed to redirect to the new ones, and the
> > redirection seems to work for most people. For some reason, the
> > redirection fails for some users who get this error instead.
> >
> > I tried to fix this last week by removing "incubator-" from blinky's
> > project.yml file, but I only made the change to master. It appears
> > "newt new" retrieves the develop branch of blinky, rather than master.
> > This is not quite right; it must have slipped through when we
> > transitioned to the current branching scheme.
> >
> > I just fixed the project.yml in develop. We should fix newt so that it
> > downloads from master instead of develop; I'll create a jira ticket.
> >
> > Chris
> >
> >
> > On Tue, Jul 04, 2017 at 08:31:57AM -0700, Sterling Hughes wrote:
> >> Hi,
> >>
> >> This is an unfortunate side effect of our exit from incubator, which
> >> renamed the git repositories.
> >>
> >> If you go to project.yml and replace “incubator-mynewt-core” with
> >> “mynewt-core” under the repo field of “apache-mynewt-core” -
> >> everything should work.
> >>
> >> Sterling
> >>
> >> On 4 Jul 2017, at 7:53, Li-Chun Ko wrote:
> >>
> >>> Hi all,
> >>>
> >>> When I was following the instructions of the "Create your first
> >>> project"
> >>> tutorial today, I got "ReadDesc: No matching branch for
> >>> apache-mynewt-core
> >>> repo" right after I enter "newt install" (no problem on the "newt new
> >>> myproj" part).
> >>>
> >>> Is this a problem of the repo or my local computer? The example used
> >>> to
> >>> work before I upgrade to go 1.7. I tried vers: 1-latest and vers:
> >>> 0-dev and
> >>> neither worked.
> >>>
> >>> Br,
> >>> Lichun
>
Re: ReadDesc: No matching branch for apache-mynewt-core repo
Posted by Sheela Kiiskila <sh...@runtime.io>.
Would this work for someone who is trying to download say released version1.0? Newt1.0 pulls from blinky1.0 so who ever is downloading version1.0 might still have to manually change the project.yml and remove “incubator”?
> On Jul 4, 2017, at 8:55 AM, Christopher Collins <ch...@runtime.io> wrote:
>
> Li-Chun, could you try again? Delete your project directory, then run
> "newt new" and "newt install". I believe the problem should be fixed
> now.
>
> Some more details: this is a confusing problem. The "incubator-..."
> github URLs are supposed to redirect to the new ones, and the
> redirection seems to work for most people. For some reason, the
> redirection fails for some users who get this error instead.
>
> I tried to fix this last week by removing "incubator-" from blinky's
> project.yml file, but I only made the change to master. It appears
> "newt new" retrieves the develop branch of blinky, rather than master.
> This is not quite right; it must have slipped through when we
> transitioned to the current branching scheme.
>
> I just fixed the project.yml in develop. We should fix newt so that it
> downloads from master instead of develop; I'll create a jira ticket.
>
> Chris
>
>
> On Tue, Jul 04, 2017 at 08:31:57AM -0700, Sterling Hughes wrote:
>> Hi,
>>
>> This is an unfortunate side effect of our exit from incubator, which
>> renamed the git repositories.
>>
>> If you go to project.yml and replace “incubator-mynewt-core” with
>> “mynewt-core” under the repo field of “apache-mynewt-core” -
>> everything should work.
>>
>> Sterling
>>
>> On 4 Jul 2017, at 7:53, Li-Chun Ko wrote:
>>
>>> Hi all,
>>>
>>> When I was following the instructions of the "Create your first
>>> project"
>>> tutorial today, I got "ReadDesc: No matching branch for
>>> apache-mynewt-core
>>> repo" right after I enter "newt install" (no problem on the "newt new
>>> myproj" part).
>>>
>>> Is this a problem of the repo or my local computer? The example used
>>> to
>>> work before I upgrade to go 1.7. I tried vers: 1-latest and vers:
>>> 0-dev and
>>> neither worked.
>>>
>>> Br,
>>> Lichun
Re: ReadDesc: No matching branch for apache-mynewt-core repo
Posted by Li-Chun Ko <li...@gmail.com>.
Yes it works! Thank for all your prompt responses guys!
2017-07-05 0:13 GMT+08:00 Christopher Collins <ch...@runtime.io>:
> Slight correction:
>
> On Tue, Jul 04, 2017 at 08:55:35AM -0700, Christopher Collins wrote:
> > We should fix newt so that it > downloads from master instead of
> > develop; I'll create a jira ticket.
>
> It should download the tag which corresponds to the current newt
> version, not master. I have added a comment to
> https://issues.apache.org/jira/browse/MYNEWT-757 clarifying this.
>
> Chris
>
Re: ReadDesc: No matching branch for apache-mynewt-core repo
Posted by Christopher Collins <ch...@runtime.io>.
Slight correction:
On Tue, Jul 04, 2017 at 08:55:35AM -0700, Christopher Collins wrote:
> We should fix newt so that it > downloads from master instead of
> develop; I'll create a jira ticket.
It should download the tag which corresponds to the current newt
version, not master. I have added a comment to
https://issues.apache.org/jira/browse/MYNEWT-757 clarifying this.
Chris
Re: ReadDesc: No matching branch for apache-mynewt-core repo
Posted by Christopher Collins <ch...@runtime.io>.
Li-Chun, could you try again? Delete your project directory, then run
"newt new" and "newt install". I believe the problem should be fixed
now.
Some more details: this is a confusing problem. The "incubator-..."
github URLs are supposed to redirect to the new ones, and the
redirection seems to work for most people. For some reason, the
redirection fails for some users who get this error instead.
I tried to fix this last week by removing "incubator-" from blinky's
project.yml file, but I only made the change to master. It appears
"newt new" retrieves the develop branch of blinky, rather than master.
This is not quite right; it must have slipped through when we
transitioned to the current branching scheme.
I just fixed the project.yml in develop. We should fix newt so that it
downloads from master instead of develop; I'll create a jira ticket.
Chris
On Tue, Jul 04, 2017 at 08:31:57AM -0700, Sterling Hughes wrote:
> Hi,
>
> This is an unfortunate side effect of our exit from incubator, which
> renamed the git repositories.
>
> If you go to project.yml and replace “incubator-mynewt-core” with
> “mynewt-core” under the repo field of “apache-mynewt-core” -
> everything should work.
>
> Sterling
>
> On 4 Jul 2017, at 7:53, Li-Chun Ko wrote:
>
> > Hi all,
> >
> > When I was following the instructions of the "Create your first
> > project"
> > tutorial today, I got "ReadDesc: No matching branch for
> > apache-mynewt-core
> > repo" right after I enter "newt install" (no problem on the "newt new
> > myproj" part).
> >
> > Is this a problem of the repo or my local computer? The example used
> > to
> > work before I upgrade to go 1.7. I tried vers: 1-latest and vers:
> > 0-dev and
> > neither worked.
> >
> > Br,
> > Lichun
Re: ReadDesc: No matching branch for apache-mynewt-core repo
Posted by Sterling Hughes <st...@gmail.com>.
Hi,
This is an unfortunate side effect of our exit from incubator, which
renamed the git repositories.
If you go to project.yml and replace “incubator-mynewt-core” with
“mynewt-core” under the repo field of “apache-mynewt-core” -
everything should work.
Sterling
On 4 Jul 2017, at 7:53, Li-Chun Ko wrote:
> Hi all,
>
> When I was following the instructions of the "Create your first
> project"
> tutorial today, I got "ReadDesc: No matching branch for
> apache-mynewt-core
> repo" right after I enter "newt install" (no problem on the "newt new
> myproj" part).
>
> Is this a problem of the repo or my local computer? The example used
> to
> work before I upgrade to go 1.7. I tried vers: 1-latest and vers:
> 0-dev and
> neither worked.
>
> Br,
> Lichun