archive mirror
 help / color / mirror / Atom feed
From: Alberto Pianon <>
To: Khem Raj <>
Subject: Re: [bitbake-devel] [PATCH] upstream source tracing: data collection (patch 2/3)
Date: Thu, 27 Apr 2023 16:10:39 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Khem,

Il 2023-04-27 09:02 Alberto Pianon ha scritto:

     Il 2023-04-27 08:56 Khem Raj ha scritto:

         On Wed, Apr 26, 2023 at 10:19 PM Alberto Pianon 
<> wrote:

             Il 2023-04-27 07:14 Alberto Pianon ha scritto:

                 Could you please check if this is really the case in 
your case?
                 You'd need to go to 
                 (check where the layer is located in your filesystem) 
and do

             Of course it is located at


             Please check also the other two files for which you get the 

         My distro uses git submodules at top level and poky is a 
submodule see

         git rev-parse --is-inside-work-tree

         % git status
         HEAD detached at 5a944d32a1
         nothing to commit, working tree clean

     so something's wrong... I'll build your distro and try to find the 

first of all kudos for Yoe, it's one of the simpler-to-build distros I 
ever tried, it seems you did a very good job there :)

BTW, I couldn't reproduce the problem, since I don't get any warning 
message, and the upstream sources are correctly identified, eg. in 
I find:

     "layer": "meta",
     "files": {
       "": {
         "sha1": "856c3f6bf74a1b11e90b0ade0b4aeecbb3babfff",
         "paths_in_workdir": [

... which is the expected result (while on the same file you get a 
warning that the download_location has not been identified).

Could you please double-check the output of git commands in 
and in other dirs?



  parent reply	other threads:[~2023-04-27 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  6:21 [PATCH] upstream source tracing: data collection (patch 2/3) alberto
2023-04-27  3:49 ` [bitbake-devel] " Khem Raj
2023-04-27  5:14   ` Alberto Pianon
2023-04-27  5:18     ` Alberto Pianon
2023-04-27  6:56       ` Khem Raj
2023-04-27  7:02         ` Alberto Pianon
     [not found]         ` <>
2023-04-27 14:10           ` Alberto Pianon [this message]
2023-04-27 19:40             ` Khem Raj
2023-04-28  7:47               ` Alberto Pianon
2023-04-28 13:47                 ` Khem Raj
2023-05-02 10:44                   ` Alberto Pianon
2023-05-02 16:41                     ` Alberto Pianon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).