Re: [yocto] mailman not found

[akuster]

On 5/2/19 5:43 AM, Searles, Dan wrote:
>
> I got this response to my recent email:
>
>  
>
> Your message to mail...@yoctoproject.org couldn't be delivered.
>

What mailing list did you send it to originally ?

- armin
>
> mailman wasn't found at yoctoproject.org.
>
>  
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] bsp-guide: replace meta-intel with meta-xilinx as container layer

[akuster]

On 5/2/19 10:45 AM, Scott Rifenbark wrote:
> The term "Container Layer" was put in the ref-manual by me to describe
> a "meta-*" layer that had other "meta-*" layers (see
> https://www.yoctoproject.org/docs/2.7/ref-manual/ref-manual.html#term-container-layer
> and the term "Container Layer").  Maybe this was never a good term?  I
> don't know.  Nobody has said anything about that term for many releases. 
>
> The problem Robert points out needs to be fixed in the BSP manual as
> "meta-intel" is not longer qualifying by my definition.  I can fix that. 
>
> Is "Container Layer" ok as I have defined it?
in those terms above, yes its fine.

thanks for clarifying.

Armin
>
> Thanks,
> Scott
>
> On Thu, May 2, 2019 at 10:21 AM akuster  <mailto:akus...@mvista.com>> wrote:
>
>
>
> On 5/2/19 6:19 AM, Robert P. J. Day wrote:
> > As meta-intel is no longer a container layer, use meta-xilinx as
> > an example instead.
>
> I thought "meta-virtualization" was a container layer?
>
> IMHO, a BSP should only deal with getting a MACHINE booted.
>
> - armin
> >
> > Signed-off-by: Robert P. J. Day  <mailto:rpj...@crashcourse.ca>>
> >
> > ---
> >
> > diff --git a/documentation/bsp-guide/bsp.xml
> b/documentation/bsp-guide/bsp.xml
> > index 0bb0b68ab..a53ff6bce 100644
> > --- a/documentation/bsp-guide/bsp.xml
> > +++ b/documentation/bsp-guide/bsp.xml
> > @@ -146,18 +146,15 @@
> >
> >      
> >          Some layers function as a layer to hold other BSP layers.
> > -        These layers are knows as
> > +        These layers are known as
> >          " url='&YOCTO_DOCS_REF_URL;#term-container-layer'>container
> layers".
> >          An example of this type of layer is the
> > -        meta-intel layer.
> > -        This layer contains BSP layers for the Intel-core2-32
> > -        Intel Common Core
> > -        (Intel-core2-32) and the Intel-corei7-64
> > -        Intel Common Core
> > -        (Intel-corei7-64).
> > -        the meta-intel layer also contains
> > -        the common/ directory, which contains
> > -        common content across those layers.
> > +        meta-xilinx layer.
> > +        This container layer contains some basic top-level
> information,
> > +        as well as three actual Xilinx-related BSP layers,
> > +        meta-xilinx-bsp,
> > +        meta-xilinx-contrib, and
> > +        meta-xilinx-standalone.
> >      
> >
> >      
> >
>
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] meta-cge

[akuster]

Hello meta-cgl maintainers,

Any plans on branching for "warrior"?

regards,
Armin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[akuster]

On 5/3/19 11:01 AM, Volosincu, Andreea S wrote:
>
> Greetings,
>
>  
>
> Yocto Project is pleased to announce the plans for the upcoming
> Embedded Linux Conferences in NA and Europe.
>
>  
>
> Here is a snapshot of our schedule:
>
>  
>
> ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront,
> San Diego, CA
>
>        Yocto Project is a sponsor. We’ll see you on the
> show floor
>
>  
>
> ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
>
> Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
>
> Level: Intermediate – Advanced. Participants will receive beginner
> material (videos and presentations) as pre-requisites
>
> Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with
> light appetizers
>
So beer is a prerequisite for Intermediate level?

This is a conflict with Linux Security summit unless someone can
convince me to be part of the training?

- armin

>  
>
> ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
>
>   Yocto Project is a sponsor. We’ll see you on the show floor
>
>  
>
> ELCE Yocto Project Summit – Dates & Times:
>
> Thursday, October 31, 2019 - 8:00AM - 6:00PM
>
>    November 1, 2019 - 8:00 am - 6:00PM
>
> Set-up:
>
> Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
>
> Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 &
> Classroom seating for 40 (for maintainers and users)
>
> Includes:
>
> Morning Break for 2 days
>
> Buffet Lunch for 2 days
>
> Beer & Wine Reception with light appetizers for 1 day
>
> The goal for the second day of the summit is to build and bring the
> community together. We are interested to hear your opinions and ideas
> on how that day and those rooms should be used for. Please send your
> ideas to Andreea Volosincu and Philip Balister.
>
>  
>
> We will call out an Advocacy meeting in a couple of weeks to go over
> plans and vote on the ideas for the second day of the summit.
>
>  
>
> Thanks!
>
> Andreea
>
> Yocto Project Advocacy Lead
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[akuster]

