All of lore.kernel.org
 help / color / mirror / Atom feed
* Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
@ 2016-04-25 13:30 Jaggi, Manish
  2016-04-25 14:42 ` Burton, Ross
  0 siblings, 1 reply; 8+ messages in thread
From: Jaggi, Manish @ 2016-04-25 13:30 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

In my bb file I added the below line,


SRCREV = "2134d97aa3a7ce38bb51f933f2e20cafde371085"
SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev"

The revision id is of v4.4.3 tag.


Below errors are generated upon kernel fetching


ERROR: linux-4.4 do_fetch: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
ERROR: linux-4.4 do_fetch: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-dev'. Unable to fetch URL from any source.

It seems the revid / tag is not on any branch
git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
returns nothing.

How to fix this issue ?


Regards,
Manish Jaggi

[-- Attachment #2: Type: text/html, Size: 1645 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-25 13:30 Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream Jaggi, Manish
@ 2016-04-25 14:42 ` Burton, Ross
  2016-04-25 16:10   ` Jaggi, Manish
  0 siblings, 1 reply; 8+ messages in thread
From: Burton, Ross @ 2016-04-25 14:42 UTC (permalink / raw)
  To: Jaggi, Manish; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

On 25 April 2016 at 14:30, Jaggi, Manish <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...

Ross

[-- Attachment #2: Type: text/html, Size: 920 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-25 14:42 ` Burton, Ross
@ 2016-04-25 16:10   ` Jaggi, Manish
  2016-04-25 17:34     ` Bruce Ashfield
  0 siblings, 1 reply; 8+ messages in thread
From: Jaggi, Manish @ 2016-04-25 16:10 UTC (permalink / raw)
  To: Burton, Ross; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]


________________________________
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.


Ross

[-- Attachment #2: Type: text/html, Size: 2276 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-25 16:10   ` Jaggi, Manish
@ 2016-04-25 17:34     ` Bruce Ashfield
  2016-04-26  1:05       ` Jaggi, Manish
  0 siblings, 1 reply; 8+ messages in thread
From: Bruce Ashfield @ 2016-04-25 17:34 UTC (permalink / raw)
  To: Jaggi, Manish, Burton, Ross; +Cc: yocto

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.

Bruce

>
>
> Ross
>
>



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-25 17:34     ` Bruce Ashfield
@ 2016-04-26  1:05       ` Jaggi, Manish
  2016-04-26  2:11         ` Bruce Ashfield
  0 siblings, 1 reply; 8+ messages in thread
From: Jaggi, Manish @ 2016-04-26  1:05 UTC (permalink / raw)
  To: Bruce Ashfield, Burton, Ross; +Cc: yocto


________________________________________
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=standard/base&id=v4.4.3
The master is 4.4 

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

Bruce

>
>
> Ross
>
>



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-26  1:05       ` Jaggi, Manish
@ 2016-04-26  2:11         ` Bruce Ashfield
  2016-04-26  7:32           ` Zhenhua Luo
  0 siblings, 1 reply; 8+ messages in thread
From: Bruce Ashfield @ 2016-04-26  2:11 UTC (permalink / raw)
  To: Jaggi, Manish, Burton, Ross; +Cc: yocto

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=standard/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
>>
>>
>



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-26  2:11         ` Bruce Ashfield
@ 2016-04-26  7:32           ` Zhenhua Luo
  2016-04-26  7:46             ` Jaggi, Manish
  0 siblings, 1 reply; 8+ messages in thread
From: Zhenhua Luo @ 2016-04-26  7:32 UTC (permalink / raw)
  To: Bruce Ashfield, Jaggi, Manish, Burton, Ross; +Cc: yocto

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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
  2016-04-26  7:32           ` Zhenhua Luo
@ 2016-04-26  7:46             ` Jaggi, Manish
  0 siblings, 0 replies; 8+ messages in thread
From: Jaggi, Manish @ 2016-04-26  7:46 UTC (permalink / raw)
  To: Zhenhua Luo, Bruce Ashfield, Burton, Ross; +Cc: yocto

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


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2016-04-26  7:47 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-25 13:30 Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream Jaggi, Manish
2016-04-25 14:42 ` Burton, Ross
2016-04-25 16:10   ` Jaggi, Manish
2016-04-25 17:34     ` Bruce Ashfield
2016-04-26  1:05       ` Jaggi, Manish
2016-04-26  2:11         ` Bruce Ashfield
2016-04-26  7:32           ` Zhenhua Luo
2016-04-26  7:46             ` Jaggi, Manish

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.