From: Gary Thomas <gary@mlbassoc.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Dealing with new git fetcher
Date: Fri, 06 Dec 2013 08:18:31 -0700 [thread overview]
Message-ID: <52A1EAC7.6080803@mlbassoc.com> (raw)
In-Reply-To: <CABcZANmvO-f5MVmHcHUWvEoD4sz5vziJcvVCX-XVM3uvefrf4Q@mail.gmail.com>
On 2013-12-06 08:15, Chris Larson wrote:
>
> On Fri, Dec 6, 2013 at 8:08 AM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
> The 'git' fetcher was recently changed to expect/need the branch
> name for the desired revision. Many recipes don't have this and
> the revision is not on the master branch, hence leading to errors
> like this:
> ERROR: Fetcher failure: Unable to find revision f89bc066db0569008418fac1a0408a__9a57f2232f in branch master even from upstream
> ERROR: Function failed: Fetcher failure for URL: 'git://github.com/__boundarydevices/u-boot-imx6.__git <http://github.com/boundarydevices/u-boot-imx6.git>'. Unable to fetch
> URL from any source.
> ERROR: Logfile of failure stored in:
> /local/imx6_new/tmp/work/__sabrelite-amltd-linux-gnueabi/__u-boot-script-boundary/v2013.__01+gitAUTOINC+f89bc066db-r0/__temp/log.do_fetch.25272
> ERROR: Task 144 (/local/poky-multi/meta-fsl-__arm-extra/recipes-bsp/u-boot/u__-boot-script-boundary_git.bb <http://u-boot-script-boundary_git.bb>, do_fetch) failed with exit
> code '1'
>
> So the problem becomes how to identify the branch? In the case
> above, I have a checked out copy of this repository and when I
> try to find the branch, I come up empty:
> $ git branch --contains f89bc066db0569008418fac1a0408a__9a57f2232f
> $ git log f89bc066db0569008418fac1a0408a__9a57f2232f
> commit f89bc066db0569008418fac1a0408a__9a57f2232f
> Author: Eric Nelson <eric.nelson@boundarydevices.__com <mailto:eric.nelson@boundarydevices.com>>
> Date: Mon Aug 26 17:36:35 2013 -0700
> i.MX6: nitrogen6x: Add Yocto boot script
>
> So I see that the commit is present, but when I ask what branch, I
> get nothing...
>
>
> You asked git only about local branches.
>
> $ git branch -a --contains f89bc066db0569008418fac1a0408a9a57f2232f
> remotes/origin/production-before-20131107
Perfect (I should have known!)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2013-12-06 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 15:08 Dealing with new git fetcher Gary Thomas
2013-12-06 15:15 ` Chris Larson
2013-12-06 15:18 ` Gary Thomas [this message]
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=52A1EAC7.6080803@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=clarson@kergoth.com \
--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.