On 5/6/19 8:06 AM, Joshua Watt wrote:
> On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
>>
>> Greetings,
>>
>>  
>>
>> Yocto Project is pleased to announce the plans for the upcoming
>> Embedded Linux Conferences in NA and Europe.
>>
>>  
>>
>> Here is a snapshot of our schedule:
>>
>>  
>>
>> ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront,
>> San Diego, CA
>>
>>        Yocto Project is a sponsor. We’ll see you on the
>> show floor
>>
>>  
>>
>> ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
>>
>> Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
>>
>> Level: Intermediate – Advanced. Participants will receive beginner
>> material (videos and presentations) as pre-requisites
>>
>> Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with
>> light appetizers
>>
>
> Is there any registration cost for this event, and how does one register?
For the training portion there normally has been. I am sure the details
will be provided once things are setup.

- armin
>
>>  
>>
>> ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
>>
>>   Yocto Project is a sponsor. We’ll see you on the show floor
>>
>>  
>>
>> ELCE Yocto Project Summit – Dates & Times:
>>
>> Thursday, October 31, 2019 - 8:00AM - 6:00PM
>>
>>    November 1, 2019 - 8:00 am - 6:00PM
>>
>> Set-up:
>>
>> Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
>>
>> Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 &
>> Classroom seating for 40 (for maintainers and users)
>>
>> Includes:
>>
>> Morning Break for 2 days
>>
>> Buffet Lunch for 2 days
>>
>> Beer & Wine Reception with light appetizers for 1 day
>>
>> The goal for the second day of the summit is to build and bring the
>> community together. We are interested to hear your opinions and ideas
>> on how that day and those rooms should be used for. Please send your
>> ideas to Andreea Volosincu and Philip Balister.
>>
>>  
>>
>> We will call out an Advocacy meeting in a couple of weeks to go over
>> plans and vote on the ideas for the second day of the summit.
>>
>>  
>>
>> Thanks!
>>
>> Andreea
>>
>> Yocto Project Advocacy Lead
>>
> -- 
> Joshua Watt mailto:jpewhac...@gmail.com>>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Yocto Project Status WW19'19

[akuster]

