From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: lei yang <yanglei.fage@gmail.com>
Cc: bitbake-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] git address in SRC_URI, doesn't works for me
Date: Tue, 22 Jan 2013 10:36:56 +0000 [thread overview]
Message-ID: <3325513.8ZibJSvNVU@helios> (raw)
In-Reply-To: <CAHsH0E96h=aT6t-u-ACY7MGFHJv4_TTqSMfCmMpSKiq3NBjciw@mail.gmail.com>
On Saturday 19 January 2013 17:13:01 lei yang wrote:
> One git address's prefix is "http" --->
> http://git.opensvc.com/multipath-tools/.git,
>
> it means
>
> git clone http://git.opensvc.com/multipath-tools/.git ---------> works
> git clone git://git.opensvc.com/multipath-tools/.git ---------> doesn't work
>
> I tried SRC_URI with below, both failed
>
> SRC_URI = "http://git.opensvc.com/multipath-tools/.git;protocol=git"
> it tells
> fatal: reference is not a tree: c23c0d33ed98a1dcee40115018b73cb3d4cda8d7
>
>
> SRC_URI = "git://git.opensvc.com/multipath-tools/.git;protocol=http"
> it doe noting,and trying to find COPING,but it doesn't clone it
I think you already got this answered on IRC, but for reference you need to
use git://....;protocol=http and not http://.....;protocol=git. BitBake uses
the prefix to determine which fetcher to use (matching the type of repository
being fetched from) and then each individual fetcher decides the meaning of
the protocol argument. In this case you're fetching from a git repository
using the HTTP transport protocol.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: lei yang <yanglei.fage@gmail.com>
Cc: bitbake-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: git address in SRC_URI, doesn't works for me
Date: Tue, 22 Jan 2013 10:36:56 +0000 [thread overview]
Message-ID: <3325513.8ZibJSvNVU@helios> (raw)
In-Reply-To: <CAHsH0E96h=aT6t-u-ACY7MGFHJv4_TTqSMfCmMpSKiq3NBjciw@mail.gmail.com>
On Saturday 19 January 2013 17:13:01 lei yang wrote:
> One git address's prefix is "http" --->
> http://git.opensvc.com/multipath-tools/.git,
>
> it means
>
> git clone http://git.opensvc.com/multipath-tools/.git ---------> works
> git clone git://git.opensvc.com/multipath-tools/.git ---------> doesn't work
>
> I tried SRC_URI with below, both failed
>
> SRC_URI = "http://git.opensvc.com/multipath-tools/.git;protocol=git"
> it tells
> fatal: reference is not a tree: c23c0d33ed98a1dcee40115018b73cb3d4cda8d7
>
>
> SRC_URI = "git://git.opensvc.com/multipath-tools/.git;protocol=http"
> it doe noting,and trying to find COPING,but it doesn't clone it
I think you already got this answered on IRC, but for reference you need to
use git://....;protocol=http and not http://.....;protocol=git. BitBake uses
the prefix to determine which fetcher to use (matching the type of repository
being fetched from) and then each individual fetcher decides the meaning of
the protocol argument. In this case you're fetching from a git repository
using the HTTP transport protocol.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-01-22 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 9:13 git address in SRC_URI, doesn't works for me lei yang
2013-01-20 2:15 ` Chris Larson
2013-01-20 2:15 ` [bitbake-devel] " Chris Larson
2013-01-20 4:27 ` lei yang
2013-01-20 4:27 ` [bitbake-devel] " lei yang
2013-01-20 6:08 ` lei yang
2013-01-20 6:08 ` [bitbake-devel] " lei yang
2013-01-20 14:05 ` Bernhard Reutner-Fischer
2013-01-20 14:05 ` [bitbake-devel] " Bernhard Reutner-Fischer
2013-01-20 20:07 ` Chris Larson
2013-01-20 20:07 ` [bitbake-devel] " Chris Larson
2013-01-22 10:36 ` Paul Eggleton [this message]
2013-01-22 10:36 ` Paul Eggleton
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=3325513.8ZibJSvNVU@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yanglei.fage@gmail.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.