All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: How to force the use of git-native?
Date: Thu, 12 Dec 2013 09:31:10 -0700	[thread overview]
Message-ID: <52A9E4CE.1060000@mlbassoc.com> (raw)
In-Reply-To: <52A9E41A.8010601@mlbassoc.com>

On 2013-12-12 09:28, Gary Thomas wrote:
> On 2013-12-12 09:20, Paul Eggleton wrote:
>> Hi Gary,
>>
>> On Thursday 12 December 2013 08:06:31 Gary Thomas wrote:
>>> I've found that the latest bitbake fetcher changes (require
>>> the use of branch names) fails with older versions of git.
>>> I have a Fedora 13 machine which I routinely use to build
>>> my Yocto projects that has git version 1.7.7.6.  On that machine,
>>> all git fetches fail, no matter what.  On my Ubuntu builder
>>> which has git 1.7.9.4, all is OK.
>>>
>>> I see that there is a git recipe in OE-core.  How can I force
>>> it to be built and used where the host's native git is inadequate?
>>
>> The solution we provide for this kind of situation is buildtools-tarball, as
>> described here (linked from the QS guide as well):
>>
>> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#required-git-tar-and-python-versions
>
> Thanks, I'll give this a go.

Oops, looks like I have a circular dependency problem since trying to make
the buildtools-tarball actually needs a working version of git??

ERROR: Fetcher failure: Unable to find revision 757a1664a440c60e8126443bf984e4bdf374c327 in branch master even from upstream
ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/opkg-utils'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/local/rpi_2013-12-12/tmp/work/i686-linux/opkg-utils-native/0.1.8+gitAUTOINC+757a1664a4-r0/temp/log.do_fetch.15416
ERROR: Task 85 (virtual:native:/home/local/poky-multi/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb, do_fetch) failed with exit code '1'
ERROR: Fetcher failure: Unable to find revision 6822ec76aa95f278195aeae59d4868ef224d7e4d in branch cross_prelink even from upstream
ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/prelink-cross.git;branch=cross_prelink'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/local/rpi_2013-12-12/tmp/work/i686-linux/prelink-native/1.0+gitAUTOINC+6822ec76aa-r0/temp/log.do_fetch.15406
ERROR: Task 244 (virtual:native:/home/local/poky-multi/meta/recipes-devtools/prelink/prelink_git.bb, do_fetch) failed with exit code '1'

>>
>> Interesting that git 1.7.7.6 is still not adequate though, that may be a
>> prompt to either fix the check to work with older versions of git or
>> increase our version number requirement.
>
> If you have ideas how I can investigate why this fails, I'd be glad
> to help out (to see if it can be made to work with 1.7.7.6 or if we
> just need a newer version period)
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2013-12-12 16:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 15:06 How to force the use of git-native? Gary Thomas
2013-12-12 16:20 ` Paul Eggleton
2013-12-12 16:28   ` Gary Thomas
2013-12-12 16:31     ` Gary Thomas [this message]
2013-12-12 16:37       ` Paul Eggleton
2013-12-12 16:43         ` Gary Thomas
2013-12-12 16:56           ` Flanagan, Elizabeth
2013-12-12 17:05             ` Gary Thomas
2013-12-16 15:10               ` Flanagan, Elizabeth
2013-12-16 17:33                 ` Gary Thomas
2013-12-17  7:33                   ` Søren Holm

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=52A9E4CE.1060000@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=paul.eggleton@linux.intel.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.