On 5/7/19 7:43 AM, Richard Purdie wrote:
>
> Current Dev Position: YP 2.8 M1
>
> Next Deadline: YP 2.8 Milestone 1 Target May ??, 2019
>
>
> SWAT Team Rotation:
>
>  *
>
> SWAT lead is currently: Anuj
>
>  *
>
> SWAT team rotation: Anuj -> Ross on May. 10, 2019
>
>  *
>
> SWAT team rotation: Ross -> Amanda on May. 17, 2019
>
>  *
>
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>
> Next Team Meetings:
>
>  *
>
> YP 2.8 Planning meeting Tuesday May 7th at 8am PDT
> (https://zoom.us/j/990892712) 
>
>  *
>
> Bug Triage meeting Thursday May 9th at 7:30am PDT
> (https://zoom.us/j/454367603)
>
>
> Key Status/Updates:
>
>  *
>
> Stephen is going to be unavailable for several weeks, please refer
> any queries to Richard
>
>  *
>
> YP 2.7 was released
>
>  *
>
> The 2.8 planning discussions are starting and there is a google
> doc summarising the discussions so far:
> 
> https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
>
> If people are planning to work on specific things in 2.8 please let us
> know so we can incorporate this into our plans. If you’re interested
> in working on anything in the document, please also let us know or
> talk with us in one of the planning meetings.
>
>  *
>
> At this point we believe we’ve made our final release for the sumo
> (2.5) series
>
Sumo is moving to community support status, wiki updated.
https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance#Stable_branch_maintainers

>  *
>
> The project is planning to adopt SPDX license headers in its
> source code where practical, bitbake has had these merged as a
> first step.
>
>  *
>
> We have a new “newcomer” bug category which are bugs suited to
> someone new to the project. These can be seen here:
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
>
>
> Planned Releases for YP 2.8:
>
>  *
>
> TBA
>
>
> Planned upcoming dot releases:
>
>  *
>
> YP 2.6.3 (Thud) is in planning
>
>  *
>
> YP 2.7.1 (Warrior) is in planning
>
>
> Tracking Metrics:
>
>  *
>
> WDD 2602 (last week
> 2593)(https://wiki.yoctoproject.org/charts/combo.html)
>
>  *
>
> Poky Patch Metrics  
>
>  o
>
> Total patches found: 1558 (last week 1565)
>
>  o
>
> Patches in the Pending State: 655 (42%) [last week 655 (42%)]
>
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features
>
>
> The Status reports are now stored on the wiki at:
> https://wiki.yoctoproject.org/wiki/Weekly_Status
>
>
> [If anyone has suggestions for other information you’d like to see on
> this weekly status update, let us know!]
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Yocto Project Status WW19'19

[akuster]

On 5/7/19 7:43 AM, Richard Purdie wrote:
>
> Current Dev Position: YP 2.8 M1
>
> Next Deadline: YP 2.8 Milestone 1 Target May ??, 2019
>
>
> SWAT Team Rotation:
>
>  *
>
> SWAT lead is currently: Anuj
>
>  *
>
> SWAT team rotation: Anuj -> Ross on May. 10, 2019
>
>  *
>
> SWAT team rotation: Ross -> Amanda on May. 17, 2019
>
>  *
>
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>
> Next Team Meetings:
>
>  *
>
> YP 2.8 Planning meeting Tuesday May 7th at 8am PDT
> (https://zoom.us/j/990892712) 
>
>  *
>
> Bug Triage meeting Thursday May 9th at 7:30am PDT
> (https://zoom.us/j/454367603)
>
>
> Key Status/Updates:
>
>  *
>
> Stephen is going to be unavailable for several weeks, please refer
> any queries to Richard
>
>  *
>
> YP 2.7 was released
>
>  *
>
> The 2.8 planning discussions are starting and there is a google
> doc summarising the discussions so far:
> 
> https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
>
> If people are planning to work on specific things in 2.8 please let us
> know so we can incorporate this into our plans. If you’re interested
> in working on anything in the document, please also let us know or
> talk with us in one of the planning meetings.
>
>  *
>
> At this point we believe we’ve made our final release for the sumo
> (2.5) series
>
>  *
>
> The project is planning to adopt SPDX license headers in its
> source code where practical, bitbake has had these merged as a
> first step.
>
>  *
>
> We have a new “newcomer” bug category which are bugs suited to
> someone new to the project. These can be seen here:
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
>
>
> Planned Releases for YP 2.8:
>
>  *
>
> TBA
>
>
> Planned upcoming dot releases:
>
>  *
>
> YP 2.6.3 (Thud) is in planning
>
>  *
>
> YP 2.7.1 (Warrior) is in planning
>
>
> Tracking Metrics:
>
>  *
>
> WDD 2602 (last week
> 2593)(https://wiki.yoctoproject.org/charts/combo.html)
>
>  *
>
> Poky Patch Metrics  
>
>  o
>
> Total patches found: 1558 (last week 1565)
>
>  o
>
> Patches in the Pending State: 655 (42%) [last week 655 (42%)]
>
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features
>

Don't we need 2.8 now ?

- armin
>
> The Status reports are now stored on the wiki at:
> https://wiki.yoctoproject.org/wiki/Weekly_Status
>
>
> [If anyone has suggestions for other information you’d like to see on
> this weekly status update, let us know!]
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[akuster]

On 5/9/19 12:55 AM, Bas Mevissen wrote:
> On 2019-05-07 20:18, Behan Webster wrote:
>
> (...)
>
>> > Yes, both for LF and YP it are off-the-shelf trainings that do not
>> require much preparation.
>
>> Speaking as a course maintainer for LF, keeping the YP course updated
>> is actually a tremendous amount of work (I'm the co-maintainer for
>> the LF YP course).
>> However, the beginner slides tend not to need more than a few hours
>> of updates every 6 months (which again is something I do).
>> Either may appear off-the-shelf, but they aren't from my perspective. ;)
>
> An additional training date would probably not require much extra I
> assume. As the training is given already a few times a year.
> But it is good to hear the training is kept up to date.
Its not the material, need or willingness of the community to help that
is at issue. Its cost.
The more members we have the more we can do. 

Regards,
Armin
>
>> Thanks,
>
>> Behan
>
> -- Bas.


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[akuster]

On 5/13/19 1:09 PM, Joshua Watt wrote:
> On Mon, May 6, 2019 at 12:43 PM Volosincu, Andreea S
>  wrote:
>> Hi Joshua,
>>
>>
>>
>> The event will be listed on the co-located events page and there will be a 
>> cost associated with it. Please check this page in a couple of days - 
>> https://events.linuxfoundation.org/events/elc-north-america-2019/program/co-located-events/
>>
>>
>>
>> You will be able to add this to your ELC registration.
> Thanks. I'm hopefully not being too annoying, but us there an ETA on
> when the registration will be open? The early registration deadline
> for the ELC is May 20th, which is basically 5 working days, and I will
> need a few days to push the paperwork though, so it's getting a little
> close for my comfort :)
Add on events can be added later or purchased on-site.  I have done in
the past so I would reg for early bird now.
>
> If it isn't going to be available soon, I do have a few questions:
> 1. Is it possible to register for the Dev Day after you have
> registered for the ELC?
> 2. Is there a rough (preferably upper limit) estimate for the cost?
Good question. This is weird year for things so I can't comment on the
new norm.

- Armin
>
>
>>
>> Thanks!
>>
>> Andreea
>>
>>
>>
>> From: Joshua Watt [mailto:jpewhac...@gmail.com]
>> Sent: Monday, May 6, 2019 8:07 AM
>> To: Volosincu, Andreea S ; 
>> yocto-advoc...@yoctoproject.org; Yocto list discussion 
>> 
>> Subject: Re: [yocto] Yocto Project Upcoming Conferences and Developer Days
>>
>>
>>
>> On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
>>
>> Greetings,
>>
>>
>>
>> Yocto Project is pleased to announce the plans for the upcoming Embedded 
>> Linux Conferences in NA and Europe.
>>
>>
>>
>> Here is a snapshot of our schedule:
>>
>>
>>
>> ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San 
>> Diego, CA
>>
>>Yocto Project is a sponsor. We’ll see you on the show 
>> floor
>>
>>
>>
>> ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
>>
>> Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
>>
>> Level: Intermediate – Advanced. Participants will receive beginner material 
>> (videos and presentations) as pre-requisites
>>
>> Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
>> appetizers
>>
>>
>>
>> Is there any registration cost for this event, and how does one register?
>>
>>
>>
>>
>>
>>
>>
>> ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
>>
>>   Yocto Project is a sponsor. We’ll see you on the show floor
>>
>>
>>
>> ELCE Yocto Project Summit – Dates & Times:
>>
>> Thursday, October 31, 2019 - 8:00AM - 6:00PM
>>
>>November 1, 2019 - 8:00 am - 6:00PM
>>
>> Set-up:
>>
>> Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
>>
>> Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & Classroom 
>> seating for 40 (for maintainers and users)
>>
>> Includes:
>>
>> Morning Break for 2 days
>>
>> Buffet Lunch for 2 days
>>
>> Beer & Wine Reception with light appetizers for 1 day
>>
>>
>>
>> The goal for the second day of the summit is to build and bring the 
>> community together. We are interested to hear your opinions and ideas on how 
>> that day and those rooms should be used for. Please send your ideas to 
>> Andreea Volosincu and Philip Balister.
>>
>>
>>
>> We will call out an Advocacy meeting in a couple of weeks to go over plans 
>> and vote on the ideas for the second day of the summit.
>>
>>
>>
>> Thanks!
>>
>> Andreea
>>
>> Yocto Project Advocacy Lead
>>
>> --
>>
>> Joshua Watt 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [patchtest-oe][PATCH] test_metadata_src_uri: new unittest detecting added patch files without modifying SRC_URI

[akuster]

On 5/27/19 6:00 PM, Changqing Li wrote:
> ping
>
> On 4/29/19 2:10 PM, Changqing Li wrote:
>> ping
>>

Does this mean you have a working knowledge of patchtest?

The one used by the project appears to be off line.  Can you help?

kind regards,
Armin
>> On 3/5/19 5:59 PM, changqing...@windriver.com wrote:
>>> From: Changqing Li 
>>>
>>> Adds new unittest detecting when a patch file is added but no
>>> corresponding
>>> change to the SRC_URI is done.
>>>
>>> This patch is from , get from
>>> commit
>>> 49201c19cfe4cadd127b112d2858d5b28db49c20, this commit is reverted by
>>> commit
>>> 6108d97f83b211f9eb245f339a412debd0ec5db4.
>>>
>>> The added test case is ok, reason of series 9949 patchtest failed is:
>>> recipe weston have REQUIRED_DISTRO_FEATURES, so parse recipe skipped,
>>> cause self.modified is none, actually .bb is mofified, so make the
>>> testcase failed.
>>>
>>> during patchtest, we don't really need DISTRO_FEATURES, so fix the
>>> problem
>>> by set REQUIRED_DISTRO_FEATURES to "" in repo patchtest, meantime,
>>> add this
>>> testcase back.
>>>
>>> [Yocto #13005]
>>>
>>> Signed-off-by: Changqing Li 
>>> ---
>>>   tests/test_metadata_src_uri.py | 25 +
>>>   1 file changed, 25 insertions(+)
>>>
>>> diff --git a/tests/test_metadata_src_uri.py
>>> b/tests/test_metadata_src_uri.py
>>> index a4c5caa..f684ced 100644
>>> --- a/tests/test_metadata_src_uri.py
>>> +++ b/tests/test_metadata_src_uri.py
>>> @@ -85,3 +85,28 @@ class SrcUri(base.Metadata):
>>>     'Amend the patch containing the
>>> software patch file removal',
>>>     data=[('Patch', f) for f in
>>> not_removed])
>>>   +    def test_src_uri_path_not_updated(self):
>>> +    new_patches = set()
>>> +    for patch in self.patchset:
>>> +    if patch.is_added_file and patch.path.endswith('.patch'):
>>> +    new_patches.add(os.path.basename(patch.path))
>>> +
>>> +    if not new_patches:
>>> +    self.skip('No new patches added, skipping test')
>>> +
>>> +    if not self.modified:
>>> +    self.fail('New patch path missing in SRC_URI',
>>> +   "Add the patch path to the recipe's SRC_URI",
>>> +   data=[('New patch(es)',
>>> '\n'.join(new_patches))])
>>> +
>>> +    for pn in self.modified:
>>> +    rd = self.tinfoil.parse_recipe(pn)
>>> +
>>> +    patchtestdata.PatchTestDataStore['%s-%s-%s' %
>>> (self.shortid(), self.metadata, pn)] = rd.getVar(self.metadata)
>>> +    test_src_uri    =
>>> patchtestdata.PatchTestDataStore['%s-%s-%s' % (self.shortid(),
>>> self.metadata, pn)].split()
>>> +    test_files    = set([os.path.basename(patch) for patch
>>> in test_src_uri if patch.startswith('file://')])
>>> +
>>> +    if not test_files.issuperset(new_patches):
>>> +    self.fail('New patch path missing in SRC_URI',
>>> +  "Add the patch path in the recipe's
>>> SRC_URI",
>>> +  data=[('New patch(es)', p) for p in
>>> new_patches.difference(test_files)])
>>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.8 M2 RC1

[akuster]

On 8/1/19 3:00 AM, richard.pur...@linuxfoundation.org wrote:
> On Thu, 2019-08-01 at 07:30 +, Yeoh, Ee Peng wrote:
>> This is the full report for 2.8 M2 RC1:  
>> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=zeus&id=d550d40646e1ca78a4b5d106e1b20831208b4c37
>>
>> === Summary 
>> No high milestone defects.  
>> Two new defects are found in this cycle, both beaglebone and
>> genericx86-64 facing shutdown hanging (BUG id:13461) and ptest failed
>> (BUG id:13465). 
>> One timeout issues observed in ptests was mdadm (BUG id: 13368).
>>
>> === Bugs 
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13461
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13465
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13368
> Thanks Ee Peng, Yi and everyone else in QA!
+1,yes,  many thanks

>
> I think we do need to fix these regressions but they're not serious
> enough to block release of M2, or require a rebuild. As such I think we
> should release this.
I am fine with releasing M2 but make them blockers for M3.

- Armin

>
> Any other feedback from anyone?
>
> Cheers,
>
> Richard
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-autobuilder2][PATCH 1/3] Bug fix: added support for ABHELPER_JSON environ.

[akuster]

On 7/30/19 11:36 AM, Thomas Goodwin wrote:
> The readme suggests exporting this variable from the
> environment to expose multiple configuration JSON files
> but the intended behavior doesn't work without adding the
> variable to extra_env.

Any chance of updating documentation on how to use this?

- armin
>
> Signed-off-by: Thomas Goodwin 
> ---
>  builders.py | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/builders.py b/builders.py
> index 5765040..3d12969 100644
> --- a/builders.py
> +++ b/builders.py
> @@ -15,7 +15,8 @@ maxsteps = 9
>  # Environment to pass into the workers, e.g. to load further local 
> configuration
>  # fragments
>  extra_env = {}
> -#extra_env = {"ABHELPER_JSON" : "config.json 
> /home/pokybuild/config-local.json"}
> +if os.environ.get('ABHELPER_JSON'):
> +extra_env['ABHELPER_JSON'] = os.environ['ABHELPER_JSON']
>  
>  @util.renderer
>  def get_sstate_release_number(props):

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] LF Community Bridge Mentorship

[akuster]

On 8/16/19 12:37 AM, Nicolas Dechesne wrote:
> hi there.
> just a reminder!
> cheers

Maybe mention this during the BoF in next week's ELC?

- armin
>
> On Tue, Jul 30, 2019 at 4:46 PM Nicolas Dechesne
>  wrote:
>> Dear all,
>>
>> The Community Bridge platform was launched earlier this year by the
>> Linux Foundation. It’s a set of services available to LF projects to
>> help them build stronger ecosystems, and foster developers
>> relationship within their respective communities. See [1] and [2]. The
>> Yocto Project has joined the Community Bridge Funding and Mentorship
>> programs.
>>
>> If you have any specific questions about these programs, please do not
>> hesitate to reach out to me.
>>
>> Today, we would like to talk more about the mentorship program. We
>> have tried several initiatives in the past about interns and
>> mentorship, and we would like to do that again using the new LF
>> platform. A mentorship program for the Yocto Project is a good
>> opportunity for our overall community to reach out to new developers,
>> improve our developers diversity. It will help increase the pool of
>> available developers with appropriate skills about the Yocto Project
>> and Open Embedded technologies and as a consequence create a more
>> sustainable ecosystem around the Yocto Project. It also offers
>> existing senior developers the chance to become mentors, and share
>> their knowledge!
>>
>> We would like to request feedback about how to best define the Yocto
>> Project Mentorship program.
>>
>> The structure of the mentorship is flexible and we can adjust as
>> needed. Our initial thought is to set 12-week project, which is what
>> the Linux Kernel Mentorship program is using, see [4]. The overall
>> process involves:
>>
>> 1. Finding / defining work items for potential mentees.
>> 2. Get appropriate funding for mentees’ stipends
>> 3. Recruit mentors within our community
>> 4. Review and select mentees’ applications
>>
>> There has already been some work on the potential work items in the
>> form of the newcomer bugs, some of which could be turned into work
>> suitable for a mentorship programme.
>>
>> === Call for ACTION ===
>>
>> * We need your help for any of the items above, and especially #1 to
>> get started. Whether you are a long time contributor to the project or
>> you recently joined our mailing list, your feedback will be greatly
>> appreciated.
>> * If you are interested to participate as a mentor, please let me know!
>> * You don’t need to be a project expert to be a mentor, you need to
>> know how the project works and be willing to help guide someone
>> through their task.
>>
>> There is no specific timeline set yet, it will most likely depend on
>> how much feedback we receive about this initiative, but most likely
>> the internships will have to be tied to the Yocto Project release
>> timeline.
>>
>> If you have any questions or any suggestions, please reach out to me!
>> cheers,
>> Nico
>>
>> [1] 
>> https://www.linuxfoundation.org/press-release/2019/03/the-linux-foundation-launches-new-communitybridge-platform-to-help-sustain-open-source-communities/
>> [2] https://communitybridge.org/
>> [3] https://people.communitybridge.org/
>> [4] https://wiki.linuxfoundation.org/lkmp

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Summit at ELCE Call for Particpation

[akuster]

On 8/19/19 3:17 AM, Philip Balister wrote:
> At the past few OopenEmbedded developer meetings, people have been
> asking for more developer and user focused events like a miniconf.
> Partly based on this feedback, there is a two day event sponsored by the
> Yocto Project that provides a chance for people to talk about the Yocto
> Project and OpenEmbedded. The CFP is a bit buried on the page and I like
> to get it more exposure, so here the direct link:
>
> https://events.linuxfoundation.org/wp-content/uploads/2019/08/Yocto-Project-Summit-2019-CFP-1.pdf

So what is the process for deciding which CFP's are selected.

I see OE was cc'd with this email but there is no mention on the link
regarding OE. What roll is OE playing in this? 

Is there a cost associated with this Summit?

- armin
>
> We'd like to see new faces talking. We know there are a lot of good
> stories out there, that will help lots of people become better users and
> developers.
>
> The link to the event is here:
>
> https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/
>
> Follow the path to the Yocto Project Summit. If you are alrady signed up
> for ELCE, you should be able to update your registration to include the
> Summit.
>
> Philip


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] U-boot recipe fails for the master branch(new sbc)

[akuster]

On 8/25/19 2:15 AM, nishant poorswani wrote:
> Hi,
>
> I'm trying to add a new board called rock-pi-s to the yocto project.
> I've succesfully done it for the rocko branch. Now I'm moving it to
> the master branch. I'm facing issues with u-boot. Here is the log for it:
>
> https://pastebin.com/NAxqsvcB
>
> It seems the libfdt from dtc-1.5.0 is incompatible with the older
> versions of u-boot. Can anyone recommend a method to fix it? Any help
> is appreciated.

You can try having your own recipe for the version you need and then use
PREFERRED_VERSION to set the version you want.

- armin
>
> Regards,
> Nishant Poorswani
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [thud][PATCH] linux-yocto/4.14: meta-yocto-bsp update to 143

[akuster]

ping.



On 10/9/19 8:09 AM, Armin Kuster wrote:
> Signed-off-by: Armin Kuster 
> ---
>  .../recipes-kernel/linux/linux-yocto_4.14.bbappend   | 20 
> ++--
>  1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend 
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
> index 426757e..5277798 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>  KMACHINE_genericx86-64 ?= "common-pc-64"
>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>  
> -SRCREV_machine_genericx86?= "5252513a39b4b3773debab1f77071d7c430ecb10"
> -SRCREV_machine_genericx86-64 ?= "5252513a39b4b3773debab1f77071d7c430ecb10"
> -SRCREV_machine_edgerouter ?= "d8fb40cd0e99325715c70aed6f361a8318097829"
> -SRCREV_machine_beaglebone-yocto ?= "c67809688bd22cb4cb909bcf1a1045e6337c3229"
> -SRCREV_machine_mpc8315e-rdb ?= "258ee8228e0a512c6dbe2a0dadcd9f030ba45964"
> +SRCREV_machine_genericx86?= "bc9d4b045fa0254d14ef3a667a200f02cb9af755"
> +SRCREV_machine_genericx86-64 ?= "bc9d4b045fa0254d14ef3a667a200f02cb9af755"
> +SRCREV_machine_edgerouter ?= "326e296f237347e965a38acb34f09e594430b0c6"
> +SRCREV_machine_beaglebone-yocto ?= "1b8c86329c9dbb10b8fcaeb2dceb75680994cd84"
> +SRCREV_machine_mpc8315e-rdb ?= "f26672ec1f164b0f2a15d629128a91093f971bdd"
>  
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>  
> -LINUX_VERSION_genericx86 = "4.14.98"
> -LINUX_VERSION_genericx86-64 = "4.14.98"
> -LINUX_VERSION_edgerouter = "4.14.98"
> -LINUX_VERSION_beaglebone-yocto = "4.14.98"
> -LINUX_VERSION_mpc8315e-rdb = "4.14.98"
> +LINUX_VERSION_genericx86 = "4.14.143"
> +LINUX_VERSION_genericx86-64 = "4.14.143"
> +LINUX_VERSION_edgerouter = "4.14.143"
> +LINUX_VERSION_beaglebone-yocto = "4.14.143"
> +LINUX_VERSION_mpc8315e-rdb = "4.14.143"

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] download.yoctoproject.org - Certificate expired

[akuster]

On 10/13/19 2:30 AM, Guilhem Saurel wrote:
> Hi,
>
> The certificate installed on https://download.yoctoproject.org expired about 4
> days ago. Is anyone else experiencing the same issue? Is a new certificate 
> going
> to be installed ?
thank you for letting us know. I believe this issue has been addressed.
Please let us know if you still having issues with the certificate.

- armin
>
> Thanks,
> Guilhem.
>



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

[akuster]

Can we get 2.6.4-rc2 in a QA queue for the next dot release?

- armin

On 10/17/19 2:17 PM, Poky Build User wrote:
> A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and 
> is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2
>
>
> Build hash information: 
>
> bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb
> meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
> meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964
> meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
> oecore: cd7cf933b3235560ec71576d8f3836dff736a39f
> poky: 51f6145f8f99a02df1dad937684f014b0172e72a
>
>
>
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
>
>
>  

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] systemd Version Going Backwards on Warrior

