All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: ALT_SRC_URI ?
Date: Wed, 30 May 2012 18:12:43 +0100	[thread overview]
Message-ID: <1338397963.20169.170.camel@ted> (raw)
In-Reply-To: <CAEsOVNfUrVFO-zqO-G2Ci958_oUGSzUnpOG-3dL8X_bS-R_1UQ@mail.gmail.com>

On Wed, 2012-05-30 at 16:08 +0000, McClintock Matthew-B29882 wrote:
> On Wed, May 30, 2012 at 9:20 AM, David Nyström <david.nystrom@enea.com> wrote:
> > Hi,
> >
> > Since meta-fsl-ppc:s git daemon(git://git.freescale.com) was down, I
> > experimented with adding the http reference as a mirror.
> >
> > MIRRORS_prepend = "\
> > git://git.freescale.com/ppc/sdk/linux.git
> > git://git.freescale.com/git/cgit.cgi/ppc/sdk/linux.git;protocol=http \n "
> >
> > Which failed and gave me:
> > http://pastebin.com/5sTQ0eMC
> >
> > It shows bitbake trying to fetch something assumed to be created as a
> > bitbake mirror, mangling the name.
> >
> > How would I go about doing above ?, getting it to failover to my own
> > specified link ?
> 
> It appears to expect mirrors to be in a tarred up bare git repository.
> Not sure if there is a way around this. You could do an override
> somewhere:
> 
> SRC_URI_pn-linux-qoriq-sdk = "git://some/other/place"

There is an open bug on this issue. Fixing it requires some invasive
changes to the fetcher code so its not been done yet and I wanted to get
the checksum issues out the way first.

Cheers,

Richard



      reply	other threads:[~2012-05-30 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 14:20 ALT_SRC_URI ? David Nyström
2012-05-30 16:08 ` McClintock Matthew-B29882
2012-05-30 17:12   ` 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=1338397963.20169.170.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B29882@freescale.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.