All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: poky@o-hand.com
Subject: Re: SVN woes persist
Date: Sat, 23 Oct 2010 01:56:06 +0100	[thread overview]
Message-ID: <1287795366.16386.801.camel@rex> (raw)
In-Reply-To: <4CC1D026.7050408@mlbassoc.com>

On Fri, 2010-10-22 at 11:55 -0600, Gary Thomas wrote:
> On 10/22/2010 08:29 AM, Richard Purdie wrote:
> > On Fri, 2010-10-22 at 08:04 -0600, Gary Thomas wrote:
> >> Will do.
> >>
> >> Should this address the similar issue with GIT packages.  These seem
> >> to be updating every time as well:
> >>     git_github.com.wrpseudo.pseudo.git.tar.gz
> >>     git_git.pokylinux.org.wr-kernel-tools.git.tar.gz
> >>     git_git.pokylinux.org.prelink-cross.git.tar.gz
> >
> > There are changes in master which will stop everything except the
> > linux-wrs recipe doing that. The linux-wrs recipe uses "fullclone" mode
> > of the git fetcher and this has known issues which we will address soon.
> >
> > If anything other than linux-wrs is refreshing on master other than that
> > recipe, let us know.
> 
> Looks good.  The one one that got updated today with a full build was pseudo
> and that's because the pinned revision was changed since I last merged.

Right, once its generated its tarball, it shouldn't touch the repo
again.

> >> I'm still hoping for a way to have a static (no network needed) setup
> >> soon.  I have to provide such in a training for some of my customers
> >> in about a month :-)
> >
> > It is meant to work like that!
> 
> This part is working much better now, thanks.
> 
> Any progress on a way to hot-start things with the staged packages?
> When last I tried it, it brought my system to its knees with no benefit
> (see original message from 2010-10-07)

I thought my last email made this clear, we've fixed issues, it works
better now.

Unfortunately there is an issue with the bits of the toolchain
overwriting each other so a build using the packages isn't entirely
working but you can for example generate images using them. All the
pieces are there and we just need to iron out a few bugs.

Cheers,

Richard



      reply	other threads:[~2010-10-23  0:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CADD32A.9010908@mlbassoc.com>
     [not found] ` <1286462951.15840.6345.camel@rex>
     [not found]   ` <4CADE06F.6040308@mlbassoc.com>
     [not found]     ` <4CADFA77.3070305@mlbassoc.com>
     [not found]       ` <1286475616.15840.6565.camel@rex>
     [not found]         ` <4CAE54A1.1080803@mlbassoc.com>
2010-10-22 13:50           ` SVN woes persist Richard Purdie
2010-10-22 14:04             ` Gary Thomas
2010-10-22 14:29               ` Richard Purdie
2010-10-22 17:55                 ` Gary Thomas
2010-10-23  0:56                   ` Richard Purdie [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=1287795366.16386.801.camel@rex \
    --to=rpurdie@linux.intel.com \
    --cc=gary@mlbassoc.com \
    --cc=poky@o-hand.com \
    /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.