[akuster]

On 10/29/19 11:50 AM, Ross Burton wrote:
> On 29/10/2019 04:41, Robert Joslyn wrote:
>> On Mon, 2019-10-28 at 19:06 +, Ross Burton wrote:
>>> On 28/10/2019 16:25, robert.jos...@redrectangle.org wrote:
 I'm using buildhistory in one of my builds that creates a package
 feed, and a recent update to systemd on warrior triggered version-
 going-backwards errors:

 ERROR: systemd-conf-241+AUTOINC+511646b8ac-r0 do_packagedata: QA
 Issue: Package version for package systemd-conf-src went backwards
 which would break package feeds from (0:241+0+c1f8ff8d0d-r0 to
 0:241+0+511646b8ac-r0) [version-going-backwards]

Isn't this do to the hashes being different and the PR server can't
really tell which one is newer?



 Should PE have been updated at the same time due to the hash making
 the version number go backwards? I can send a patch if that's all
 that's missing. Or is a PR server enough to prevent this? My debug
 builds do not use a PR server, but my production builds do use a PR
 server.
>>>
>>> If you're using feeds, you need to use a PR server.  This is *exactly*
>>> what they are for.
> >
>
>> The part I wasn't sure about was if the PR server helped in the case
>> where
>> PV went backwards. I know it works when PV stays the same but the
>> package
>> was rebuilt. But if it keeps the versions going forward no matter how PV
>> changes, then I should be good. I should probably setup a separate PR
>> server on my debug builds to avoid this kind of error.
>
> If the PV actually goes backwards then the PR service isn't useful, as
> PV sorts before PR.
>
> However in this case the problem is that SRCREV should have a
> incrementing counter (the +0+ should be +1+ in the rebuild) which I
> believe comes from the PR service.  I may be wrong...
>
> Ross

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto life cycle statement

