Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

["Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>]

Thanks,

It worked with standards/base branch. 

Regards,
Manish Jaggi

________________________________________
From: Zhenhua Luo <zhenhua.luo@nxp.com>
Sent: Tuesday, April 26, 2016 1:02 PM
To: Bruce Ashfield; Jaggi, Manish; Burton, Ross
Cc: yocto@yoctoproject.org
Subject: RE: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

If the SHA exists in a tag instead of any branch, you can use nobranch parameter, refer to http://git.yoctoproject.org/cgit.cgi/poky/tree/bitbake/lib/bb/fetch2/git.py?id=c4bcaa3f7ceac346af1555fff2b526ceeac92a54#n47.


Best Regards,

Zhenhua

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Bruce Ashfield
> Sent: Tuesday, April 26, 2016 10:11 AM
> To: Jaggi, Manish <Manish.Jaggi@caviumnetworks.com>; Burton, Ross
> <ross.burton@intel.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Fetcher failure: Unable to find revision
> 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> upstream
>
> On 2016-04-25 9:05 PM, Jaggi, Manish wrote:
> >
> > ________________________________________
> > From: Bruce Ashfield [bruce.ashfield@windriver.com]
> > Sent: Monday, April 25, 2016 11:04 PM
> > To: Jaggi, Manish; Burton, Ross
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] Fetcher failure: Unable to find revision
> > 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> > upstream
> >
> > On 2016-04-25 12:10 PM, Jaggi, Manish wrote:
> >>
> >> ---------------------------------------------------------------------
> >> ---
> >> *From:* Burton, Ross <ross.burton@intel.com>
> >> *Sent:* Monday, April 25, 2016 8:12 PM
> >> *To:* Jaggi, Manish
> >> *Cc:* yocto@yoctoproject.org
> >> *Subject:* Re: [yocto] Fetcher failure: Unable to find revision
> >> 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> >> upstream
> >>
> >> On 25 April 2016 at 14:30, Jaggi, Manish
> >> <Manish.Jaggi@caviumnetworks.com
> >> <mailto:Manish.Jaggi@caviumnetworks.com>> wrote:
> >>
> >>      It seems the revid / tag is not on any branch
> >>      git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
> >>      returns nothing.
> >>
> >>      How to fix this issue ?
> >>
> >>
> >> You probably want to use git branch -r --contains 213... as otherwise
> >> git branch will only list local branches.  The web UI says that this
> >> commit exists on master though...
> >>
> >> [Manish] Same output with -r.
> >> Can you please share the link of web ui. As per the error it is not
> >> on master branch.
> >
> > linux-yoct-dev and linux-yocto-4.4 are different trees.
> > linux-yocto-dev tracks the latest mainline kernel, not -stable.
> >
> > So if you are looking for 4.4.3 on linux-yocto-dev, you aren't going
> > to find it.
> >
> > [Manish] the 4.4.3 tag is also not on master branch of the 4.4 tree.
> > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.4/tag/?h=stand
> > ard/base&id=v4.4.3
> > The master is 4.4
>
> It's on standard/base. master is left as the initial branch point of the repository.
> When LTSI is available, I tend to update master, but since 4.4 has no LTSI
> content, I leave master alone.
>
> Also note: I'm currently not pushing and -stable updates to that tree, since I'm
> temporarily frozen for the yocto 2.1 release.
>
>
> >
> > A clone and check from tag works manually, but when bitbake fetches it, it
> throws error as bitbake is not able to find the commit on master branch.
> > How to fix thisk
>
> don't use master, use standard/base as the branch.
>
> Bruce
>
> >
> > Bruce
> >
> >>
> >>
> >> Ross
> >>
> >>
> >
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto