From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] fetch/git: Change to use clearer ssh url syntax for broken servers
Date: Wed, 13 Jan 2016 22:19:42 +0000 [thread overview]
Message-ID: <1452723582.28375.118.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=Xb6HHZm0BaqtGeCUknP1_dTy6t1L7LtZru9F+=j-BmSg@mail.gmail.com>
On Wed, 2016-01-13 at 13:37 -0800, Andre McCurdy wrote:
> On Thu, Jan 7, 2016 at 5:18 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Some servers, e.g. bitbucket.org can't cope with ssh:// as part of
> > the git url syntax. git itself is happy enough with this but you
> > get server side errors when using it.
> >
> > This changes the git fetcher to use the more common ssh url format
> > which also means we need a : before the path.
>
> This seems to break SRC_URIs using ssh to access self hosted git
> servers setup following the process described here:
>
> https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Ser
> ver
>
> An example of such a SRC_URI, which now fails to work:
>
> SRC_URI = "git
> ://git@mylocalserver.com:/opt/git/myrepo.git;protocol=ssh"
Does:
SRC_URI = "git://git@mylocalserver.com/opt/git/myrepo.git;protocol=ssh"
work though?
I'm not sure we ever suggested people should use ":/" in SRC_URI since
that isn't a url format the system was ever designed to cope with. It
might have happened to work but that is different...
Cheers,
Richard
next prev parent reply other threads:[~2016-01-13 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 13:18 [PATCH] fetch/git: Change to use clearer ssh url syntax for broken servers Richard Purdie
2016-01-13 21:37 ` Andre McCurdy
2016-01-13 22:19 ` Richard Purdie [this message]
2016-01-13 23:20 ` Andre McCurdy
2016-01-13 23:59 ` Andre McCurdy
2016-01-14 14:47 ` Peter Kjellerstedt
2016-01-14 15:25 ` Richard Purdie
2016-01-14 16:51 ` Andre McCurdy
2016-01-14 17:07 ` Olof Johansson
2016-01-14 17:50 ` Peter Kjellerstedt
2016-01-15 15:04 ` Richard Purdie
2016-01-15 16:18 ` Olof Johansson
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=1452723582.28375.118.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=bitbake-devel@lists.openembedded.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.