[akuster@mvista]

Hello,

Can someone point to a 'life cycle statement' for Yocto versions, one 
that discusses limited bug fixing peroid and ultimate EOL of a version. 
I am having trouble find it.


Regards,
Armin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto life cycle statement

[akuster@mvista]

On 4/16/14, 1:21 PM, Stewart, David C wrote:

Thanks Stewart.

That is what I was looking for.

regards,
Armin

I found the following comments at
https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_release_cycle_of_the_Yoc
to_Project.3F
(It does seem like we have been supplying maintenance releases for two
releases back, not just one. So maybe this wiki needs to be updated)



What is the release cycle of the Yocto Project?

Each release of the Yocto Project is subject to its own release schedule
according to the community-maintained Project Planning Guide
<https://wiki.yoctoproject.org/wiki/Planning#Yocto>. It is generally
expected that a new version of the Yocto Project will be released every
six months.

What is the overall support plan for the Yocto Project?

Security patches and critical bug fixes are supplied one release back. No
toolchain or kernel changes are allowed for these updates. Support for
longer periods of time can be supplied by commercial OSVs.



On 4/16/14, 12:43 PM, "Jeff Osier-Mixon"  wrote:


Hi Armin - let me do some research on this, just wanted to let you
know that I had seen it. I'm not sure we have a formal statement
published.

