All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Jate S <jatedev@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: linux-yocto fetch bottleneck
Date: Mon, 24 Mar 2014 17:25:17 -0600	[thread overview]
Message-ID: <5330BEDD.3020607@mlbassoc.com> (raw)
In-Reply-To: <CAPphmgZ8ix__X7uvJzuGmiFOTZpcKydCoS-X5Vs15GKA-ujW6Q@mail.gmail.com>

On 2014-03-24 17:18, Jate S wrote:
> What is the name of the mirror tarball that's created? I am trying to
> see if it worked. I saw no log messages stating "Creating tarball of
> git repository".

It will look something like this (for the opkg-utils_git recipe)
  downloads/git2_git.yoctoproject.org.opkg-utils.tar.gz

You should then  arrange to move/copy any of these tarballs to your mirror
so you benefit from this the next time around (when building in a new/different
build tree)

> On Fri, Mar 21, 2014 at 6:04 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2014-03-21 15:54, Jate S wrote:
>>> The documentation has warnings of space usage. Will it start using
>>> lots of space? If so, can I use it on a per mirror basis?
>>
>> Yes, the tarballs can be quite large, but they are incredibly useful
>> with a local mirror.  Especially when you consider that updating a GIT
>> checkout, e.g. the Linux kernel. can take a *really* long time.
>>
>>> I am using a local mirror, so maybe the space usage will not be a problem.
>>
>> The space needed will not be terribly different than what you've already
>> encountered without generating the tarballs.
>>
>> n.b. it's polite to keep replies on the mailing list so that everyone benefits.
>>
>>> On Fri, Mar 21, 2014 at 5:33 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> On 2014-03-21 15:27, Jate S wrote:
>>>>> I am running into a bottleneck with the linux-yocto recipe on dora
>>>>> 1.5.1. The fetch retrieves git2_git.yoctoproject.org.git.tar.gz, but
>>>>> then it hits a bottleneck when it must do a git fetch to update to the
>>>>> required references. The git server does not have high bandwdith.
>>>>>
>>>>> One workaround that I've found is to archive the git repository and
>>>>> replace the tar.gz in the downloads directory. The recipe then finds
>>>>> the required references.
>>>>>
>>>>> Would BB_GENERATE_MIRROR_TARBALLS actually take care of this? Any
>>>>> other recommendations?
>>>>
>>>> Yes, that's exactly what BB_GENERATE_MIRROR_TARBALLS does.  The updated
>>>> tarball will end up in your downloads directory.  If you use any sort of
>>>> local mirror, you'll want to push the new tarball to it for the next time.
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------

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


      reply	other threads:[~2014-03-24 23:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 21:27 linux-yocto fetch bottleneck Jate S
2014-03-21 21:33 ` Gary Thomas
     [not found]   ` <CAPphmgbHhHMRTAGtXMsHfbHR6FuQa7MODGW_UQY22xCO2Z38MQ@mail.gmail.com>
2014-03-21 22:04     ` Gary Thomas
2014-03-24 23:18       ` Jate S
2014-03-24 23:25         ` 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=5330BEDD.3020607@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=jatedev@gmail.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.