Re: [OE-core] git fetcher sanity check for matching branch and SRCREV

2013-12-11 Thread Martin Jansa
On Wed, Dec 11, 2013 at 10:58:20PM +, Richard Purdie wrote: > On Wed, 2013-12-11 at 23:51 +0100, Martin Jansa wrote: > > I understand and support reasons behind recently added commit > > "fetch2/git: Add sanity check to ensure we really did fetch the correct > > revisions" > > > > but there is

Re: [OE-core] git fetcher sanity check for matching branch and SRCREV

2013-12-11 Thread Nicolas Dechesne
On Wed, Dec 11, 2013 at 11:51 PM, Martin Jansa wrote: > Unfortunately we cannot "disable" this check by explicitly setting empty > branch or setting tag=1.0.12 > > I can ask yajl owner to push that one missing patch to 1.x branch, but > there were no changes in last 11 months so I don't know how r

Re: [OE-core] git fetcher sanity check for matching branch and SRCREV

2013-12-11 Thread Richard Purdie
On Wed, 2013-12-11 at 23:51 +0100, Martin Jansa wrote: > I understand and support reasons behind recently added commit > "fetch2/git: Add sanity check to ensure we really did fetch the correct > revisions" > > but there is at least one corner case which IMHO isn't supported now, in > meta-webos we

[OE-core] git fetcher sanity check for matching branch and SRCREV

2013-12-11 Thread Martin Jansa
I understand and support reasons behind recently added commit "fetch2/git: Add sanity check to ensure we really did fetch the correct revisions" but there is at least one corner case which IMHO isn't supported now, in meta-webos we have yajl recipe with: # corresponds to tag 1.0.12 SRCREV = "17b1