From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: "fatal: A branch named 'meta-orig' already exists."
Date: Tue, 31 Mar 2015 20:49:10 -0400 [thread overview]
Message-ID: <551B4086.8050200@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1503311824570.28969@localhost>
On 2015-03-31 6:26 PM, Robert P. J. Day wrote:
>
> oh, what fresh hell is this?
>
> ... snip ...
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: Function failed: do_validate_branches (log file is located at
> /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
> ERROR: Logfile of failure stored in:
> /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
> Log data follows:
> | DEBUG: Executing shell function do_validate_branches
> | NOTE: Setting branch meta to
> 9e70b482d3773abf92c9c5850e134cbca1d5651f
> | fatal: A branch named 'meta-orig' already exists.
>
> this is building core-image-minimal for qemux86, and i'm assuming
> this is not fedora rawhide related.
You've got a borked tree sitting in work-shared. If you clean-all
and start again, does it show up ?
If it repeats, then it very well could be the version of git in
rawhide that is causing the issue.
Bruce
>
> rday
>
next prev parent reply other threads:[~2015-04-01 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 22:26 "fatal: A branch named 'meta-orig' already exists." Robert P. J. Day
2015-04-01 0:49 ` Bruce Ashfield [this message]
2015-04-01 7:07 ` Robert P. J. Day
2015-04-01 11:16 ` Bruce Ashfield
2015-04-01 11:24 ` Robert P. J. Day
2015-04-01 12:34 ` Bruce Ashfield
2015-04-02 8:17 ` Robert P. J. Day
2015-04-02 10:16 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551B4086.8050200@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.