combo-layer issue

combo-layer issue

[akuster808]

Morning all,

I am trying to replicate how Poky is created using combo-layer.  I have 
referenced  https://wiki.yoctoproject.org/wiki/Combo-layer

The issue seems to be related when I define "branch". Not defining it 
works fine (ie, master default). I suspect I am doing something 
incorrectly or a compatibility issue with my local git version 1.9.1.

can someone poke to go in the right direction.

kind regards,
Armin


combo-layer.conf:

[bitbake]
src_uri = git://git.openembedded.org/bitbake
local_repo_dir = /tmp/src/test/bitbake
dest_dir = bitbake
branch = 1.26
last_revision =

[oe-core]
src_uri = git://git.openembedded.org/openembedded-core
local_repo_dir = /tmp/src/test/oecore
dest_dir = .
branch = fido
last_revision =



Error message:

[07:22:26] fatal: ambiguous argument 'fido': unknown revision or path 
not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fido

Traceback (most recent call last):
   File "./scripts/combo-layer", line 869, in <module>
     ret = main()
   File "./scripts/combo-layer", line 865, in main
     actions.get(args[1], action_error)(confdata, args[1:])
   File "./scripts/combo-layer", line 220, in action_init
     rev = runcmd('git rev-parse %s' % initialrev, ldir).strip()
   File "./scripts/combo-layer", line 179, in runcmd
     raise e
CalledProcessError: Command 'git rev-parse fido' returned non-zero exit 
status 128

Re: combo-layer issue

[Trevor Woerner]

On 15-04-03 10:34 AM, akuster808 wrote:
> I am trying to replicate how Poky is created using combo-layer.  I 
> have referenced  https://wiki.yoctoproject.org/wiki/Combo-layer

Interesting! I had never heard of this :-)

> The issue seems to be related when I define "branch". Not defining it 
> works fine (ie, master default). I suspect I am doing something 
> incorrectly or a compatibility issue with my local git version 1.9.1.

I just tried with git version 2.4.0.rc0.43.gcf8a8c6 and had the same 
result, so it's not related to git version (or its relying on a very old 
version of git).