* [PATCH] buildhistory.bbclass: metadata-revs show repo parent
@ 2016-03-12 2:49 Trevor Woerner
2016-03-12 3:59 ` Khem Raj
2016-03-13 0:34 ` Trevor Woerner
0 siblings, 2 replies; 10+ messages in thread
From: Trevor Woerner @ 2016-03-12 2:49 UTC (permalink / raw)
To: openembedded-core
Currently my build shows two "meta" repositories: one from meta-poky and one
from openembedded-core. Have the code which prints the repositories into
metadata-revs show the parent directories when repositories with multiple
sub-layers are used.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
meta/classes/buildhistory.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/buildhistory.bbclass b/meta/classes/buildhistory.bbclass
index fac7fed..b6b4324 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -616,7 +616,7 @@ def buildhistory_get_build_id(d):
def buildhistory_get_metadata_revs(d):
# We want an easily machine-readable format here, so get_layers_branch_rev isn't quite what we want
layers = (d.getVar("BBLAYERS", True) or "").split()
- medadata_revs = ["%-17s = %s:%s" % (os.path.basename(i), \
+ medadata_revs = ["%-17s = %s:%s" % (os.path.relpath(i, d.getVar('BBLAYERS_FETCH_DIR', True)), \
base_get_metadata_git_branch(i, None).strip(), \
base_get_metadata_git_revision(i, None)) \
for i in layers]
--
2.7.0.rc3
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 2:49 [PATCH] buildhistory.bbclass: metadata-revs show repo parent Trevor Woerner
@ 2016-03-12 3:59 ` Khem Raj
2016-03-12 4:28 ` Trevor Woerner
2016-03-13 0:34 ` Trevor Woerner
1 sibling, 1 reply; 10+ messages in thread
From: Khem Raj @ 2016-03-12 3:59 UTC (permalink / raw)
To: Trevor Woerner; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
On Mar 12, 2016 9:50 AM, "Trevor Woerner" <twoerner@gmail.com> wrote:
>
> Currently my build shows two "meta" repositories: one from meta-poky and
one
> from openembedded-core. Have the code which prints the repositories into
> metadata-revs show the parent directories when repositories with multiple
> sub-layers are used.
Meta-poky is a leaf layer. So how is it offering conflicting meta layer ?
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> meta/classes/buildhistory.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/buildhistory.bbclass
b/meta/classes/buildhistory.bbclass
> index fac7fed..b6b4324 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -616,7 +616,7 @@ def buildhistory_get_build_id(d):
> def buildhistory_get_metadata_revs(d):
> # We want an easily machine-readable format here, so
get_layers_branch_rev isn't quite what we want
> layers = (d.getVar("BBLAYERS", True) or "").split()
> - medadata_revs = ["%-17s = %s:%s" % (os.path.basename(i), \
> + medadata_revs = ["%-17s = %s:%s" % (os.path.relpath(i,
d.getVar('BBLAYERS_FETCH_DIR', True)), \
> base_get_metadata_git_branch(i, None).strip(), \
> base_get_metadata_git_revision(i, None)) \
> for i in layers]
> --
> 2.7.0.rc3
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
[-- Attachment #2: Type: text/html, Size: 2191 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 3:59 ` Khem Raj
@ 2016-03-12 4:28 ` Trevor Woerner
2016-03-12 5:33 ` Trevor Woerner
2016-03-12 21:54 ` Burton, Ross
0 siblings, 2 replies; 10+ messages in thread
From: Trevor Woerner @ 2016-03-12 4:28 UTC (permalink / raw)
To: Khem Raj; +Cc: Patches and discussions about the oe-core layer
On 03/11/16 22:59, Khem Raj wrote:
>
>
> On Mar 12, 2016 9:50 AM, "Trevor Woerner" <twoerner@gmail.com
> <mailto:twoerner@gmail.com>> wrote:
> >
> > Currently my build shows two "meta" repositories: one from meta-poky
> and one
> > from openembedded-core. Have the code which prints the repositories into
> > metadata-revs show the parent directories when repositories with
> multiple
> > sub-layers are used.
>
> Meta-poky is a leaf layer. So how is it offering conflicting meta layer ?
>
There's no conflict, I'm just trying to generate output the
differentiates amongst leaf layers in its output.
Before:
meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
meta-oe = master:a1e135a499998add7575682bf53db5e02e753580
meta-gnome = master:a1e135a499998add7575682bf53db5e02e753580
meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
meta-linaro-toolchain = master:367f784b831938dc508b7d472342d2d0d6ed9769
meta = master:37b61b059031e3c272a929b834e12fd83f46598c
meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
After:
openembedded-core/meta =
master:00d3fd571a8d261d065b43f5cf3076a381843984
meta-openembedded/meta-oe =
master:a1e135a499998add7575682bf53db5e02e753580
meta-openembedded/meta-gnome =
master:a1e135a499998add7575682bf53db5e02e753580
meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
meta-linaro/meta-linaro-toolchain =
master:367f784b831938dc508b7d472342d2d0d6ed9769
meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
So you see how it prints the parent layer for any leaf layers, which is
more descriptive (and better?).
> >
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com
> <mailto:twoerner@gmail.com>>
> > ---
> > meta/classes/buildhistory.bbclass | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/buildhistory.bbclass
> b/meta/classes/buildhistory.bbclass
> > index fac7fed..b6b4324 100644
> > --- a/meta/classes/buildhistory.bbclass
> > +++ b/meta/classes/buildhistory.bbclass
> > @@ -616,7 +616,7 @@ def buildhistory_get_build_id(d):
> > def buildhistory_get_metadata_revs(d):
> > # We want an easily machine-readable format here, so
> get_layers_branch_rev isn't quite what we want
> > layers = (d.getVar("BBLAYERS", True) or "").split()
> > - medadata_revs = ["%-17s = %s:%s" % (os.path.basename(i), \
> > + medadata_revs = ["%-17s = %s:%s" % (os.path.relpath(i,
> d.getVar('BBLAYERS_FETCH_DIR', True)), \
> > base_get_metadata_git_branch(i, None).strip(), \
> > base_get_metadata_git_revision(i, None)) \
> > for i in layers]
> > --
> > 2.7.0.rc3
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> <mailto:Openembedded-core@lists.openembedded.org>
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 4:28 ` Trevor Woerner
@ 2016-03-12 5:33 ` Trevor Woerner
2016-03-12 11:55 ` Khem Raj
2016-03-12 21:54 ` Burton, Ross
1 sibling, 1 reply; 10+ messages in thread
From: Trevor Woerner @ 2016-03-12 5:33 UTC (permalink / raw)
To: Khem Raj; +Cc: Patches and discussions about the oe-core layer
To me, the purpose of buildhistory's metadata-revs is to enable someone
else (or myself in the future) to recreate a specific build, that's why
I always save this file with any build artifacts. Simply saying "meta"
isn't good enough because it doesn't specify which repository's "meta".
So the purpose of this patch is to try to clarify which repositories
we're talking about.
> Before:
> meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
> meta-oe = master:a1e135a499998add7575682bf53db5e02e753580
> meta-gnome = master:a1e135a499998add7575682bf53db5e02e753580
> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
> meta-linaro-toolchain =
> master:367f784b831938dc508b7d472342d2d0d6ed9769
> meta = master:37b61b059031e3c272a929b834e12fd83f46598c
> meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>
> After:
> openembedded-core/meta =
> master:00d3fd571a8d261d065b43f5cf3076a381843984
> meta-openembedded/meta-oe =
> master:a1e135a499998add7575682bf53db5e02e753580
> meta-openembedded/meta-gnome =
> master:a1e135a499998add7575682bf53db5e02e753580
> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
> meta-linaro/meta-linaro-toolchain =
> master:367f784b831938dc508b7d472342d2d0d6ed9769
> meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
> meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
I have a second patch, now, that will generate the following output,
which I think is even better:
git://git.openembedded.org/openembedded-core.git
openembedded-core/meta =
master:00d3fd571a8d261d065b43f5cf3076a381843984
git://git.openembedded.org/meta-openembedded
meta-openembedded/meta-oe =
master:a1e135a499998add7575682bf53db5e02e753580
git://git.openembedded.org/meta-openembedded
meta-openembedded/meta-gnome =
master:a1e135a499998add7575682bf53db5e02e753580
git://github.com/96boards/meta-rpb.git
meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
https://github.com/96boards/meta-96boards.git
meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
https://github.com/ndechesne/meta-qcom.git
meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
git://github.com/OSSystems/meta-browser.git
meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
git://git.linaro.org/openembedded/meta-linaro.git
meta-linaro/meta-linaro-toolchain =
master:367f784b831938dc508b7d472342d2d0d6ed9769
git://git.yoctoproject.org/poky
meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
git://git.yoctoproject.org/poky
meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
Frankly, there are too many forks and clones. There are too many
meta-beaglebone or meta-odroid or meta-raspberrypi repositories. If six
months from now I want to recreate a build I've done today, I'll need to
know the repository, where it's from, and which commit was checked out.
My latest patch provides that information.
Is this better?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 5:33 ` Trevor Woerner
@ 2016-03-12 11:55 ` Khem Raj
2016-03-12 15:26 ` Trevor Woerner
0 siblings, 1 reply; 10+ messages in thread
From: Khem Raj @ 2016-03-12 11:55 UTC (permalink / raw)
To: Trevor Woerner; +Cc: Patches and discussions about the oe-core layer
On Sat, Mar 12, 2016 at 1:33 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> To me, the purpose of buildhistory's metadata-revs is to enable someone else
> (or myself in the future) to recreate a specific build, that's why I always
> save this file with any build artifacts. Simply saying "meta" isn't good
> enough because it doesn't specify which repository's "meta". So the purpose
> of this patch is to try to clarify which repositories we're talking about.
>
>> Before:
>> meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
>> meta-oe = master:a1e135a499998add7575682bf53db5e02e753580
>> meta-gnome = master:a1e135a499998add7575682bf53db5e02e753580
>> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>> meta-linaro-toolchain =
>> master:367f784b831938dc508b7d472342d2d0d6ed9769
>> meta = master:37b61b059031e3c272a929b834e12fd83f46598c
>> meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>>
>> After:
>> openembedded-core/meta =
>> master:00d3fd571a8d261d065b43f5cf3076a381843984
>> meta-openembedded/meta-oe =
>> master:a1e135a499998add7575682bf53db5e02e753580
>> meta-openembedded/meta-gnome =
>> master:a1e135a499998add7575682bf53db5e02e753580
>> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>> meta-linaro/meta-linaro-toolchain =
>> master:367f784b831938dc508b7d472342d2d0d6ed9769
>> meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
>> meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>
>
> I have a second patch, now, that will generate the following output, which I
> think is even better:
>
> git://git.openembedded.org/openembedded-core.git
> openembedded-core/meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
>
> git://git.openembedded.org/meta-openembedded
> meta-openembedded/meta-oe =
> master:a1e135a499998add7575682bf53db5e02e753580
>
> git://git.openembedded.org/meta-openembedded
> meta-openembedded/meta-gnome =
> master:a1e135a499998add7575682bf53db5e02e753580
>
> git://github.com/96boards/meta-rpb.git
> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>
> https://github.com/96boards/meta-96boards.git
> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>
> https://github.com/ndechesne/meta-qcom.git
> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>
> git://github.com/OSSystems/meta-browser.git
> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>
> git://git.linaro.org/openembedded/meta-linaro.git
> meta-linaro/meta-linaro-toolchain =
> master:367f784b831938dc508b7d472342d2d0d6ed9769
>
> git://git.yoctoproject.org/poky
> meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
>
> git://git.yoctoproject.org/poky
> meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>
> Frankly, there are too many forks and clones. There are too many
> meta-beaglebone or meta-odroid or meta-raspberrypi repositories. If six
> months from now I want to recreate a build I've done today, I'll need to
> know the repository, where it's from, and which commit was checked out. My
> latest patch provides that information.
>
> Is this better?
what happens if one has a local checkout forked from upstream branch ?
it reports that one, so buildhistory is expecting you to control the repos
e.g. when using tools like repo, it gets utterly confused since its meant
to track local checkout SHAs not remote ones, may be your change
can establish a better origin tracking. it would be interesting to see
how it works with repo and when I have more than 1 remotes in a single
repo
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 11:55 ` Khem Raj
@ 2016-03-12 15:26 ` Trevor Woerner
0 siblings, 0 replies; 10+ messages in thread
From: Trevor Woerner @ 2016-03-12 15:26 UTC (permalink / raw)
To: Khem Raj; +Cc: Patches and discussions about the oe-core layer
On 03/12/16 06:55, Khem Raj wrote:
> On Sat, Mar 12, 2016 at 1:33 PM, Trevor Woerner <twoerner@gmail.com> wrote:
>> To me, the purpose of buildhistory's metadata-revs is to enable someone else
>> (or myself in the future) to recreate a specific build, that's why I always
>> save this file with any build artifacts. Simply saying "meta" isn't good
>> enough because it doesn't specify which repository's "meta". So the purpose
>> of this patch is to try to clarify which repositories we're talking about.
>>
>>> Before:
>>> meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
>>> meta-oe = master:a1e135a499998add7575682bf53db5e02e753580
>>> meta-gnome = master:a1e135a499998add7575682bf53db5e02e753580
>>> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>>> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>>> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>>> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>>> meta-linaro-toolchain =
>>> master:367f784b831938dc508b7d472342d2d0d6ed9769
>>> meta = master:37b61b059031e3c272a929b834e12fd83f46598c
>>> meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>>>
>>> After:
>>> openembedded-core/meta =
>>> master:00d3fd571a8d261d065b43f5cf3076a381843984
>>> meta-openembedded/meta-oe =
>>> master:a1e135a499998add7575682bf53db5e02e753580
>>> meta-openembedded/meta-gnome =
>>> master:a1e135a499998add7575682bf53db5e02e753580
>>> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>>> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>>> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>>> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>>> meta-linaro/meta-linaro-toolchain =
>>> master:367f784b831938dc508b7d472342d2d0d6ed9769
>>> meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
>>> meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>>
>> I have a second patch, now, that will generate the following output, which I
>> think is even better:
>>
>> git://git.openembedded.org/openembedded-core.git
>> openembedded-core/meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
>>
>> git://git.openembedded.org/meta-openembedded
>> meta-openembedded/meta-oe =
>> master:a1e135a499998add7575682bf53db5e02e753580
>>
>> git://git.openembedded.org/meta-openembedded
>> meta-openembedded/meta-gnome =
>> master:a1e135a499998add7575682bf53db5e02e753580
>>
>> git://github.com/96boards/meta-rpb.git
>> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>>
>> https://github.com/96boards/meta-96boards.git
>> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>>
>> https://github.com/ndechesne/meta-qcom.git
>> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>>
>> git://github.com/OSSystems/meta-browser.git
>> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>>
>> git://git.linaro.org/openembedded/meta-linaro.git
>> meta-linaro/meta-linaro-toolchain =
>> master:367f784b831938dc508b7d472342d2d0d6ed9769
>>
>> git://git.yoctoproject.org/poky
>> meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
>>
>> git://git.yoctoproject.org/poky
>> meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>>
>> Frankly, there are too many forks and clones. There are too many
>> meta-beaglebone or meta-odroid or meta-raspberrypi repositories. If six
>> months from now I want to recreate a build I've done today, I'll need to
>> know the repository, where it's from, and which commit was checked out. My
>> latest patch provides that information.
>>
>> Is this better?
> what happens if one has a local checkout forked from upstream branch ?
> it reports that one, so buildhistory is expecting you to control the repos
> e.g. when using tools like repo, it gets utterly confused since its meant
> to track local checkout SHAs not remote ones, may be your change
> can establish a better origin tracking. it would be interesting to see
> how it works with repo and when I have more than 1 remotes in a single
> repo
Here's how it handled a build that I have where the repositories are
handled by the repo tool:
https://github.com/openembedded/openembedded-core
meta =
contrib/twoerner/buildhistory-patches:953046fa31617a0c53f66faacf3fa9ef88375dee
https://github.com/openembedded/meta-openembedded
../meta-openembedded/meta-oe = HEAD:dc5634968b270dde250690609f0015f881db81f2
https://github.com/openembedded/meta-openembedded
../meta-openembedded/meta-gnome =
HEAD:dc5634968b270dde250690609f0015f881db81f2
https://github.com/96boards/meta-rpb
../meta-rpb = HEAD:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
https://github.com/96boards/meta-96boards
../meta-96boards = HEAD:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
http://git.linaro.org/openembedded/meta-linaro
../meta-linaro/meta-linaro-toolchain =
HEAD:395ca11e22c26bd0c26ea1078722628ba6aa2332
https://github.com/ndechesne/meta-qcom
../meta-qcom = HEAD:32fcda819acb8ec485d9ab05108d554f807bf75d
https://github.com/linaro-home/meta-browser
../meta-browser = HEAD:5c00d0114c5963a178cb33f6d06181c588c03ae0
My patch simply uses "git remote -v" and takes the first line. I'll look
into reporting multiple remotes.
Local forks of upstream repositories would simply be reported as local
repositories. I'm not even sure what I would do on the cmdline to figure
out that sort of repository's origin, other than to manually work
backwards until I found something that looked sensible.
In any case, the above is an improvement?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 4:28 ` Trevor Woerner
2016-03-12 5:33 ` Trevor Woerner
@ 2016-03-12 21:54 ` Burton, Ross
2016-03-12 22:32 ` Trevor Woerner
1 sibling, 1 reply; 10+ messages in thread
From: Burton, Ross @ 2016-03-12 21:54 UTC (permalink / raw)
To: Trevor Woerner; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On 12 March 2016 at 04:28, Trevor Woerner <twoerner@gmail.com> wrote:
> openembedded-core/meta =
> master:00d3fd571a8d261d065b43f5cf3076a381843984
> meta-openembedded/meta-oe =
> master:a1e135a499998add7575682bf53db5e02e753580
> meta-openembedded/meta-gnome =
> master:a1e135a499998add7575682bf53db5e02e753580
> meta-rpb = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
> meta-96boards = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
> meta-qcom = master:32fcda819acb8ec485d9ab05108d554f807bf75d
> meta-browser = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
> meta-linaro/meta-linaro-toolchain =
> master:367f784b831938dc508b7d472342d2d0d6ed9769
> meta-poky/meta = master:37b61b059031e3c272a929b834e12fd83f46598c
> meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>
Why are you pulling oe-core/meta and poky/meta into the same build
considering they're literally the same layer? You should either drop
oe-core/meta or poky/meta from your bblayers.
However the output showing the full remote URLs seems a sensible
improvement to me.
Ross
[-- Attachment #2: Type: text/html, Size: 1673 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 21:54 ` Burton, Ross
@ 2016-03-12 22:32 ` Trevor Woerner
2016-03-13 19:25 ` Paul Eggleton
0 siblings, 1 reply; 10+ messages in thread
From: Trevor Woerner @ 2016-03-12 22:32 UTC (permalink / raw)
To: Burton, Ross; +Cc: Patches and discussions about the oe-core layer
On 03/12/16 16:54, Burton, Ross wrote:
>
> On 12 March 2016 at 04:28, Trevor Woerner <twoerner@gmail.com
> <mailto:twoerner@gmail.com>> wrote:
>
> openembedded-core/meta =
> master:00d3fd571a8d261d065b43f5cf3076a381843984
> meta-openembedded/meta-oe =
> master:a1e135a499998add7575682bf53db5e02e753580
> meta-openembedded/meta-gnome =
> master:a1e135a499998add7575682bf53db5e02e753580
> meta-rpb =
> master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
> meta-96boards =
> master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
> meta-qcom =
> master:32fcda819acb8ec485d9ab05108d554f807bf75d
> meta-browser =
> master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
> meta-linaro/meta-linaro-toolchain =
> master:367f784b831938dc508b7d472342d2d0d6ed9769
> meta-poky/meta =
> master:37b61b059031e3c272a929b834e12fd83f46598c
> meta-poky/meta-poky =
> master:37b61b059031e3c272a929b834e12fd83f46598c
>
>
> Why are you pulling oe-core/meta and poky/meta into the same build
> considering they're literally the same layer? You should either drop
> oe-core/meta or poky/meta from your bblayers.
Ok, thanks; good point.
>
> However the output showing the full remote URLs seems a sensible
> improvement to me.
>
My hesitation is whether we want to replace the existing
buildhistory/metadata-revs with my "improvements" or whether I should
just create a second file with the updates. I don't want to break
anyone's process should they have come to rely on that file being as it is.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 2:49 [PATCH] buildhistory.bbclass: metadata-revs show repo parent Trevor Woerner
2016-03-12 3:59 ` Khem Raj
@ 2016-03-13 0:34 ` Trevor Woerner
1 sibling, 0 replies; 10+ messages in thread
From: Trevor Woerner @ 2016-03-13 0:34 UTC (permalink / raw)
To: openembedded-core
Here is how my latest incarnation looks with a "normal" build:
origin git://git.openembedded.org/openembedded-core.git (fetch)
origin git://git.openembedded.org/openembedded-core.git (push)
layer: openembedded-core/meta
branch:
contrib/twoerner/buildhistory-metatdata-revs-full-repository-remote
remote: (HEAD does not point to a remote branch)
HEAD: 9ad6e0cf8e1e7d0301ee98b55095294bd2b1c508
origin git://git.openembedded.org/meta-openembedded (fetch)
origin git://git.openembedded.org/meta-openembedded (push)
layer: meta-openembedded/meta-oe
branch: master
remote: origin/master
HEAD: a1e135a499998add7575682bf53db5e02e753580
origin git://git.openembedded.org/meta-openembedded (fetch)
origin git://git.openembedded.org/meta-openembedded (push)
layer: meta-openembedded/meta-gnome
branch: master
remote: origin/master
HEAD: a1e135a499998add7575682bf53db5e02e753580
origin git://github.com/96boards/meta-rpb.git (fetch)
origin git://github.com/96boards/meta-rpb.git (push)
layer: meta-rpb
branch: master
remote: origin/master
HEAD: 203903ca6f4e8df09bef6ea3c6e899d07eca8df9
origin https://github.com/96boards/meta-96boards.git (fetch)
origin https://github.com/96boards/meta-96boards.git (push)
layer: meta-96boards
branch: master
remote: origin/master
HEAD: 2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
origin https://github.com/ndechesne/meta-qcom.git (fetch)
origin https://github.com/ndechesne/meta-qcom.git (push)
layer: meta-qcom
branch: master
remote: origin/master
HEAD: 32fcda819acb8ec485d9ab05108d554f807bf75d
origin git://github.com/OSSystems/meta-browser.git (fetch)
origin git://github.com/OSSystems/meta-browser.git (push)
layer: meta-browser
branch: master
remote: origin/master
HEAD: a3789a4168fcd42f1cdf5b5febe2c779a9467919
origin git://git.linaro.org/openembedded/meta-linaro.git (fetch)
origin git://git.linaro.org/openembedded/meta-linaro.git (push)
layer: meta-linaro/meta-linaro-toolchain
branch: master
remote: origin/master
HEAD: 367f784b831938dc508b7d472342d2d0d6ed9769
origin git://git.yoctoproject.org/poky (fetch)
origin git://git.yoctoproject.org/poky (push)
layer: meta-poky/meta
branch: master
remote: origin/master
HEAD: 37b61b059031e3c272a929b834e12fd83f46598c
origin git://git.yoctoproject.org/poky (fetch)
origin git://git.yoctoproject.org/poky (push)
layer: meta-poky/meta-poky
branch: master
remote: origin/master
HEAD: 37b61b059031e3c272a929b834e12fd83f46598c
------------------------------------------------------------------------------
here is how it looks with a build where the repositories are managed by
the 'repo' tool:
github https://github.com/openembedded/openembedded-core (fetch)
github https://github.com/openembedded/openembedded-core (push)
layer: meta
branch: contrib/twoerner/buildhistory-patches
remote: (HEAD does not point to a remote branch)
HEAD: a77ff8f9b203fdfbd04fabc94613face86e52af5
github https://github.com/openembedded/meta-openembedded (fetch)
github https://github.com/openembedded/meta-openembedded (push)
layer: ../meta-openembedded/meta-oe
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: dc5634968b270dde250690609f0015f881db81f2
github https://github.com/openembedded/meta-openembedded (fetch)
github https://github.com/openembedded/meta-openembedded (push)
layer: ../meta-openembedded/meta-gnome
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: dc5634968b270dde250690609f0015f881db81f2
github https://github.com/96boards/meta-rpb (fetch)
github https://github.com/96boards/meta-rpb (push)
layer: ../meta-rpb
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: 203903ca6f4e8df09bef6ea3c6e899d07eca8df9
github https://github.com/96boards/meta-96boards (fetch)
github https://github.com/96boards/meta-96boards (push)
layer: ../meta-96boards
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: 2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
linaro http://git.linaro.org/openembedded/meta-linaro (fetch)
linaro http://git.linaro.org/openembedded/meta-linaro (push)
layer: ../meta-linaro/meta-linaro-toolchain
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: 395ca11e22c26bd0c26ea1078722628ba6aa2332
github https://github.com/ndechesne/meta-qcom (fetch)
github https://github.com/ndechesne/meta-qcom (push)
layer: ../meta-qcom
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: 32fcda819acb8ec485d9ab05108d554f807bf75d
github https://github.com/linaro-home/meta-browser (fetch)
github https://github.com/linaro-home/meta-browser (push)
layer: ../meta-browser
branch: HEAD
remote: (HEAD does not point to a remote branch)
HEAD: 5c00d0114c5963a178cb33f6d06181c588c03ae0
------------------------------------------------------------------------------
and here is how a different build looks when a repository has multiple
remotes:
contrib git://git.yoctoproject.org/poky-contrib.git (fetch)
contrib git://git.yoctoproject.org/poky-contrib.git (push)
origin git://git.yoctoproject.org/poky (fetch)
origin git://git.yoctoproject.org/poky (push)
layer: meta
branch: YOCTO7850
remote: contrib/YOCTO7850
HEAD: dc1410f720b6b2e8087a484b56cb7df299c31774
contrib git://git.yoctoproject.org/poky-contrib.git (fetch)
contrib git://git.yoctoproject.org/poky-contrib.git (push)
origin git://git.yoctoproject.org/poky (fetch)
origin git://git.yoctoproject.org/poky (push)
layer: meta-yocto
branch: YOCTO7850
remote: contrib/YOCTO7850
HEAD: dc1410f720b6b2e8087a484b56cb7df299c31774
contrib git://git.yoctoproject.org/poky-contrib.git (fetch)
contrib git://git.yoctoproject.org/poky-contrib.git (push)
origin git://git.yoctoproject.org/poky (fetch)
origin git://git.yoctoproject.org/poky (push)
layer: meta-yocto-bsp
branch: YOCTO7850
remote: contrib/YOCTO7850
HEAD: dc1410f720b6b2e8087a484b56cb7df299c31774
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
2016-03-12 22:32 ` Trevor Woerner
@ 2016-03-13 19:25 ` Paul Eggleton
0 siblings, 0 replies; 10+ messages in thread
From: Paul Eggleton @ 2016-03-13 19:25 UTC (permalink / raw)
To: Trevor Woerner; +Cc: openembedded-core
Hi Trevor,
On Sat, 12 Mar 2016 17:32:03 Trevor Woerner wrote:
> On 03/12/16 16:54, Burton, Ross wrote:
> > On 12 March 2016 at 04:28, Trevor Woerner <twoerner@gmail.com
> >
> > <mailto:twoerner@gmail.com>> wrote:
> > openembedded-core/meta =
> > master:00d3fd571a8d261d065b43f5cf3076a381843984
> >
> > meta-openembedded/meta-oe =
> >
> > master:a1e135a499998add7575682bf53db5e02e753580
> >
> > meta-openembedded/meta-gnome =
> >
> > master:a1e135a499998add7575682bf53db5e02e753580
> >
> > meta-rpb =
> >
> > master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
> >
> > meta-96boards =
> >
> > master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
> >
> > meta-qcom =
> >
> > master:32fcda819acb8ec485d9ab05108d554f807bf75d
> >
> > meta-browser =
> >
> > master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
> >
> > meta-linaro/meta-linaro-toolchain =
> >
> > master:367f784b831938dc508b7d472342d2d0d6ed9769
> >
> > meta-poky/meta =
> >
> > master:37b61b059031e3c272a929b834e12fd83f46598c
> >
> > meta-poky/meta-poky =
> >
> > master:37b61b059031e3c272a929b834e12fd83f46598c
> >
> > Why are you pulling oe-core/meta and poky/meta into the same build
> > considering they're literally the same layer? You should either drop
> > oe-core/meta or poky/meta from your bblayers.
>
> Ok, thanks; good point.
>
> > However the output showing the full remote URLs seems a sensible
> > improvement to me.
>
> My hesitation is whether we want to replace the existing
> buildhistory/metadata-revs with my "improvements" or whether I should
> just create a second file with the updates. I don't want to break
> anyone's process should they have come to rely on that file being as it is.
metadata-revs was intended to be consumed by scripts rather than humans, so
I'd rather not change its format unless absolutely necessary.
Besides, if you fix the problem with what you've checked out, do you need to
make the change at all?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2016-03-13 19:25 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-12 2:49 [PATCH] buildhistory.bbclass: metadata-revs show repo parent Trevor Woerner
2016-03-12 3:59 ` Khem Raj
2016-03-12 4:28 ` Trevor Woerner
2016-03-12 5:33 ` Trevor Woerner
2016-03-12 11:55 ` Khem Raj
2016-03-12 15:26 ` Trevor Woerner
2016-03-12 21:54 ` Burton, Ross
2016-03-12 22:32 ` Trevor Woerner
2016-03-13 19:25 ` Paul Eggleton
2016-03-13 0:34 ` Trevor Woerner
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.