On Wed, Apr 16, 2014 at 11:49 AM, akuster@mvista 
wrote:

Hello,

Can someone point to a 'life cycle statement' for Yocto versions, one
that
discusses limited bug fixing peroid and ultimate EOL of a version. I am
having trouble find it.

Regards,
Armin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




--
Jeff Osier-Mixon @Intel
Yocto Project Community Manager http://yoctoproject.org
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux] build issue

[akuster@mvista]

Hello,

I am trying to build meta-selinux and ran into some build issues. I 
started by cloning poky and meta-selinux. I am using master on both. 
When I run "bitbake core-image-selinux", I get the following errors.


ERROR: No recipes available for:

/home/armin/work/yocto/poky/meta-selinux/recipes-core/util-linux/util-linux_2.23.2.bbappend

/home/armin/work/yocto/poky/meta-selinux/recipes-connectivity/bind/bind_9.8.1.bbappend

/home/armin/work/yocto/poky/meta-selinux/recipes-kernel/linux/linux-yocto_3.8.bbappend

/home/armin/work/yocto/poky/meta-selinux/recipes-connectivity/openssh/openssh_6.4p1.bbappend

/home/armin/work/yocto/poky/meta-selinux/recipes-extended/psmisc/psmisc_22.20.bbappend

/home/armin/work/yocto/poky/meta-selinux/recipes-extended/augeas/augeas_1.1.0.bbappend

/home/armin/work/yocto/poky/meta-selinux/recipes-graphics/mesa/mesa_9.2.2.bbappend


Is this a config issue or am I using the wrong sources?

regards,
Armin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto