From: "Roos, Thomas" <throos@amazon.de>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: devtool upgrade for go recipes with git "broken"
Date: Thu, 20 Oct 2022 09:18:30 +0000 [thread overview]
Message-ID: <1028eccc021a4bf5ab2520b3c4fb82a6@amazon.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Hi,
when doing a "devtool upgrade" for a recipe which inherits "go" and using a SRC_URI to a git repo this will fail. Complaining that the git revision is "out of tree" - I found that the additional "src" folder inside the checkout out sources is causing this problem and I wondering if this is necessary. I'm not a go programmer, but when changing this the recipe seems to produce the same result.
I did change our go recipe to don't use this additional src folder by overwriting the go_do_upack and go_do_configure method. Here: https://github.com/aws4embeddedlinux/meta-aws/blob/942651026c7a91b9703609d7658bd1649350acaf/recipes-support/amazon-ssm-agent/amazon-ssm-agent_3.1.1856.0.bb
Is this a bug or do anybody know why go use that additional src folder?
Cheers,
Thomas
Amazon Web Services EMEA SARL
38 avenue John F. Kennedy, L-1855 Luxembourg
Sitz der Gesellschaft: L-1855 Luxemburg
eingetragen im Luxemburgischen Handelsregister unter R.C.S. B186284
Amazon Web Services EMEA SARL, Niederlassung Deutschland
Marcel-Breuer-Str. 12, D-80807 Muenchen
Sitz der Zweigniederlassung: Muenchen
eingetragen im Handelsregister des Amtsgerichts Muenchen unter HRB 242240, USt-ID DE317013094
[-- Attachment #2: Type: text/html, Size: 1938 bytes --]
next reply other threads:[~2022-10-20 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 9:18 Roos, Thomas [this message]
2022-10-20 9:32 ` [yocto] devtool upgrade for go recipes with git "broken" Alexander Kanavin
2022-10-20 9:50 ` AW: " Roos, Thomas
2022-10-20 9:56 ` Alexander Kanavin
2022-10-20 10:05 ` AW: " Roos, Thomas
2022-10-20 10:09 ` Alexander Kanavin
2022-10-20 10:22 ` AW: " Roos, Thomas
2022-10-20 10:40 ` Alexander Kanavin
2022-10-20 10:45 ` Monsees, Steven C (US)
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=1028eccc021a4bf5ab2520b3c4fb82a6@amazon.de \
--to=throos@amazon.de \
--cc=yocto@lists.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.