From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Can't fetch git SRC_URI via HTTP
Date: Wed, 03 Oct 2012 15:07:27 +0100 [thread overview]
Message-ID: <1889683.vhv9f2oRm3@helios> (raw)
In-Reply-To: <CAMKF1sr_-YjqDeaSY-T68tiFQbCKQeGG9Yu99MFcDKf1pZx-HA@mail.gmail.com>
On Wednesday 03 October 2012 07:04:06 Khem Raj wrote:
> On Wed, Oct 3, 2012 at 12:39 AM, Julian Scheel <julian@jusst.de> wrote:
> > Am Dienstag, den 02.10.2012, 23:52 +0200 schrieb Martin Jansa:
> >> On Tue, Oct 02, 2012 at 11:38:08PM +0200, Julian Scheel wrote:
> >> > Am 02.10.2012 um 23:22 schrieb Martin Jansa <martin.jansa@gmail.com>:
> >> > > On Tue, Oct 02, 2012 at 05:17:23PM -0400, Evade Flow wrote:
> >> > >> I'm trying to build core-image-sato for my Pandaboard ES, following
> >> > >> the
> >> > >>
> >> > >> instructions posted here:
> >> > >> - http://maniacbug.wordpress.com/2012/08/03/pandayocto/
> >> > >>
> >> > >> Thus, my OE build configuration looks like this:
> >> > >>> OE Build Configuration:
> >> > >>> BB_VERSION = "1.15.2"
> >> > >>> TARGET_ARCH = "arm"
> >> > >>> TARGET_OS = "linux-gnueabi"
> >> > >>> MACHINE = "pandaboard"
> >> > >>> DISTRO = "poky"
> >> > >>> DISTRO_VERSION = "1.2.1"
> >> > >>> TUNE_FEATURES = "armv7a vfp neon cortexa9"
> >> > >>> TARGET_FPU = "vfp-neon"
> >> > >>> meta
> >> > >>> meta-yocto =
> >> > >>> "denzil:65ffa7395055f7e012cb973f63f92380828eed0d"
> >> > >>> meta-ti =
> >> > >>> "(nobranch):30fb40ebc13614a74c2e237927c60ac43e01d1bc"
> >> > >>
> >> > >> I have these lines in my .gitconfig:
> >> > >>> [http]
> >> > >>>
> >> > >>> proxy=http://user:passwd@usaprox.lightning.com:8080
> >> > >>
> >> > >> so I'd expect URLs like this one (from the meta-ti layer's
> >> > >>
> >> > >> linux-omap4_3.1.0.bb recipe) to work fine:
> >> > >>> SRC_URI =
> >> > >>> "http://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;pro
> >> > >>> tocol=git;branch=ti-ubuntu-3.1-1282 \>> > >
> >> > > This url seems wrong, it should start with git:// if you want to
> >> > > clone
> >> > > git repo.
> >> > >
> >> > > Because it starts with http:// normal fetch (like wget) was used so
> >> > > it
> >> > > downloaded probably some http code (see that kernel-ubuntu.git file)
> >> > > instead of any relevant source.
> >> >
> >> > I ran into the same issue a few days ago. It seems yocto only supports
> >> > git fetch through servers providing the repositories through the git
> >> > protocol. A way to use git repositories which are provided through
> >> > http or https would be quite a good thing to have.
> >>
> >> That's what protocol param does;
> >>
> >> Change that to
> >> git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;protocol=htt
> >> p;branch=ti-ubuntu-3.1-1282 and you'll get git fetch over http protocol.
> >
> > Nice to know. Actually when I had this issue I tried it the other way
> > round. Use a http url and set protocol to git...
> > Is this noted somewhere in the documentation? I could not find it. I
> > think it would be worth mentioning it in the yocto reference manual as
> > this seems to be a quite common thing to struggle with.
>
> I think Paul posted a patch where bitbake will spit out a good error
> message about such usage
Indeed, in fact coincidentally I was just trying to find this thread in my
cluttered inbox in order to reply to it mentioning that :)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-03 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 21:17 Can't fetch git SRC_URI via HTTP Evade Flow
2012-10-02 21:22 ` Martin Jansa
2012-10-02 21:38 ` Julian Scheel
2012-10-02 21:52 ` Martin Jansa
2012-10-02 22:01 ` Evade Flow
2012-10-03 7:39 ` Julian Scheel
2012-10-03 14:04 ` Khem Raj
2012-10-03 14:07 ` Paul Eggleton [this message]
2012-10-03 14:30 ` Evade Flow
2012-10-03 6:37 ` Khem Raj
2012-10-02 22:09 ` Scott Garman
2012-10-02 22:20 ` Martin Jansa
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=1889683.vhv9f2oRm3@helios \
--to=paul.eggleton@linux.intel.com \
--cc=raj.khem@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.