All of lore.kernel.org
 help / color / mirror / Atom feed
* git works standalone, but not within yocto for weird Azure Devops ssh uri
@ 2018-09-19  9:05 Jakob Hasse
  2018-09-20 13:49 ` Evan O'Loughlin
  2018-10-03  6:14 ` git works standalone, but not within yocto for certain ssh uri format Jakob Hasse
  0 siblings, 2 replies; 5+ messages in thread
From: Jakob Hasse @ 2018-09-19  9:05 UTC (permalink / raw)
  To: Yocto List; +Cc: Andrii Voloshyn

[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]

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"

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"
    SRC_URI_append = "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
T: +41 44 552 02 66

Qiio GmbH
www.qiio.com


[-- Attachment #2: Type: text/html, Size: 2879 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: git works standalone, but not within yocto for weird Azure Devops ssh uri
  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
  2018-10-03  6:14 ` git works standalone, but not within yocto for certain ssh uri format Jakob Hasse
  1 sibling, 1 reply; 5+ messages in thread
From: Evan O'Loughlin @ 2018-09-20 13:49 UTC (permalink / raw)
  To: Jakob Hasse; +Cc: Yocto List, Andrii Voloshyn


________________________________________
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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* git works standalone, but not within yocto for certain ssh uri format
  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  6:14 ` Jakob Hasse
  2018-10-04 10:29   ` Bas Mevissen
  1 sibling, 1 reply; 5+ messages in thread
From: Jakob Hasse @ 2018-10-03  6:14 UTC (permalink / raw)
  To: Yocto List; +Cc: Andrii Voloshyn

[-- Attachment #1: Type: text/plain, Size: 2722 bytes --]

Hello again,

I looked up the git man page and confirmed that the given SSH URI is valid, in fact, the "v3" is just part of the path. No need to explicitly specify a port number. As already mentioned, git works fine when cloning standalone.
Furthermore, if I add a slash after the colon, the Yocto fetcher works fine:

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>

Is there a workaround for this problem? Has anyone experienced this before?

All the Best,
Jakob

On 19.09.2018 11:05, Jakob Hasse wrote:
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>


--
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>

[-- Attachment #2: Type: text/html, Size: 4098 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: git works standalone, but not within yocto for weird Azure Devops ssh uri
  2018-09-20 13:49 ` Evan O'Loughlin
@ 2018-10-03  7:03   ` Jakob Hasse
  0 siblings, 0 replies; 5+ messages in thread
From: Jakob Hasse @ 2018-10-03  7:03 UTC (permalink / raw)
  To: Evan O'Loughlin; +Cc: Yocto List, Andrii Voloshyn

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: git works standalone, but not within yocto for certain ssh uri format
  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
  0 siblings, 0 replies; 5+ messages in thread
From: Bas Mevissen @ 2018-10-04 10:29 UTC (permalink / raw)
  To: Jakob Hasse; +Cc: Yocto List, Andrii Voloshyn

On 2018-10-03 08:14, Jakob Hasse wrote:

> Hello again,
> 
> I looked up the git man page and confirmed that the given SSH URI is 
> valid, in fact, the "v3" is just part of the path. No need to 
> explicitly specify a port number. As already mentioned, git works fine 
> when cloning standalone.
> Furthermore, if I add a slash after the colon, the Yocto fetcher works 
> fine:
> 
> SRC_URI = 
> "gitsm://my-company@vs-ssh.visualstudio.com:/v3/my-company/IoTSolutions/my-app"
> 
> Is there a workaround for this problem? Has anyone experienced this 
> before?

No experience with Azure. On Bitbucket, a private Git repo might be 
defined with:

SRC_URI = "git://git@bitbucket.org/<project>/<repo>.git;protocol=ssh"

So in your case I think it should look like:

SRC_URI = 
"gitsm://git@vs-ssh.visualstudio.com/v3/my-company/IoTSolutions/my-app.git;protocol=ssh"

(or try omitting the .git from the SRC_URI)

Regards,

-- Bas.











^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-10-04 10:29 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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.