On 2020-04-27 3:39 p.m., Alexander Kanavin wrote:
You need to first see from the failure page which configuration is
failing, for example non-gpl3 is one such.
Then you find that configuration in config.json. The below should
hopefully be self-explanatory in how you should set up the build?
|"non-gpl3" : { "NEEDREPOS" : ["poky", "meta-gplv2"], "MACHINE" :
"qemux86", "BBTARGETS" : "core-image-minimal core-image-full-cmdline",
"extravars" : [ "INCOMPATIBLE_LICENSE = '*GPLv3'", "WARN_QA_remove =
'incompatible-license'" ], "EXTRACMDS" : [
"../../yocto-autobuilder-helper/scripts/check-gplv3" ] },
|
|
|
|Alex
Hi Rahul,
Sorry for my late reply.
The commit log for v2 is very good now!
Thanks for incorporating my --pedantic suggestions. ;-)
It seems that you need a perl dependency for something (docs?
$ cd .../bzip2.git
$ grep -r "perl " *
format.pl:#!/usr/bin/perl -w
README.XML.STUFF:It uses format.pl, a perl script...
Then we need to figure out how to deal with the GPLv3 issue.
The buildbot output can be tedious to figure out. I haven't really
spent enough time plugging away at it to be proficient yet either.
Have you been able to reproduce the problems that Richard reported?
If not, and you've tried for a bit, then just say so and I'll try to
help tomorrow or early next week.
It looks like you are packaging the test code/data with the main package
not in bzip2-ptest. Have a look at:
meta/recipes-support/libpcre/libpcre_8.44.bb
for an example. There are many more.
Also, if you look at oe-core.git:
$ rgrep LICENSE_ * | grep PN
you can see many examples of sub-packages with different licenses
than the main package. One example is:
meta/recipes-support/gnutls/gnutls_3.6.13.bb
I hope that can address the buildbot problem but I haven't tried it
myself yet.
BTW, Trevor has gotten the YP autobuilder going at Wind River and
he'll be sending a few documentation updates next week or so.
That may help in case you want to reproduce the YP AB test
infrastructure. I expect that you don't _have_ to do so but
I think it would be good if more contributing organizations did
have an instance with only limited builders of the YP AB so that
we can do more testing before Richard runs our changes through
the main system. Richard has cautioned that the YP AB has lots of
builders each of which has many cores but I hope that we can at least
do some AB checking ourselves.
../Randy
|
On Mon, 27 Apr 2020 at 20:54, Rahul Kumar <rah...@mvista.com
<mailto:rah...@mvista.com>> wrote:
Hi Richard/Alexander,
I am not able to understand how I can use the below file.
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json
did you mean to say that i have to set MACRO in local.conf based on
this file.
*Thanks & Regards,*
Rahul Kumar
Software Engineer,Linux Solutions Engineering
Group,Montavista Software LLC
Email Id: rah...@mvista.com <mailto:rah...@mvista.com>
<https://plus.google.com/+CodeTwoSoftware>
On Mon, Apr 27, 2020 at 11:46 PM Richard Purdie
<richard.pur...@linuxfoundation.org
<mailto:richard.pur...@linuxfoundation.org>> wrote:
On Mon, 2020-04-27 at 18:30 +0200, Alexander Kanavin wrote:
> You need to look at configurations defined here:
>
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json
> and replicate them locally. Then you can reproduce the
failures that
> the AB gets in those configurations.
That start of the failing logs on the autobuilder also list out the
configuration options for that build.
Cheers,
Richard
--
# Randy MacLeod
# Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#137694):
https://lists.openembedded.org/g/openembedded-core/message/137694
Mute This Topic: https://lists.openembedded.org/mt/73224911/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe:
https://lists.openembedded.org/g/openembedded-core/leave/8023207/1426099254/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
