All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Hasse <jakob.hasse@qiio.com>
To: Evan O'Loughlin <evan.oloughlin@vitalograph.ie>
Cc: Yocto List <yocto@yoctoproject.org>,
	Andrii Voloshyn <andrii.voloshyn@qiio.com>
Subject: Re: git works standalone, but not within yocto for weird Azure Devops ssh uri
Date: Wed, 3 Oct 2018 07:03:32 +0000	[thread overview]
Message-ID: <7640d655-3c25-15e8-8484-7f8f9fbe2c73@qiio.com> (raw)
In-Reply-To: <2EE3E45FEAD8944697CC29BFE83DD70F289B9403@VitalExchange.vitalograph.local>

Hi Evan,

Thank you very much for the answer!
I tried your format as well, unfortunately still had the same problem. 
It looks to me a bit like a bug in the bitbake/Yocto code processing the 
fetch URL.

But I'll investigate further later.

All the Best,
Jakob

On 20.09.2018 15:49, Evan O'Loughlin wrote:
> ________________________________________
> From: yocto-bounces@yoctoproject.org [yocto-bounces@yoctoproject.org] on behalf of Jakob Hasse [jakob.hasse@qiio.com]
> Sent: 19 September 2018 10:05
> To: Yocto List
> Cc: Andrii Voloshyn
> Subject: [yocto] git works standalone, but not within yocto for weird Azure Devops ssh uri
>
> Hello,
>
> I have several projects hosted in Azure DepOs (former Visual Studio online).
> When I glone them with git inside my host machine or the Ubuntu 16.04 container, everything works fine. When I use bitbake to build the recipe with the same ssh uri, it fails (yocto inside Ubuntu 16.04 container).
>
> The SCR_URI in my recipe looks like this:
>
> SRC_URI = "gitsm://XXX@vs-ssh.visualstudio.com:v3/XXX-app"<mailto:gitsm://XXX@vs-ssh.visualstudio.com:v3/XXX-app>
>
> What strikes me is the weird "v3" in the app uri, with the other ssh uris not containing this but the ssh port (22) instead, I didn't have any problem so far.
> I also upgraded git to version 2.17 or 2.19 or so already.
>
> Does anyone have a solution for this?
> The actual recipe looks like this:
>
> DESCRIPTION = "My app"
> LICENSE = "CLOSED"
> SECTION = "app"
>
> # util-linux is for some uuid headers
> DEPENDS = "openssl curl u-boot-fw-utils restart-me util-linux"
>
> SRC_URI = "gitsm://my-company@vs-ssh.visualstudio.com:v3/my-company/IoTSolutions/my-app"<mailto:gitsm://my-company@vs-ssh.visualstudio.com:v3/my-company/IoTSolutions/my-app>
> SRC_URI_append = "file://start_my-app.sh"<file://start_my-app.sh>
>
> SRCREV_pn-my-app = "356dfb095d4b162120f43769cd5b23c7f5a15bd0"
> #SRCREV_pn-swisscom-app = "${AUTOREV}"
> S = "${WORKDIR}/git"
>
> inherit cmake update-rc.d
>
> INITSCRIPT_NAME = "start_my-app.sh"
> INITSCRIPT_PARAMS = "start 23 3 5 ."
>
> EXTRA_OECMAKE = ""
>
> do_install() {
>      install -d ${D}${bindir}
>      install -m 0755 ${S}/bin/my-app ${D}${bindir}/my-app
>      chrpath -d ${D}${bindir}/my-app
>
>      install -d ${D}${sysconfdir}/init.d
>
>      install -c -m 755 ${WORKDIR}/${INITSCRIPT_NAME} ${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
> }
>
> All the Best
> Jakob
>
>
> --
> Jakob Hasse
> Software Developement
>
> E: jakob.hasse@qiio.ch<mailto:jakob.hasse@qiio.ch>
> T: +41 44 552 02 66
>
> Qiio GmbH
> www.qiio.com<http://www.qiio.com>
>
>
> Hi Jacob,
>
> I had a similar issue setting-up my recipe recently.
>
> Our git server uses ssh key authentication and i finally got it working using the following SRC_URI in my recipe:
> SRC_URI = "git://user@server:ProjectName;protocol=file;branch=DevBranch"
>
>
> Hope this helps,
>
> Regards,
> Evan
>
> .
>

-- 
Jakob Hasse
Software Developement

E: jakob.hasse@qiio.ch
T: +41 44 552 02 66

Qiio GmbH
www.qiio.com


  reply	other threads:[~2018-10-03 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  9:05 git works standalone, but not within yocto for weird Azure Devops ssh uri Jakob Hasse
2018-09-20 13:49 ` Evan O'Loughlin
2018-10-03  7:03   ` Jakob Hasse [this message]
2018-10-03  6:14 ` git works standalone, but not within yocto for certain ssh uri format Jakob Hasse
2018-10-04 10:29   ` Bas Mevissen

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=7640d655-3c25-15e8-8484-7f8f9fbe2c73@qiio.com \
    --to=jakob.hasse@qiio.com \
    --cc=andrii.voloshyn@qiio.com \
    --cc=evan.oloughlin@vitalograph.ie \
    --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.