All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Saul Wold <saul.wold@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [poky] meta-toolchain build failed on fetch
Date: Fri, 04 Feb 2011 13:48:35 -0500	[thread overview]
Message-ID: <4D4C4A03.3070400@windriver.com> (raw)
In-Reply-To: <4D4C41F7.6010704@intel.com>

On 11-02-04 01:14 PM, Saul Wold wrote:
> On 02/04/2011 08:43 AM, Zhang, Jessica wrote:
>> Wold, Saul wrote:
>>> On 02/04/2011 06:16 AM, Bruce Ashfield wrote:
>>>> On 11-02-04 12:20 AM, Zhang, Jessica wrote:
>>>>> Has anyone run into the following failure, this is for
>>>>> meta-toolchain for x86_64:
>>>>
>>>> This is lurking in various forms at the moment, the fetcher
>>>> updates + new branches and the mirrors with old copies (my
>>>> guess), is causing this undesirable behaviour.
>>>>
>>>>>> Fetcher accessed the network with the command git fetch
>>>>> git.pokylinux.org/linux-yocto-2.6.37
>>>>>> NOTE: Fetcher accessed the network with the command git fetch
>>>>> git.pokylinux.org/linux-yocto-2.6.37
>>>>>> Fetching origin
>>>>>> error: unable to resolve reference
>>>>> refs/remotes/origin/yocto/standard/common-pc-64/base: Not a
>>>>> directory
>>>>>> From git://git.pokylinux.org/linux-yocto-2.6.37
>>>>>> ! [new branch] yocto/standard/common-pc-64/base ->
>>>>> origin/yocto/standard/common-pc-64/base (unable to update local ref)
>>>>>> error: unable to resolve reference
>>>>
>>>> This is due to the way that git manages things on disk. In
>>>> this case, make sure to completely remove your old downloaded
>>>> copy of the repo and re-fetch.
>>>>
>>> Yes, I am working from clean downloads,
>> Saul, you're saying that you're testing the clean downloads or the fetch
>> failures you ran into was from a clean download?
>>
> Both, I am pretty much dead in the water right now, I can't build a
> complete system at all.
>
> I have removed git* from my downloads and started with a clean build
> area. Git fetches are not working.

The problem here is that the mirrors are causing problems
now. I don't have (any) access to address this, but if
anyone is block on a local build, feel free to ping me
and I can show you what you can do to get your build
up and running.

I've sent Richard some information resulting from tests
I ran this morning, and that should fixup the fetching for
incremental builds. Purging the mirrors may be a different
question, since in my tests the fetches are returning remote
refs to branches that have been deleted a month ago.

Bruce

>
> Sau!
>
>> I remembered hearing this
>>> before I am going to test some of Richard's changes in a private
>>> branch but right now, I am deal in the water getting more testing
>>> done!
>>>
>>> Sau!
>>>
>>>> I'm trying to find a way to have git properly deal with
>>>> this at the moment.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>>> refs/remotes/origin/yocto/standard/common-pc-64/sugarbay: Not a
>>>>> directory
>>>>>> ! [new branch] yocto/standard/common-pc-64/sugarbay ->
>>>>> origin/yocto/standard/common-pc-64/sugarbay (unable to update local
>>>>> ref)
>>>>>> error: some local refs could not be updated; try running
>>>>>> 'git remote prune origin' to remove any old, conflicting branches
>>>>>> error: Could not fetch origin Function 'Fetch failed: Unable to
>>>>>> fetch URL
>>>>>
>> git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;fullclone=1;branch=y
>>
>> octo/standard/base;name=machine
>>>>>
>>>>> from any source.' failed
>>>>>> ERROR: Function 'Fetch failed: Unable to fetch URL
>>>>>
>> git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;fullclone=1;branch=y
>>
>> octo/standard/base;name=machine
>>>>>
>>>>> from any source.' failed
>>>>> NOTE: package
>>>>>
>> linux-libc-headers-yocto-2.6.37+git-0+a9d833fda90e2f1257888a97e092135610b5f2
>>
>> 59_0+standard-r2:
>>>>>
>>>>> task Fetch failed: Unable to fetch URL
>>>>>
>> git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;fullclone=1;branch=y
>>
>> octo/standard/base;name=machine
>>>>>
>>>>> from any source.: Failed
>>>>> NOTE: package gcc-cross-4.5.1-r2: task do_unpack: Started
>>>>> ERROR: Task 441
>>>>>
>> (/home/jzhang/poky-master/meta/recipes-kernel/linux-libc-headers/linux-libc-
>>
>> headers-yocto_git.bb,
>>>>>
>>>>> do_fetch) failed with exit code '1'
>>>>> Thanks,
>>>>> Jessica
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto@yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>>
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>



      reply	other threads:[~2011-02-04 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  5:20 [poky] meta-toolchain build failed on fetch Zhang, Jessica
2011-02-04  7:38 ` Saul Wold
2011-02-04 14:16 ` Bruce Ashfield
2011-02-04 16:32   ` Saul Wold
2011-02-04 16:43     ` Zhang, Jessica
2011-02-04 18:14       ` Saul Wold
2011-02-04 18:48         ` Bruce Ashfield [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=4D4C4A03.3070400@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=saul.wold@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.