[yocto] The error of task do_validate_branches

[Bruce Ashfield]

On 2015-04-13 11:14 PM, Neil.Wu at Emerson.com wrote:
> Hi, all
>
> I build the custom linux-yocto kernel, it appears the error as bellow :

Hi Neil,

Can you provide a bit more information ? What release/branch are you
building ?

Obviously you are building a variant of linux-yocto that wasn't
released as part of the project (since we don't have a tiam335x
recipe), is there a place that recipe can be found ?

>
> ERROR: Function failed: do_validate_branches (log file is located at
> /home/ectrs/poky/coretexa8/tmp/work/am335x_evm-poky-linux-gnueabi/linux-yocto-tiam335x/3.12.10--SS-r0/temp/log.do_validate_branches.4899)
>
> ERROR: Logfile of failure stored in:
> /home/ectrs/poky/coretexa8/tmp/work/am335x_evm-poky-linux-gnueabi/linux-yocto-tiam335x/3.12.10--SS-r0/temp/log.do_validate_branches.4899
>
> Log data follows:
>
> | DEBUG: Executing shell function do_validate_branches
>
> | NOTE: custom recipe is being built, forcing SRCREV to INVALID
>
> | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch
>
> | fatal: A branch named 'master-orig' already exists.
>
> | fatal: ambiguous argument 'INVALID': unknown revision or path not in
> the working tree.

These errors are pointing to an invalid or somehow corrupted/partially
built kernel git repository being used.

I assume that you've tried a clean/cleanll on the kernel recipe and
then rebuilt ?

Bruce

>
> | Use '--' to separate paths from revisions, like this:
>
> | 'git <command> [<revision>...] -- [<file>...]'
>
> | WARNING: exit code 128 from a shell command.
>
> | ERROR: Function failed: do_validate_branches (log file is located at
> /home/ectrs/poky/coretexa8/tmp/work/am335x_evm-poky-linux-gnueabi/linux-yocto-tiam335x/3.12.10--SS-r0/temp/log.do_validate_branches.4899)
>
> ERROR: Task 69
> (/home/ectrs/poky/meta-emerson-ecosys/recipes-kernel/linux/linux-yocto-tiam335x_3.12.10.bb,
> do_validate_branches) failed with exit code '1'
>
> How to resolve this problem? if you know please help me.
>
> Thanks
>
> Neil
>
>
>