bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Alberto Pianon <alberto@pianon.eu>
Cc: bitbake-devel@lists.openembedded.org,
	richard.purdie@linuxfoundation.org,  jpewhacker@gmail.com,
	carlo@piana.eu
Subject: Re: [bitbake-devel] [PATCH] upstream source tracing: data collection (patch 2/3)
Date: Fri, 28 Apr 2023 06:47:42 -0700	[thread overview]
Message-ID: <CAMKF1sqwNtQj0c7MhQWzrn+Kkiv5zptf52kktUUqENUUS1sKmg@mail.gmail.com> (raw)
In-Reply-To: <f831364c9b14ac92d527b04fe82713dc@pianon.eu>

On Fri, Apr 28, 2023 at 12:47 AM Alberto Pianon <alberto@pianon.eu> wrote:
>
>
> On 2023-04-27 21:40, Khem Raj wrote:
> > On Thu, Apr 27, 2023 at 7:10 AM Alberto Pianon <alberto@pianon.eu>
> > wrote:
> >>
> >> 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
> >> <alberto@pianon.eu> 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
> >> meta/recipes-sato/matchbox-panel-2/files
> >>                  (check where the layer is located in your filesystem)
> >> and do
> >>
> >>
> >>              Of course it is located at
> >>              /mnt/b/yoe/master/sources/poky/meta/recipes-sato/m
> >>
> >> atchbox-panel-2/files/0001-applets-systray-Allow-icons-to-be-smaller.patch
> >>
> >>              :)
> >>
> >>              Please check also the other two files for which you get
> >> the
> >> warnings
> >>
> >>
> >>          My distro uses git submodules at top level and poky is a
> >> submodule see
> >>          https://github.com/yoedistro/yoe-distro
> >>
> >>          git rev-parse --is-inside-work-tree
> >>          true
> >>
> >>          % 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
> >> problem
> >>      thanks
> >>
> >>
> >> 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
> >> build/tmp/work/cortexa72-yoe-linux/matchbox-keyboard/0.1.1-r0/temp/matchbox-keyboard-0.1.1.unpack.trace.json.zst
> >> I find:
> >>
> >>
> >> "git+https://github.com/yoedistro/poky@5a944d32a1e2baff34eb03b07ec094421a7a8773#meta/recipes-sato/m
> >> atchbox-keyboard/files/0001-desktop-file-Hide-the-keyboard-from-app-list.patch":
> >> {
> >>      "download_location":
> >> "git+https://github.com/yoedistro/poky@5a944d32a1e2baff34eb03b07ec094421a7a8773#meta/recipes-sato/matchbox-keyboard/files/0001-desktop-file-Hide-the-keyboard-from-app-list.patch",
> >>      "src_uri":
> >> "file://0001-desktop-file-Hide-the-keyboard-from-app-list.patch",
> >>      "layer": "meta",
> >>      "files": {
> >>        "": {
> >>          "sha1": "856c3f6bf74a1b11e90b0ade0b4aeecbb3babfff",
> >>          "paths_in_workdir": [
> >>            "0001-desktop-file-Hide-the-keyboard-from-app-list.patch"
> >>          ]
> >>        }
> >>      }
> >>    },
> >>
> >> ... 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
> >> /mnt/b/yoe/master/sources/poky/meta/recipes-sato/matchbox-keyboard/files/
> >> and in other dirs?
> >
> > [kraj@apollo
> > /mnt/b/yoe/master/sources/poky/meta/recipes-sato/matchbox-keyboard/files]
> > % git rev-parse --is-inside-work-tree
> >
> > true
> >
> > Secondly, I am building on archlinux which is uptodate as of
> > yesterday, Default yoe builds in a debian bullseye container
> > so I wonder if thats what is mattering here. in order to not use
> > container with yoe add
> >
> > cp local.sh.example local.sh
> >
> > and add below line to local.sh
> >
> > export DOCKER_REPO=none
> >
> > Then source envsetup again and build.
> >
>
> I tried that, but I got the same (good) results, I get none of the
> warnings you are getting. I'm on Ubuntu 22.04 though... which archlinux
> version are you on?

arch is a rolling distro i am uptodate as of today


  reply	other threads:[~2023-04-28 13:48 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]         ` <1759B8A6082B56AB.32698@lists.openembedded.org>
2023-04-27 14:10           ` Alberto Pianon
2023-04-27 19:40             ` Khem Raj
2023-04-28  7:47               ` Alberto Pianon
2023-04-28 13:47                 ` Khem Raj [this message]
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:
  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=CAMKF1sqwNtQj0c7MhQWzrn+Kkiv5zptf52kktUUqENUUS1sKmg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=alberto@pianon.eu \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=carlo@piana.eu \
    --cc=jpewhacker@gmail.com \
    --cc=richard.purdie@linuxfoundation.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 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).