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

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] 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] [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] 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] 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] 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-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] 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=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] [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] 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] [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] [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] [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] 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] [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

[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] [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='_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

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 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 
>
> ---
>
> 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
>  "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
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [sumo] [PATCH v1] systemd: fix musl compilation

[akuster]

On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let everyone know that
> sumo-next branch is currently broken with MUSL unless this patch is
> applied.

After closer look, I don't the "Upstream-Status:" nor a signoff in the
patch being added in the bb file.

Does this issue affect later branches ?

- armin

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

Re: [yocto] [sumo] [PATCH v1] systemd: fix musl compilation

[akuster]

On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let everyone know that
> sumo-next branch is currently broken with MUSL unless this patch is
> applied.

Thanks for the reminder. it will be in my next merge series.

- armin

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

Re: [yocto] Building on non-x86 hosts, wic and syslinux

[akuster]

On 4/8/19 4:43 AM, Anders Montonen wrote:
> Hi,
>
> I was experimenting with building on an AArch64 host, and ran into the issue 
> that image_types_wic.bbclass unconditionally adds syslinux-native to the 
> dependencies, while syslinux is only compatible with x86 hosts. I didn’t look 
> further into this, but is it possible to make this dependency chain dependent 
> on the actual image types you’re trying to build?
I think we are going to have to figure that out. The Yocto Project has
an arm64 builder that they are in the middle of bring up. If might be
helpful to the project if you could open a bug on this. I know there are
a few folks building on raspberrypi who my be on the different mailing
list,  openembedded-c...@lists.openembedded.org. You might want to post
your question there too.

kind regards,
Armin
>
> After working around the problem by manually removing the dependency from the 
> class, the build completed without issues (though I did not test the results).
>
> Regards,
> Anders


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

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

[akuster]

On 4/5/19 6:28 AM, Tim Orling wrote:
> Just curious: all Perl modules in oe-core have ptest enabled, but only
> libxml-parser-perl is included in these test reports. Is it simply the
> only module in that image or is something else afoot?

Is this what you are looking for ?


pango              | 12          | 0        | 0        | -
perl               | 2282        | 3        | 120      | -
python             | 8331        | 45       | 69       | -

>
> On Thu, Apr 4, 2019 at 3:29 PM  > wrote:
>
> On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote:
> >
> > On 4/5/19 3:25 AM, richard.pur...@linuxfoundation.org
>  wrote:
> > > On Thu, 2019-04-04 at 02:19 +, Jain, Sangeeta wrote:
> > > > Also, I don't see any ptest results for 2.6.2.rc3 on public
> > > > autobuilder. Do you have any plans to run them and share the
> > > > results
> > > > on autobuilder?
> > > These were run separately but will run as part of any new stable
> > > release builds. The results are here:
> > >
> > >
> 
> https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
> > >
> 
> https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/
> > >
> > > (for 2.6.2 and 2.5.4)
> > >
> > > I'll merge these into the main release output in due course.
> > Did I miss something in order to create:
> >
> 
> https://autobuilder.yocto.io/pub/non-release/20190326-8/testresults/testresult-report.txt
>
> Right now only a-quick or a-full builds get those.
>
> You can get one with:
>
> $ wget
> 
> https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/testresults.json
> $ resulttool report .
>
> which gives:
>
> 
> ==
> PTest Result Summary
> 
> ==
> 
> --
> Recipe             | Passed      | Failed   | Skipped  | Time(s)   
> 
> --
> acl                | 221         | 0        | 0        | -
> attr               | 109         | 0        | 0        | -
> bash               | 75          | 4        | 0        | -
> bluez5             | 25          | 0        | 0        | -
> busybox            | 528         | 15       | 45       | -
> bzip2              | 6           | 0        | 0        | -
> dbus-test          | 18          | 3        | 2        | -
> diffstat           | 439         | 0        | 0        | -
> diffutils          | 20          | 0        | 0        | -
> e2fsprogs          | 315         | 6        | 27       | -
> flex               | 114         | 0        | 0        | -
> gawk               | 342         | 0        | 0        | -
> gdbm               | 24          | 0        | 0        | -
> gdk-pixbuf         | 20          | 0        | 0        | -
> glib-2.0           | 259         | 3        | 0        | -
> gstreamer1.0       | 101         | 3        | 0        | -
> gzip               | 21          | 0        | 0        | -
> libpcre            | 3           | 0        | 0        | -
> libusb1            | 4           | 0        | 0        | -
> libxml-parser-perl | 15          | 0        | 0        | -
> libxml2            | 134         | 0        | 0        | -
> lttng-tools        | 1087        | 0        | 0        | - T
> lzo                | 39          | 6        | 0        | -
> nettle             | 158         | 0        | 2        | -
> openssh            | 832         | 72       | 367      | - T
> openssl            | 0           | 0        | 0        | -
> pango              | 12          | 0        | 0        | -
> perl               | 2298        | 1        | 120      | -
> python             | 5444        | 15       | 53       | -
> python3            | 7466        | 0        | 198      | -
> quilt              | 57          | 0        | 0        | -
> sed                | 86          | 0        | 0        | -
> slang              | 97          | 0        | 0        | -
> strace             | 213         | 272      | 97       | - T
> tcl                | 148         | 0        | 0        | -
> util-linux         | 0           | 395      | 55       | -
> 
> --
>
> and
>
> $ wget
> 
> 

Re: [yocto] [meta-security][PATCH 4/5] sssd: update to 1.16.4

[akuster]

On 3/29/19 12:10 AM, Adrian Bunk wrote:
> On Thu, Mar 28, 2019 at 10:28:20PM -0700, Armin Kuster wrote:
>> Add systemd pkgconf via DISTRO_FEATURE
>>
>> Fix uid/gid of sssd.conf
>>
>> Signed-off-by: Armin Kuster 
>> ...
>> -RDEPENDS_${PN} = "bind dbus samba libldb"
>> +RDEPENDS_${PN} = "bind dbus samba libldb libpam"
> Why is this required?
>
> And the way this commit mixes unrelated changes, it is no even clear 
> whether this is for the new upstream version or supposed to fix some 
> older issue.
I will be squish those extra changes into the clean up patch and just
have the update separate.
thanks,
Armin
> cu
> Adrian
>

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

Re: [yocto] [meta-security][PATCH 2/5] libldb: work around samba libldb packaging issues

[akuster]

On 3/28/19 11:50 PM, Adrian Bunk wrote:
> On Thu, Mar 28, 2019 at 10:28:18PM -0700, Armin Kuster wrote:
>> Samba and libldb overlap in a few places. This is the simplest fix for
>> now.
> Adding a quick hack for interaction problems between two packages
> that are both in meta-openembedded by adding a .bbappend in 
> meta-security creates a technical debt while not even helping
> users who are not using meta-security.
>
> The proper solution is likely to make samba use the external libldb 
> instead of an internal copy.
>
>> Signed-off-by: Armin Kuster 
>> ---
>>  recipes-support/libldb/libldb_%.bbappend | 22 ++
>>  1 file changed, 22 insertions(+)
>>  create mode 100644 recipes-support/libldb/libldb_%.bbappend
>>
>> diff --git a/recipes-support/libldb/libldb_%.bbappend 
>> b/recipes-support/libldb/libldb_%.bbappend
>> new file mode 100644
>> index 000..2633a1e
>> --- /dev/null
>> +++ b/recipes-support/libldb/libldb_%.bbappend
>> @@ -0,0 +1,22 @@
>> +# This fixes this issue:
>> +#ERROR: sssd-1.16.3-r0 do_prepare_recipe_sysroot: The file 
>> /usr/lib/python2.7/site-packages/_ldb_text.py is installed by both libldb 
>> and samba, aborting
>> +
>> +EXTRA_OECONF += "--disable-python"
>> ...
> So just adding the meta-security layer will turn the pyldb* packages 
> into empty packages?
 I think I have a possible solution in libldb. patch out shortly.

- armin
>
> cu
> Adrian
>

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

Re: [yocto] [meta-security][PATCH 3/5] sssd: fix a few runtime issues

[akuster]

On 3/28/19 11:51 PM, Adrian Bunk wrote:
> On Thu, Mar 28, 2019 at 10:28:19PM -0700, Armin Kuster wrote:
>> include a few more RDEPEND packages. remove init script as there really
>> isn't one yet.
>>
>> Signed-off-by: Armin Kuster 
>> ---
>>  recipes-security/sssd/sssd_1.16.3.bb | 14 --
>>  1 file changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/recipes-security/sssd/sssd_1.16.3.bb 
>> b/recipes-security/sssd/sssd_1.16.3.bb
>> index 8f7f805..e3fb254 100644
>> --- a/recipes-security/sssd/sssd_1.16.3.bb
>> +++ b/recipes-security/sssd/sssd_1.16.3.bb
>> ...
>>  # The package contains symlinks that trip up insane
>>  INSANE_SKIP_${PN} = "dev-so"
>>  
>> -RDEPENDS_${PN} += "bind dbus"
>> +RDEPENDS_${PN} = "bind dbus samba libldb"
> Even when samba support is not enabled?
Yeah, that isn't right.
thanks,
Armin
>
> cu
> Adrian
>

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

Re: [yocto] SDK build fails at latest thud

[akuster]

On 3/13/19 9:50 PM, Teemu K wrote:
> Hi,
>
> I noticed that when trying to build sdk on thud it fails on latest
> version. Actually it broke somewhere between commits:
>
> 1cab405d88149fd63322a867c6adb4a80ba68db3 (old)
> 7c76c5d78b850a9c1adccf8b11ed0164da608f1c (new)
>
> I'm using it with meta-freescale - layer to build image to iMX8.
>
> I'm using command 'populate_sdk' and it works fine on older version,
> but newer version it fails with error:
Can you provide the steps to reproduce?
>
> ==
> The following packages have unmet dependencies:
>  target-sdk-provides-dummy : Conflicts: coreutils
> E: Unable to correct problems, you have held broken packages.

There is a change sitting in stable/thud-next:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stable/thud-next=af5cf78b275ab5226354337d25d8dc1c41a08904

which might be related. Can you try that branch?

git://git.yoctoproject.org/poky-contrib  stable/thud-next

- armin
> ==
>
> I'm assuming this is problem in poky - layer and not meta-freescale
> since it can be 'fixed' by downgrading to older version of thud.
>
> -Teemu

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

Re: [yocto] Yocto Project Status WW09'19

[akuster]

On 2/26/19 7:58 AM, sjolley.yp...@gmail.com wrote:
>
> Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)
>
> Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019
>
>  
>
> SWAT Team Rotation:
>
>   * SWAT lead is currently: Ross
>   * SWAT team rotation: Ross -> Chen on Mar. 1, 2019
>   * SWAT team rotation: Chen -> Armin on Mar. 8, 2019
>
I am going to be at LS on Monday March 10th and traveling on March 13. 
If this may be an issue, maybe rescheduling for a different week may be
in order.
I personal don't this there will be an issue.

>  *
>
>
>   * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>  
>
> Key Status/Updates:
>
>   * We have now passed the feature freeze point for 2.7
>   * YP 2.7 M2 rc2 is out of QA and being readied for release.  See:
> 
> https://wiki.yoctoproject.org/wiki/WW07_-_2019-02-14_-_Full_Test_Cycle_2.7_M2_RC2
> and
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status#Milestone_2_-_Target_Feb._1.2C_2019
>   * We now have resulttool, buildhistory and build-performance all
> working with the autobuilder and will be using this as the primary
> QA mechanism going forward. More details can be found here:
>
> http://lists.openembedded.org/pipermail/openembedded-architecture/2019-February/001591.html
>
>   * There were some serious usability issues found with multiconfig,
> those have been fixed in master and thud.
>   * Various recipe upgrades made it in, thanks to all who contributed.
> Several recipes also converted to meson including glib-2.0 and
> gdk-pixbuf.
>   * We now need to build M3 as we’re past feature freeze point for
> 2.7. Right now we’re aware of the following things which ideally
> need to be resolved first:
>   o Bug 13178 “X server and matchbox desktop don't start up
> properly on beaglebone” needs to be fixed
>
a patch was sent and  is in master.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4860914b3b5b38926ed6a80bb83a011d341ff2d8


- armin
>
>  o
>   o Find the framebuffer problem with qemuarmv7 and switch to that
>   o Several ptest issues would be addressed (missing openssl
> tests, 3 timeouts)
>   o Arm build host issues identified and resolved
>   * It’s unlikely we’ll switch to virtgl by default for 2.7 due to
> lack of testing from the community although the base patches for
> this have merged.
>
>  
>
> Planned Releases for YP 2.7:
>
>   * YP 2.7 M2 rc2 is out of QA.
>   * YP 2.7 M2 Release Target was Feb. 1, 2019
>   * YP 2.7 M3 Cutoff is Feb. 25, 2019
>   * YP 2.7 M3 Release Target is Mar. 8, 2019
>   * YP 2.7 M4 Cutoff is Apr. 1, 2019
>   * YP 2.7 M4 Release Target is Apr. 26, 2019
>
>  
>
> Planned upcoming dot releases:
>
>   * YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
>   * YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
>   * YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.
>
>  
>
> Tracking Metrics:
>
>   * WDD 2415 (last week
> 2392)(https://wiki.yoctoproject.org/charts/combo.html)
>   * Poky Patch Metrics  
>   o Total patches found: 1516 (last week 1527)
>   o Patches in the Pending State: 660 (44%) [last week 663 (43%)]
>
>  
>
> 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!]
>
>  
>
> Thanks,
>
>  
>
> */Stephen K. Jolley/**//*
>
> *Yocto Project Program Manager*
>
> (    *Cell*:    (208) 244-4460
>
> * *Email*:  _sjolley.yp...@gmail.com
> _
>
>  
>
>

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

Re: [yocto] [meta-security][PATCH] xmlsec1: Include libxmlsec1-*.so in the main package

[akuster]

series merged.

On 1/30/19 1:57 AM, Adrian Bunk wrote:
> They can be dynamically loaded with xmlSecCryptoDLLoadLibrary().
>
> Signed-off-by: Adrian Bunk 
> ---
>  recipes-security/xmlsec1/xmlsec1_1.2.26.bb | 5 +
>  1 file changed, 5 insertions(+)
>
> diff --git a/recipes-security/xmlsec1/xmlsec1_1.2.26.bb 
> b/recipes-security/xmlsec1/xmlsec1_1.2.26.bb
> index 2dbbf33..aca9634 100644
> --- a/recipes-security/xmlsec1/xmlsec1_1.2.26.bb
> +++ b/recipes-security/xmlsec1/xmlsec1_1.2.26.bb
> @@ -32,6 +32,11 @@ EXTRA_OECONF = "\
>  --with-nss=${STAGING_LIBDIR}/../.. --with-nspr=${STAGING_LIBDIR}/../.. \
>  "
>  
> +# these can be dynamically loaded with xmlSecCryptoDLLoadLibrary()
> +FILES_SOLIBSDEV = "${libdir}/libxmlsec1.so"
> +FILES_${PN} += "${libdir}/libxmlsec1-*.so"
> +INSANE_SKIP_${PN} = "dev-so"
> +
>  FILES_${PN}-dev += "${libdir}/xmlsec1Conf.sh"
>  FILES_${PN}-dbg += "${PTEST_PATH}/.debug/*"
>  

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

Re: [yocto] [meta-security][PATCHv2] Upgrade scapy to 2.4.2

[akuster]

series merged

On 1/19/19 3:16 AM, Scott Ellis wrote:
> Upstream MANIFEST.in removed doc and test directories
> so remove ptest.
>
> Signed-off-by: Scott Ellis 
> ---
>  recipes-security/scapy/files/run-ptest|  4 
>  recipes-security/scapy/python-scapy.inc   | 11 +++
>  recipes-security/scapy/python-scapy_2.4.0.bb  |  6 --
>  recipes-security/scapy/python-scapy_2.4.2.bb  |  4 
>  recipes-security/scapy/python3-scapy_2.4.0.bb |  4 
>  recipes-security/scapy/python3-scapy_2.4.2.bb |  2 ++
>  6 files changed, 9 insertions(+), 22 deletions(-)
>  delete mode 100755 recipes-security/scapy/files/run-ptest
>  delete mode 100644 recipes-security/scapy/python-scapy_2.4.0.bb
>  create mode 100644 recipes-security/scapy/python-scapy_2.4.2.bb
>  delete mode 100644 recipes-security/scapy/python3-scapy_2.4.0.bb
>  create mode 100644 recipes-security/scapy/python3-scapy_2.4.2.bb
>
> diff --git a/recipes-security/scapy/files/run-ptest 
> b/recipes-security/scapy/files/run-ptest
> deleted file mode 100755
> index 91b29f9..000
> --- a/recipes-security/scapy/files/run-ptest
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -#!/bin/sh
> -UTscapy -t regression.uts -f text -l -C \
> --o @PTEST_PATH@/scapy_ptest_$(date +%Y%m%d-%H%M%S).log \
> -2>&1 | sed -e 's/^passed None/PASS:/' -e 's/^failed None/FAIL:/'
> diff --git a/recipes-security/scapy/python-scapy.inc 
> b/recipes-security/scapy/python-scapy.inc
> index 5abe7db..95e5312 100644
> --- a/recipes-security/scapy/python-scapy.inc
> +++ b/recipes-security/scapy/python-scapy.inc
> @@ -5,15 +5,10 @@ LICENSE = "GPLv2"
>  
>  LIC_FILES_CHKSUM = 
> "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
>  
> -SRC_URI[md5sum] = "d7d3c4294f5a718e234775d38dbeb7ec"
> -SRC_URI[sha256sum] = 
> "452f714f5c2eac6fd0a6146b1dbddfc24dd5f4103f3ed76227995a488cfb2b73"
> +SRC_URI[md5sum] = "e6a03d8c924a6bbde1e86fc58bd2b9d6"
> +SRC_URI[sha256sum] = 
> "1baa048936207ceb1a4281a0e1e3b4317667c754872a0bb4734c5213c468e86a"
>  
> -inherit pypi ptest
> -
> -do_install_ptest() {
> -install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
> -sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
> -}
> +inherit pypi
>  
>  RDEPENDS_${PN} = "tcpdump ${PYTHON_PN}-compression ${PYTHON_PN}-netclient  \
>${PYTHON_PN}-netserver ${PYTHON_PN}-pydoc 
> ${PYTHON_PN}-pkgutil ${PYTHON_PN}-shell \
> diff --git a/recipes-security/scapy/python-scapy_2.4.0.bb 
> b/recipes-security/scapy/python-scapy_2.4.0.bb
> deleted file mode 100644
> index 98db1fd..000
> --- a/recipes-security/scapy/python-scapy_2.4.0.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -inherit setuptools
> -require python-scapy.inc
> -
> -SRC_URI += "file://run-ptest"
> -
> -RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
> diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb 
> b/recipes-security/scapy/python-scapy_2.4.2.bb
> new file mode 100644
> index 000..ea8764a
> --- /dev/null
> +++ b/recipes-security/scapy/python-scapy_2.4.2.bb
> @@ -0,0 +1,4 @@
> +inherit setuptools
> +require python-scapy.inc
> +
> +RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
> diff --git a/recipes-security/scapy/python3-scapy_2.4.0.bb 
> b/recipes-security/scapy/python3-scapy_2.4.0.bb
> deleted file mode 100644
> index 93ca7be..000
> --- a/recipes-security/scapy/python3-scapy_2.4.0.bb
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -inherit setuptools3
> -require python-scapy.inc
> -
> -SRC_URI += "file://run-ptest"
> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
> b/recipes-security/scapy/python3-scapy_2.4.2.bb
> new file mode 100644
> index 000..34eb2a3
> --- /dev/null
> +++ b/recipes-security/scapy/python3-scapy_2.4.2.bb
> @@ -0,0 +1,2 @@
> +inherit setuptools3
> +require python-scapy.inc

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

Re: [yocto] [meta-security][PATCH] checksec: Remove old script

[akuster]

merged

On 1/24/19 11:56 PM, Scott Ellis wrote:
> Should have been removed in previous patch.
>
> Signed-off-by: Scott Ellis 
> ---
>  recipes-security/checksec/files/checksec.sh | 882 
> 
>  1 file changed, 882 deletions(-)
>  delete mode 100644 recipes-security/checksec/files/checksec.sh
>
> diff --git a/recipes-security/checksec/files/checksec.sh 
> b/recipes-security/checksec/files/checksec.sh
> deleted file mode 100644
> index dd1f72e..000
> --- a/recipes-security/checksec/files/checksec.sh
> +++ /dev/null
> @@ -1,882 +0,0 @@
> -#!/bin/bash
> -#
> -# The BSD License (http://www.opensource.org/licenses/bsd-license.php) 
> -# specifies the terms and conditions of use for checksec.sh:
> -#
> -# Copyright (c) 2009-2011, Tobias Klein.
> -# All rights reserved.
> -#
> -# Redistribution and use in source and binary forms, with or without 
> -# modification, are permitted provided that the following conditions 
> -# are met:
> -# 
> -# * Redistributions of source code must retain the above copyright 
> -#   notice, this list of conditions and the following disclaimer.
> -# * Redistributions in binary form must reproduce the above copyright 
> -#   notice, this list of conditions and the following disclaimer in 
> -#   the documentation and/or other materials provided with the 
> -#   distribution.
> -# * Neither the name of Tobias Klein nor the name of trapkit.de may be 
> -#   used to endorse or promote products derived from this software 
> -#   without specific prior written permission.
> -#
> -# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
> -# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
> -# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 
> -# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 
> -# COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
> -# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
> -# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS 
> -# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 
> -# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, 
> -# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF 
> -# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH 
> -# DAMAGE.
> -#
> -# Name: checksec.sh
> -# Version : 1.5
> -# Author  : Tobias Klein
> -# Date: November 2011
> -# Download: http://www.trapkit.de/tools/checksec.html
> -# Changes : http://www.trapkit.de/tools/checksec_changes.txt
> -#
> -# Description:
> -#
> -# Modern Linux distributions offer some mitigation techniques to make it 
> -# harder to exploit software vulnerabilities reliably. Mitigations such 
> -# as RELRO, NoExecute (NX), Stack Canaries, Address Space Layout 
> -# Randomization (ASLR) and Position Independent Executables (PIE) have 
> -# made reliably exploiting any vulnerabilities that do exist far more 
> -# challenging. The checksec.sh script is designed to test what *standard* 
> -# Linux OS and PaX (http://pax.grsecurity.net/) security features are being 
> -# used.
> -#
> -# As of version 1.3 the script also lists the status of various Linux kernel 
> -# protection mechanisms.
> -#
> -# Credits:
> -#
> -# Thanks to Brad Spengler (grsecurity.net) for the PaX support.
> -# Thanks to Jon Oberheide (jon.oberheide.org) for the kernel support.
> -# Thanks to Ollie Whitehouse (Research In Motion) for rpath/runpath support.
> -# 
> -# Others that contributed to checksec.sh (in no particular order):
> -#
> -# Simon Ruderich, Denis Scherbakov, Stefan Kuttler, Radoslaw Madej,
> -# Anthony G. Basile, Martin Vaeth and Brian Davis. 
> -#
> -
> -# global vars
> -have_readelf=1
> -verbose=false
> -
> -# FORTIFY_SOURCE vars
> -FS_end=_chk
> -FS_cnt_total=0
> -FS_cnt_checked=0
> -FS_cnt_unchecked=0
> -FS_chk_func_libc=0
> -FS_functions=0
> -FS_libc=0
> - 
> -# version information
> -version() {
> -  echo "checksec v1.5, Tobias Klein, www.trapkit.de, November 2011"
> -  echo 
> -}
> -
> -# help
> -help() {
> -  echo "Usage: checksec [OPTION]"
> -  echo
> -  echo "Options:"
> -  echo
> -  echo "  --file "
> -  echo "  --dir  [-v]"
> -  echo "  --proc "
> -  echo "  --proc-all"
> -  echo "  --proc-libs "
> -  echo "  --kernel"
> -  echo "  --fortify-file "
> -  echo "  --fortify-proc "
> -  echo "  --version"
> -  echo "  --help"
> -  echo
> -  echo "For more information, see:"
> -  echo "  http://www.trapkit.de/tools/checksec.html;
> -  echo
> -}
> -
> -# check if command exists
> -command_exists () {
> -  type $1  > /dev/null 2>&1;
> -}
> -
> -# check if directory exists
> -dir_exists () {
> -  if [ -d $1 ] ; then
> -return 0
> -  else
> -return 1
> -  fi
> -}
> -
> -# check user privileges
> -root_privs () {
> -  if [ $(/usr/bin/id -u) -eq 0 ] ; then
> -return 0
> -  else
> -return 1
> -  fi
> -}
> -
> -# check if input is numeric
> -isNumeric () {
> -  

Re: [yocto] [PATCH 00/10] Misc fixes (cover letter only)

[akuster]

Hello Paul.

On 2/6/19 2:00 PM, Paul Eggleton wrote:
> The following changes since commit 61e9b048591adab88d1996646286e1d7df024bea:
>
>   Fix drop-down alignment on duplicates page (2018-11-20 11:58:42 +1300)
>
> are available in the Git repository at:
>
>   git://git.yoctoproject.org/layerindex-web paule/fixes12
>   http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes12
>
> Paul Eggleton (10):
>   Send people an email when another user adds them as a maintainer
>   Add links to other branch recipes in recipe detail
>   Fix errors due to races deleting bitbake temp files
>   local.conf: allow for upstream_tracking.inc to be missing
>   Use try...finally or with to ensure files get closed
>   Replace use of assert with exceptions
>   docker: add wget to dependencies
>   RRS: fix sorting arrow positioning
>   rrs_maintainer_history: check out layer branch before looking for
> maintainers.inc
>   RRS: add tool to import/export upstream history data

Thanks for the updates and fixes. This is  a very useful tool to both YP
and OE. 

I had to look at what was actual changes to figure out what this patch
set was against.  Should we change the "subject" to help clarify? ie
[layer-index][PATCH ...?

The layer index is hosted on OE. Should one of the  OE mailing be CC'ed??

Yes I realize the sources are hosted on YP but the url for the tool is
http://layers.openembedded.org. can be confusing.

kind regards,
Armin
>
>  Dockerfile |   1 +
>  conf/local.conf|   2 +-
>  layerindex/bulkchange.py   |  18 +-
>  layerindex/update.py   |   4 +-
>  layerindex/update_layer.py |  14 +-
>  layerindex/utils.py|  21 ++-
>  layerindex/views.py|  70 ++--
>  rrs/tools/historytool.py   | 196 +
>  rrs/tools/rrs_distros.py   |  19 +-
>  rrs/tools/rrs_maintainer_history.py|  45 ++---
>  rrs/tools/rrs_upgrade_history.py   |   4 +-
>  rrs/tools/rrs_upstream_history.py  |   3 +-
>  rrs/tools/upgrade_history_internal.py  |   3 +-
>  rrs/views.py   |   2 +
>  templates/layerindex/maintemail.txt|   9 +
>  templates/layerindex/maintemailsubject.txt |   1 +
>  templates/layerindex/recipedetail.html |  27 +++
>  templates/rrs/maintainers.html |   2 +-
>  templates/rrs/recipedetail.html|  27 +++
>  templates/rrs/recipes.html |   2 +-
>  20 files changed, 392 insertions(+), 78 deletions(-)
>  create mode 100755 rrs/tools/historytool.py
>  create mode 100644 templates/layerindex/maintemail.txt
>  create mode 100644 templates/layerindex/maintemailsubject.txt
>


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

Re: [yocto] [meta-security][PATCHv2] Upgrade scapy to 2.4.2

[akuster]

Scott,


On 1/19/19 3:16 AM, Scott Ellis wrote:
> Upstream MANIFEST.in removed doc and test directories
> so remove ptest.
>
> Signed-off-by: Scott Ellis 
> ---
>  recipes-security/scapy/files/run-ptest|  4 
>  recipes-security/scapy/python-scapy.inc   | 11 +++
>  recipes-security/scapy/python-scapy_2.4.0.bb  |  6 --
>  recipes-security/scapy/python-scapy_2.4.2.bb  |  4 
>  recipes-security/scapy/python3-scapy_2.4.0.bb |  4 
>  recipes-security/scapy/python3-scapy_2.4.2.bb |  2 ++
>  6 files changed, 9 insertions(+), 22 deletions(-)
>  delete mode 100755 recipes-security/scapy/files/run-ptest
>  delete mode 100644 recipes-security/scapy/python-scapy_2.4.0.bb
>  create mode 100644 recipes-security/scapy/python-scapy_2.4.2.bb
>  delete mode 100644 recipes-security/scapy/python3-scapy_2.4.0.bb
>  create mode 100644 recipes-security/scapy/python3-scapy_2.4.2.bb

Thank you for the update. The issue I have is the doc's and test got
removed from the pypi package via commit:
https://github.com/secdev/scapy/commit/8857c03bad798ba902b34c64282ef72483569c77
when they went to 2.4.2.


Any ideas on how to restore the ptests?  I know 2.4.1 still has the
tests. I wonder how may folks run this ptest?

I am holding this update for now.

- armin

>
> diff --git a/recipes-security/scapy/files/run-ptest 
> b/recipes-security/scapy/files/run-ptest
> deleted file mode 100755
> index 91b29f9..000
> --- a/recipes-security/scapy/files/run-ptest
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -#!/bin/sh
> -UTscapy -t regression.uts -f text -l -C \
> --o @PTEST_PATH@/scapy_ptest_$(date +%Y%m%d-%H%M%S).log \
> -2>&1 | sed -e 's/^passed None/PASS:/' -e 's/^failed None/FAIL:/'
> diff --git a/recipes-security/scapy/python-scapy.inc 
> b/recipes-security/scapy/python-scapy.inc
> index 5abe7db..95e5312 100644
> --- a/recipes-security/scapy/python-scapy.inc
> +++ b/recipes-security/scapy/python-scapy.inc
> @@ -5,15 +5,10 @@ LICENSE = "GPLv2"
>  
>  LIC_FILES_CHKSUM = 
> "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
>  
> -SRC_URI[md5sum] = "d7d3c4294f5a718e234775d38dbeb7ec"
> -SRC_URI[sha256sum] = 
> "452f714f5c2eac6fd0a6146b1dbddfc24dd5f4103f3ed76227995a488cfb2b73"
> +SRC_URI[md5sum] = "e6a03d8c924a6bbde1e86fc58bd2b9d6"
> +SRC_URI[sha256sum] = 
> "1baa048936207ceb1a4281a0e1e3b4317667c754872a0bb4734c5213c468e86a"
>  
> -inherit pypi ptest
> -
> -do_install_ptest() {
> -install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
> -sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
> -}
> +inherit pypi
>  
>  RDEPENDS_${PN} = "tcpdump ${PYTHON_PN}-compression ${PYTHON_PN}-netclient  \
>${PYTHON_PN}-netserver ${PYTHON_PN}-pydoc 
> ${PYTHON_PN}-pkgutil ${PYTHON_PN}-shell \
> diff --git a/recipes-security/scapy/python-scapy_2.4.0.bb 
> b/recipes-security/scapy/python-scapy_2.4.0.bb
> deleted file mode 100644
> index 98db1fd..000
> --- a/recipes-security/scapy/python-scapy_2.4.0.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -inherit setuptools
> -require python-scapy.inc
> -
> -SRC_URI += "file://run-ptest"
> -
> -RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
> diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb 
> b/recipes-security/scapy/python-scapy_2.4.2.bb
> new file mode 100644
> index 000..ea8764a
> --- /dev/null
> +++ b/recipes-security/scapy/python-scapy_2.4.2.bb
> @@ -0,0 +1,4 @@
> +inherit setuptools
> +require python-scapy.inc
> +
> +RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
> diff --git a/recipes-security/scapy/python3-scapy_2.4.0.bb 
> b/recipes-security/scapy/python3-scapy_2.4.0.bb
> deleted file mode 100644
> index 93ca7be..000
> --- a/recipes-security/scapy/python3-scapy_2.4.0.bb
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -inherit setuptools3
> -require python-scapy.inc
> -
> -SRC_URI += "file://run-ptest"
> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
> b/recipes-security/scapy/python3-scapy_2.4.2.bb
> new file mode 100644
> index 000..34eb2a3
> --- /dev/null
> +++ b/recipes-security/scapy/python3-scapy_2.4.2.bb
> @@ -0,0 +1,2 @@
> +inherit setuptools3
> +require python-scapy.inc


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

Re: [yocto] [meta-security][PATCH 01/11] README: add git-config tips

[akuster]

On 1/14/19 6:41 AM, Ross Burton wrote:
> Signed-off-by: Ross Burton 
> ---
>  README | 7 +++
>  1 file changed, 7 insertions(+)

series merged.

thanks
>
> diff --git a/README b/README
> index e238271..c15fea9 100644
> --- a/README
> +++ b/README
> @@ -57,6 +57,13 @@ Send pull requests, patches, comments or questions to 
> yocto@yoctoproject.org
>  When sending single patches, please using something like:
>  'git send-email -1 --to yocto@yoctoproject.org 
> --subject-prefix=meta-security][PATCH'
>  
> +These values can be set as defaults for this repository:
> +
> +$ git config sendemail.to yocto@yoctoproject.org
> +$ git config format.subjectPrefix meta-security][PATCH
> +
> +Now you can just do 'git send-email origin/master' to send all local patches.
> +
>  Maintainers:Armin Kuster 
>  Saul Wold 
>  

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

Re: [yocto] [meta-security][PATCH] Upgrade scapy to 2.4.2

[akuster]

On 1/12/19 1:45 PM, Scott Ellis wrote:
> Signed-off-by: Scott Ellis 
> ---
>  recipes-security/scapy/python-scapy.inc   | 4 ++--
>  .../scapy/{python-scapy_2.4.0.bb => python-scapy_2.4.2.bb}| 0
>  .../scapy/{python3-scapy_2.4.0.bb => python3-scapy_2.4.2.bb}  | 0
>  3 files changed, 2 insertions(+), 2 deletions(-)
>  rename recipes-security/scapy/{python-scapy_2.4.0.bb => 
> python-scapy_2.4.2.bb} (100%)
>  rename recipes-security/scapy/{python3-scapy_2.4.0.bb => 
> python3-scapy_2.4.2.bb} (100%)
>
> diff --git a/recipes-security/scapy/python-scapy.inc 
> b/recipes-security/scapy/python-scapy.inc
> index 5abe7db..d5a70fe 100644
> --- a/recipes-security/scapy/python-scapy.inc
> +++ b/recipes-security/scapy/python-scapy.inc
> @@ -5,8 +5,8 @@ LICENSE = "GPLv2"
>  
>  LIC_FILES_CHKSUM = 
> "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
>  
> -SRC_URI[md5sum] = "d7d3c4294f5a718e234775d38dbeb7ec"
> -SRC_URI[sha256sum] = 
> "452f714f5c2eac6fd0a6146b1dbddfc24dd5f4103f3ed76227995a488cfb2b73"
> +SRC_URI[md5sum] = "e6a03d8c924a6bbde1e86fc58bd2b9d6"
> +SRC_URI[sha256sum] = 
> "1baa048936207ceb1a4281a0e1e3b4317667c754872a0bb4734c5213c468e86a"

When i build this with "ptest" enabled I get this failure.
| grep: Makefile: No such file or directory
| install: cannot stat
'/home/akuster/oss/maint/openembedded-core/build/tmp-glibc/work/aarch64-oe-linux/python3-scapy/2.4.2-r0/scapy-2.4.2/test/regression.uts':
No such file or directory

regression.uts no longer exists.

- armin

>  
>  inherit pypi ptest
>  
> diff --git a/recipes-security/scapy/python-scapy_2.4.0.bb 
> b/recipes-security/scapy/python-scapy_2.4.2.bb
> similarity index 100%
> rename from recipes-security/scapy/python-scapy_2.4.0.bb
> rename to recipes-security/scapy/python-scapy_2.4.2.bb
> diff --git a/recipes-security/scapy/python3-scapy_2.4.0.bb 
> b/recipes-security/scapy/python3-scapy_2.4.2.bb
> similarity index 100%
> rename from recipes-security/scapy/python3-scapy_2.4.0.bb
> rename to recipes-security/scapy/python3-scapy_2.4.2.bb

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

Re: [yocto] [meta-security][PATCH] checksec: Upgrade to 1.11.0

[akuster]

On 1/3/19 9:02 AM, Scott Ellis wrote:
> Switch source to a more up to date github repo.
Very cool.
>
> Signed-off-by: Scott Ellis 
> ---
>  recipes-security/checksec/checksec_1.11.bb | 19 +++
>  1 file changed, 19 insertions(+)
>  create mode 100644 recipes-security/checksec/checksec_1.11.bb
It appears that the removed nor the delta of the current version are not
present.

- armin
>
> diff --git a/recipes-security/checksec/checksec_1.11.bb 
> b/recipes-security/checksec/checksec_1.11.bb
> new file mode 100644
> index 000..59a67bd
> --- /dev/null
> +++ b/recipes-security/checksec/checksec_1.11.bb
> @@ -0,0 +1,19 @@
> +SUMMARY = "Linux system security checks"
> +DESCRIPTION = "The checksec script is designed to test what standard Linux 
> OS and PaX security features are being used."
> +SECTION = "security"
> +LICENSE = "BSD"
> +HOMEPAGE="https://github.com/slimm609/checksec.sh;
> +
> +LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=93fddcca19f6c897871f9b5f9a035f4a"
> +
> +SRCREV = "a57e03c4f62dbaca0ec949bbc58491fb0c461447"
> +SRC_URI = "git://github.com/slimm609/checksec.sh"
> +
> +S = "${WORKDIR}/git"
> +
> +do_install() {
> +install -d ${D}${bindir}
> +install -m 0755 ${S}/checksec ${D}${bindir}
> +}
> +
> +RDEPENDS_${PN} = "bash openssl-bin"


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

Re: [yocto] [meta-security][thud][PATCH] tpm2.0-tss: Remove resourcemgr sub-package

[akuster]

On 12/7/18 2:38 AM, Daniel Dragomir wrote:
> Since in 2.0.x branch resourcemgr was removed as deprecated by
> commit 7966ef8916f79ed09eab966a58d773f413fbb67f ("Remove resourcemgr
> and fixup build.") and commit 0e175d36c13b1801d75ae768ac520154585326f8
> ("contrib: Remove systemd service and udev rules for old resourcemgr."),
> remove resourcemgr sub-package with it's components.
merged.

> Build will fail when trying sed command on resourcemgr.service
> (No such file or directory).
>
> Signed-off-by: Daniel Dragomir 
> ---
>  meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_2.0.1.bb | 19 ---
>  1 file changed, 19 deletions(-)
>
> diff --git a/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_2.0.1.bb 
> b/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_2.0.1.bb
> index 3e7b81a..9d1ff72 100644
> --- a/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_2.0.1.bb
> +++ b/meta-tpm/recipes-tpm/tpm2.0-tss/tpm2.0-tss_2.0.1.bb
> @@ -24,22 +24,6 @@ EXTRA_USERS_PARAMS = "\
>   groupadd tss; \
>   "
>  
> -SYSTEMD_PACKAGES = "resourcemgr"
> -SYSTEMD_SERVICE_resourcemgr = "resourcemgr.service"
> -SYSTEMD_AUTO_ENABLE_resourcemgr = "enable"
> -
> -do_patch[postfuncs] += 
> "${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','fix_systemd_unit','',
>  d)}"
> -fix_systemd_unit () {
> -sed -i -e 
> 's;^ExecStart=.*/resourcemgr;ExecStart=${sbindir}/resourcemgr;' 
> ${S}/contrib/resourcemgr.service
> -}
> -
> -do_install_append() {
> -if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; 
> then
> -install -d ${D}${systemd_system_unitdir}
> -install -m0644 ${S}/contrib/resourcemgr.service 
> ${D}${systemd_system_unitdir}/resourcemgr.service
> -fi
> -}
> -
>  PROVIDES = "${PACKAGES}"
>  PACKAGES = " \
>  ${PN} \
> @@ -57,7 +41,6 @@ PACKAGES = " \
>  libtss2 \
>  libtss2-dev \
>  libtss2-staticdev \
> -resourcemgr \
>  "
>  
>  FILES_libtss2-tcti-device = "${libdir}/libtss2-tcti-device.so.*"
> @@ -89,5 +72,3 @@ FILES_libtss2-dev = " \
>  FILES_libtss2-staticdev = "${libdir}/libtss*a"
>  
>  FILES_${PN} = "${libdir}/udev"
> -
> -FILES_resourcemgr = "${sbindir}/resourcemgr 
> ${systemd_system_unitdir}/resourcemgr.service"

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

Re: [yocto] [PATCH][meta-qt4] sip: re-add 4.19

[akuster]

On 11/30/18 7:34 AM, Andreas Müller wrote:
> * Haven't tested this but it seems unlikely that python-pyqt builds properly
>   with '--sip-module PyQt5.sip' in meta-oe's sip

Why not fix the version in meta-oe?

- armin
> * I plan to move reworked sip to meta-qt5 and remove meta-oe's version
> * remove FILES_${PN} - not necessary
> * add "STRIP="" for native configure to avoid 'already stripped' warning
> * tested build of python-pyqt
>
> Signed-off-by: Andreas Müller 
> ---
>  recipes-qt4/recipes-python/sip_4.19.bb | 41 
> ++
>  1 file changed, 41 insertions(+)
>  create mode 100644 recipes-qt4/recipes-python/sip_4.19.bb
>
> diff --git a/recipes-qt4/recipes-python/sip_4.19.bb 
> b/recipes-qt4/recipes-python/sip_4.19.bb
> new file mode 100644
> index 000..b43c2d2
> --- /dev/null
> +++ b/recipes-qt4/recipes-python/sip_4.19.bb
> @@ -0,0 +1,41 @@
> +SUMMARY = "SIP is a C++/Python Wrapper Generator"
> +HOMEPAGE = "http://www.riverbankcomputing.co.uk/sip;
> +SECTION = "devel"
> +LICENSE = "GPLv2+"
> +LIC_FILES_CHKSUM = "file://LICENSE-GPL2;md5=e91355d8a6f8bd8f7c699d62863c7303"
> +
> +inherit python-dir
> +
> +DEPENDS = "python"
> +
> +SRC_URI = "${SOURCEFORGE_MIRROR}/project/pyqt/sip/sip-${PV}/sip-${PV}.tar.gz"
> +SRC_URI[md5sum] = "be51a05065c9323b98a2ec2966c64e6a"
> +SRC_URI[sha256sum] = 
> "014bf55f653e0d8bcc582705ef4fbd61e0859a36e959ab46d8fa060cdf0b5e27"
> +
> +BBCLASSEXTEND = "native"
> +
> +PACKAGES += "python-sip"
> +
> +do_configure_prepend_class-target() {
> +echo "py_platform = linux" > sip.cfg
> +echo "py_inc_dir = 
> %(sysroot)/${includedir}/python%(py_major).%(py_minor)" >> sip.cfg
> +echo "sip_bin_dir = ${D}/${bindir}" >> sip.cfg
> +echo "sip_inc_dir = ${D}/${includedir}" >> sip.cfg
> +echo "sip_module_dir = 
> ${D}/${libdir}/python%(py_major).%(py_minor)/site-packages" >> sip.cfg
> +echo "sip_sip_dir = ${D}/${datadir}/sip" >> sip.cfg
> +python configure.py --configuration sip.cfg --sysroot 
> ${STAGING_DIR_HOST} CC="${CC}" CXX="${CXX}" LINK="${CXX}" STRIP="" 
> LINK_SHLIB="${CXX}" CFLAGS="${CFLAGS}" CXXFLAGS="${CXXFLAGS}" 
> LFLAGS="${LDFLAGS}"
> +}
> +do_configure_prepend_class-native() {
> +echo "py_platform = linux" > sip.cfg
> +echo "py_inc_dir = ${includedir}/python%(py_major).%(py_minor)" >> 
> sip.cfg
> +echo "sip_bin_dir = ${D}/${bindir}" >> sip.cfg
> +echo "sip_inc_dir = ${D}/${includedir}" >> sip.cfg
> +echo "sip_module_dir = 
> ${D}/${libdir}/python%(py_major).%(py_minor)/site-packages" >> sip.cfg
> +echo "sip_sip_dir = ${D}/${datadir}/sip" >> sip.cfg
> +python configure.py --configuration sip.cfg --sysroot 
> ${STAGING_DIR_NATIVE} STRIP=""
> +}
> +do_install() {
> +oe_runmake install
> +}
> +
> +FILES_python-sip = "${libdir}/${PYTHON_DIR}/site-packages/"

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

Re: [yocto] Autobuilder changes

[akuster]

On 11/23/18 10:02 AM, Richard Purdie wrote:
> I've take this quiet period as an opportunity to make some significant
> autobuilder changes:
>
> The targets have all been renamed and split up. "nightly-arm" became 
> "qemuarm" and "beaglebone". The "nightly-" prefixes were dropped.
>
> The nightly target was dropped and replaced by "a-quick" and "a-full".
> The difference are a number of targets which don't often find problems.
> We're also ramping down on the amount of testing qemumips-lsb/qemuppc-
> lsb get for example as they're more minor architectures as things
> stand. The "a-" prefix is for sorting in the UI and to separate them
> out from the mass of other builds.
>
> There are now selftest targets per "distro" which can replace the
> testing that Intel QA have been doing. This is only done for "a-full"
> and the selftest on a distro at random is done by "a-quick".
>
> Buildhistory is only being generated for the qemu* targets.
>
> The "template" used for testing qemu or "real-hardware" targets was
> standardised as there were weird differences for now good reason.
>
> The structure of "non-release" builds on 
> https://autobuilder.yocto.io/pub/ was cleaned up and now appears under
> a single date+number under the non-release directory which was how it
> was meant to work. All the other spurious output that was there has
> been cleaned up.
>
> XML test results are now being published for all builds, e.g.:
> https://autobuilder.yocto.io/pub/non-release/20181122-11/qemuarm64/
>
> Ptest was added to "a-full" builds for arm and x86 although the arm
> builds currently time out. The plan will be to enable arm when we have
> an arm build server with KVM support in our rack (next week?). ptest
> execution for x86 takes around 3 hours and some sample result output
> is:
>
> https://autobuilder.yocto.io/pub/non-release/20181122-11/qemux86-64-ptest/
>
> "meta-oe" and "meta-virt" test targets were added for experimentation,
> testing meta-openembedded and meta-virtualization respectively. These
> are work in progress currently just doing a "world -k" build for
> qemux86-64 which fails (they take around 2.5 hours).
>
> We now run "a-quick" on master at 1am every day which will make
What Time zone for 1am?
> buildhistory more up to date and useful for the master branch and give
> us better comparison data for -next and mut.
>
> wine is installed onto the ubuntu1804 workers and the mingw testing was
> split into a meta-mingw target, now with 32 and 64 bit build tests and
> 64 bit runtime tests. With master-next of meta-mingw this appears to
> run the test. Huge kudos to Joshua Watt for putting that testing
> together. If we install more onto the workers we could probably test 32
> bit as well, I'm torn on that right now as its a lot more dependencies
> on the workers.
>
> Building older releases is now broken until I sort out the
> corresponding helper changes for those branches but one thing at a
> time!

Does that include Thud ? I expect sumo and below to be problems.

Do the changes need to roll from newest to oldest  or are they
independent? I was hoping to get Sumo tested using the original QA
process to buy us time to get the automation working on it. Does this
changes that ?

- armin

>
> If anyone would like to help with xml results file analysis tooling,
> that is where we need work next to be able to summarise the ptest
> results and do results comparison. I know Ee Peng has some work in this
> area which I will be looking at next.
>
> Cheers,
>
> Richard
>
>
>


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

Re: [yocto] [yocto-docs][thud][v2][PATCH] ref-system-requirements: sync with thud poky.conf

[akuster]

On 11/19/18 2:44 AM, Bas Mevissen wrote:
> On 2018-11-19 04:08, Armin Kuster wrote:
>> poky.conf
>>     ubuntu-16.04
>>     ubuntu-16.10
>>     ubuntu-17.04
>>     fedora-26
>
> Support for Fedora 26 has ended. I've been using Fedora 27 and 28 for
> Sumo and they are fine for me. I can do some tests on Thud. However, I
> cannot do the full 2TB tests that are suggested at
> https://wiki.yoctoproject.org/wiki/Distribution_Support and
> https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan
Thanks for the info. I believe the Test plan has been superseded by the
builders bring up in the AutoBuilder. The version in master has been
updated so you make want to take a look.

I am aligning the Docs with what is identified in the Thud released
sources. The becomes our stake in the ground. As time goes on we test on
newer host OS and update accordingly.

Thanks
- armin
>
> -- Bas.
>
>>     centos-7
>>     debian-8
>>     debian-9
>>     opensuse-42.1
>>     opensuse-42.2
>>
>> Signed-off-by: Armin Kuster 
>>
>> -- 
>> [v2]
>> Drop LTS for ubuntu-16.10
>> ---
>>  documentation/ref-manual/ref-system-requirements.xml | 20
>> 
>>  1 file changed, 12 insertions(+), 8 deletions(-)
>>
>> diff --git a/documentation/ref-manual/ref-system-requirements.xml
>> b/documentation/ref-manual/ref-system-requirements.xml
>> index 9298e84..6795a69 100644
>> --- a/documentation/ref-manual/ref-system-requirements.xml
>> +++ b/documentation/ref-manual/ref-system-requirements.xml
>> @@ -93,19 +93,22 @@
>>  Ubuntu 11.10
>>  Ubuntu 12.04 (LTS)
>>  Ubuntu 13.10
>> -    Ubuntu 14.04 (LTS)
>> -->
>> +    Ubuntu 14.04 (LTS)
>>  Ubuntu 14.10
>>  Ubuntu 15.04
>> -    Ubuntu 15.10
>> +    Ubuntu 15.10 -->
>>  Ubuntu 16.04 (LTS)
>> +    Ubuntu 16.10 
>> +    Ubuntu 17.04 
>>  
>> +    Fedora release 20
>> (Heisenbug)
>>  Fedora release 22
>>  Fedora release 23
>> -
>> +    Fedora release 26
>> +
>> -
>> -    openSUSE 13.2
>> +    openSUSE 13.1
>> +    openSUSE 13.2 -->
>>  openSUSE 42.1
>> +    openSUSE 42.2
>>  
>>  
>>
>> -- 
>> 2.7.4
>

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

Re: [yocto] [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool

[akuster]

On 11/7/18 10:33 AM, Michael Halstead wrote:
> We add workers to the nightly-bringup pool to test them in a production like
> enviroment. Include one completely emulated target and one to test
> virtualization extentions.


Would this be a good indicator to add a new host to the sanity checker
or start that process?


- armin

>
> Signed-off-by: Michael Halstead 
> ---
>  config.json | 13 +
>  1 file changed, 13 insertions(+)
>
> diff --git a/config.json b/config.json
> index f912abf..2945155 100644
> --- a/config.json
> +++ b/config.json
> @@ -145,6 +145,19 @@
>  "SANITYTARGETS" : "core-image-minimal:do_testsdkext"
>  }
>  },
> +   "nightly-bringup" : {
> +"MACHINE" : "qemuarm",
> +"TEMPLATE" : "nightly-arch",
> +"step2" : {
> +"MACHINE" : "beaglebone-yocto",
> +"BBTARGETS" : "core-image-sato core-image-sato-dev 
> core-image-sato-sdk core-image-minimal core-image-minimal-dev 
> core-image-sato-sdk-ptest core-image-sato:do_populate_sdk"
> +},
> +"step5" : {
> +"MACHINE" : "qemux86-64",
> +"SDKMACHINE" : "x86_64",
> +"BBTARGETS" : "core-image-minimal:do_populate_sdk_ext 
> core-image-sato:do_populate_sdk"
> +}
> +},
>  "nightly-mips" : {
>  "MACHINE" : "qemumips",
>  "TEMPLATE" : "nightly-arch",
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][sumo][PATCH 0/7] Refpolicy updates for sumo

[akuster]

On 10/29/18 11:31 AM, Joe MacDonald wrote:
> I'm sending this out  as a follow-up to our discussion from last week.
> This set will be placed on the newly-created 'sumo' branch.  I plan to
> follow up with a slightly different version for a new 'thud' branch as
> well, at which point things should be stable enough on those two
> branches that I can finish up the refpolicy update (2.20180701) I'd
> started a little while ago.  After that, I think top of my list is to
> clean up some (I think unintended) behaviour in the _git recipe variants.
>
> Comments / suggestions / etc. more than welcome.


so this is not based on Master?

- armin

>
> -- 
> Joe MacDonald
> :wq
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][sumo][PATCH 1/7] layer.conf: update LAYERSERIES_COMPAT `sumo' -> `thud'

[akuster]

On 10/29/18 11:32 AM, Joe MacDonald wrote:
> From: Hongxu Jia 
>
> Since `9ec5a8a layer.conf: Drop sumo from LAYERSERIES_CORENAMES' and
> `9867924 layer.conf: Add thud to LAYERSERIES_CORENAMES' applied in oe-core,
> update LAYERSERIES_COMPAT `sumo' -> `thud'

the subject branch and change confuse me. Shouldn't his be for "Thud"?

- armin

>
> Signed-off-by: Hongxu Jia 
> Signed-off-by: Joe MacDonald 
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 0f9ea41..5fecac6 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -18,7 +18,7 @@ BBFILE_PRIORITY_selinux = "5"
>  # cause compatibility issues with other layers
>  LAYERVERSION_selinux = "1"
>  
> -LAYERSERIES_COMPAT_selinux = "sumo"
> +LAYERSERIES_COMPAT_selinux = "thud"
>  
>  LAYERDEPENDS_selinux = " \
>  core \
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] meta-oracle-java still maintained?

[akuster]

On 10/17/18 8:55 AM, Mark Hatle wrote:
> On 10/17/18 9:33 AM, Joshua Watt wrote:
>> I was wondering if meta-oracle-java is still maintained? It looks like
>> there haven't been any release branches created since pyro.
>>
>> We are looking at using it to provide virtual/java-native for some
>> build host tools we have that were written in Java, but I want to make
>> sure that it isn't going to die off on us if we do.
> I believe this was abandoned when Oracle changed their licensing.
>
> The 'meta-java' layer however is still being updated and provides an 
> alternative
> to the Oracle Java.

Maybe that layer should be moved to the "Yocto Metadata Layer Archive"
area then.

- armin

> --Mark
>
>> Thanks,
>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [RFC] CVEs on sumo branch

[akuster]

On 09/21/2018 02:07 PM, Sinan Kaya wrote:
> On 9/21/2018 4:35 PM, akuster808 wrote:
>> I already have in my sumo-next
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=stable/sumo-next
>>
>> libcroco: patch for CVE-2017-7960
>> 
>>
>>
>> libarchive: CVE-2017-14501
>> 
>>
>>
>> For the rest can you sent them to the proper mailing list
>> openembedded-c...@lists.openembedded.org  via git send-patch.
>
> Actually, I took this from open-embedded master branch.
>
> https://github.com/openembedded/openembedded-core/commit/b9b254da08c1db94ac9ded5f67d7e2e82e3b9be7
>
>
> commit b9b254da08c1db94ac9ded5f67d7e2e82e3b9be7
> Author: Zheng Ruoqin 
> Date:   Tue Jun 26 13:44:17 2018 +0800
>
>     glibc: fix CVE-2018-11237
>
>     glibc: fix CVE-2018-11237
>
>     Signed-off-by: Zheng Ruoqin 
>     Signed-off-by: Richard Purdie 
>
> What does it take to move this in the right direction?
bring it to my attention like you have.

backported it for the next build round.

Thanks,
Armin
>
> I'll take care of the remaining 3.

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

Re: [yocto] Demos for the Yocto Project booth at ELCE in Edinburgh

[akuster]

On 09/18/2018 06:29 AM, Nicolas Dechesne wrote:
> Dear all,
>
> As usual, the Yocto Project will have a booth at the ELCE conference
> in Edinburgh next month. While the booth is a great opportunity for
> everyone to get a new sticker of your favorite project ;-) we are also
> very excited when developers from our community get a chance to show
> off the fun and cool things they build thanks to the Yocto Project!
>
> If you want to bring any of your cool demo on the YP booth, please
> send me an email so that we can plan and discuss any of the logistics!

I will be bringing a demo.. Not sure it its cool though :)

- armin
>
> Also, don't forget the YP Dev Day Europe, which is right after ELCE,
> in Edinburgh, more information can be found here:
> https://www.yoctoproject.org/yocto-project-dev-day-europe-2018/
>
> cheers
> nico

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

Re: [yocto] [meta-security][PATCH] ecryptfs-utils: fix usrmerge install path

[akuster]

On 08/27/2018 10:45 PM, mingli...@windriver.com wrote:
> From: Mingli Yu 
>
> Update rootsbindir from /sbin to ${base_sbindir}
> to fix below do_install error when usrmerge
> enabled in DISTRO_FEATURES
> | chmod: cannot access 
> '/poky-build/tmp-glibc/work/core2-64-wrs-linux/ecryptfs-utils/111-r0/image/usr/sbin/mount.ecryptfs_private':
>  No such file or directory
>
> And pass "--with-pamdir=${base_libdir}/security"
> to configure script to fix below warning when
> usrmerge enabled in DISTRO_FEATURES
> | WARNING: ecryptfs-utils-111-r0 do_package: QA Issue: ecryptfs-utils: 
> Files/directories were installed but not shipped in any package:
>   /lib64/security/pam_ecryptfs.so
merged
> Signed-off-by: Mingli Yu 
> ---
>  recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb | 9 +++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb 
> b/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
> index f55b0c3..1f780f9 100644
> --- a/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
> +++ b/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
> @@ -29,6 +29,7 @@ EXTRA_OECONF = "\
>  --libdir=${base_libdir} \
>  --disable-pywrap \
>  --disable-nls \
> +--with-pamdir=${base_libdir}/security \
>  "
>  
>  PACKAGECONFIG ??= "nss \
> @@ -43,12 +44,16 @@ do_configure_prepend() {
>  export NSS_LIBS="-L${STAGING_BASELIBDIR} -lssl3 -lsmime3 -lnss3 
> -lsoftokn3 -lnssutil3"
>  export KEYUTILS_CFLAGS="-I${STAGING_INCDIR}"
>  export KEYUTILS_LIBS="-L${STAGING_LIBDIR} -lkeyutils"
> +sed -i -e "s;rootsbindir=\"/sbin\";rootsbindir=\"\${base_sbindir}\";g" 
> ${S}/configure.ac
>  }
>  
>  do_install_append() {
>  chmod 4755 ${D}${base_sbindir}/mount.ecryptfs_private
> -mkdir -p ${D}/${libdir}
> -mv ${D}/${base_libdir}/pkgconfig ${D}/${libdir}
> +# ${base_libdir} is identical to ${libdir} when usrmerge enabled
> +if ! 
> ${@bb.utils.contains('DISTRO_FEATURES','usrmerge','true','false',d)}; then
> +mkdir -p ${D}/${libdir}
> +mv ${D}/${base_libdir}/pkgconfig ${D}/${libdir}
> +fi
>  sed -i -e 's:-I${STAGING_INCDIR}::' \
> -e 's:-L${STAGING_LIBDIR}::' 
> ${D}/${libdir}/pkgconfig/libecryptfs.pc
>  sed -i -e "s: ${base_sbindir}/cryptsetup: ${sbindir}/cryptsetup:" 
> ${D}${bindir}/ecryptfs-setup-swap

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

Re: [yocto] yocto dev day 2018 eurpoe

[akuster]

On 07/20/2018 07:09 PM, Trevor Woerner wrote:
> Has a date/location been set?

I believe it has. An announcement is being formulated and will be sent
to the mailing lists and posted on the Yocto web site. Give it a little
time as new people are getting use to the process.

kind regards,
Armin

>
> (Is it too presumptuous of me to assume there will be a Yocto Dev Day
> in Scotland this year?)
>
>

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

Re: [yocto] [meta-security][PATCH 0/2] Fix build issue for apparmor

[akuster]

series merged.

Thanks,

Armin


On 06/06/2018 07:06 AM, Jinliang Li wrote:
> This patch series fix 2 build issues for apparmor.
>
> Jinliang Li (2):
>   Fix build issue for apparmor kernel configuration
>   Fix build issue for apparmor when systemd is used
>
>  recipes-kernel/linux/linux-yocto_4.%.bbappend | 2 +-
>  recipes-security/AppArmor/apparmor_2.11.0.bb  | 5 +
>  2 files changed, 6 insertions(+), 1 deletion(-)
>

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

Re: [yocto] [meta-selinux][PATCH] policycoreutils: remove oe_filter_out

[akuster]

On 04/14/2018 03:33 PM, Armin Kuster wrote:
> bb.data_smart.ExpansionError: Failure expanding variable WARN_QA[:=], 
> expression was ${@oe_filter_out('unsafe-references-in-scripts', 'ldflags 
> useless-rpaths rpaths staticdev libdir xorg-driver-abi textrel 
> already-stripped incompatible-license files-invalid 
> installed-vs-shipped compile-host-path install-host-path 
> pn-overrides infodir build-deps unknown-configure-option 
> symlink-to-sysroot multilib invalid-packageconfig 
> host-user-contaminated uppercase-pn ', d)} which triggered 
> exception NameError: name 'oe_filter_out' is not defined
>
> Signed-off-by: Armin Kuster 

ping
> ---
>  recipes-security/selinux/policycoreutils.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-security/selinux/policycoreutils.inc 
> b/recipes-security/selinux/policycoreutils.inc
> index 442b086..1842fd8 100644
> --- a/recipes-security/selinux/policycoreutils.inc
> +++ b/recipes-security/selinux/policycoreutils.inc
> @@ -64,8 +64,8 @@ RDEPENDS_${BPN}-setsebool += "\
>  "
>  RDEPENDS_${BPN} += "selinux-python"
>  
> -WARN_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${WARN_QA}', 
> d)}"
> -ERROR_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${ERROR_QA}', 
> d)}"
> +WARN_QA_remove = " unsafe-references-in-scripts"
> +ERROR_QA_remove = " unsafe-references-in-scripts"
>  
>  
>  PACKAGES =+ "\

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

Re: [yocto] [meta-qt4][v2][PATCH 2/2] layers: move LAYERSERIES_COMPAT to sumo

[akuster]

On 04/13/2018 03:39 PM, Armin Kuster wrote:
> [v2]
> Fix cut error
>
> Signed-off-by: Armin Kuster 
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 1ce54af..915d89c 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -8,4 +8,4 @@ BBFILE_COLLECTIONS += "qt4-layer"
>  BBFILE_PATTERN_qt4-layer = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_qt4-layer = "6"
>  
> -LAYERSERIES_COMPAT_qt4-layer = "rocko"
> +LAYERSERIES_COMPAT_qt4-layer = "sumo"
Ping for the series

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

Re: [yocto] [meta-qt3][v2][PATCH 1/2] layer: add LAYERSERIES_COMPAT

[akuster]

On 04/13/2018 03:47 PM, Armin Kuster wrote:
> [v2]
> Fix type in name
>
> Signed-off-by: Armin Kuster 
> ---
>  conf/layer.conf | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 84ab5f7..0197197 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -8,3 +8,4 @@ BBFILE_COLLECTIONS += "qt3"
>  BBFILE_PATTERN_qt3 = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_qt3 = "6"
>  
> +LAYERSERIES_COMPAT_qt3 = "rocko"
Ping

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

Re: [yocto] [meta-qt3][v2][PATCH 2/2] layer: Change LAYERSERIES_COMPAT to sumo

[akuster]

On 04/13/2018 03:47 PM, Armin Kuster wrote:
> [v2]
> fix typo in layer name
>
> Signed-off-by: Armin Kuster 
Ping
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 0197197..cfcad24 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -8,4 +8,4 @@ BBFILE_COLLECTIONS += "qt3"
>  BBFILE_PATTERN_qt3 = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_qt3 = "6"
>  
> -LAYERSERIES_COMPAT_qt3 = "rocko"
> +LAYERSERIES_COMPAT_qt3 = "sumo"

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

Re: [yocto] [meta-cgl][PATCH 0/5][RFC] CGL cleanup

[akuster]

On 04/18/2018 05:42 AM, Adrian Dudau wrote:
> On mån, 2018-04-16 at 08:03 -0700, Armin Kuster wrote:
>> I understand some of these changes a harsh. This set of changes allow
>> this layer to pass the
>> yocto-check-layer. This is one of many options to address passing.
>>
> Hi Armin,
>
> Thanks for doing this. The series is good, and I merged it with some
> minor changes, see below.
>
> I also fixed the LAYERSERIES_COMPAT issue in meta-cgl-common so you
> won't have to resend that series.
great thanks.

- Armin
>
> Regards,
> --Adrian
>
>
>
>> Armin Kuster (5):
>>   meta-cgl-fsl-ppc: drop layer supporting old kernel
> This patch didn't apply without your patches from the
> LAYERSERIES_COMPAT series which wasn't correct. I was going to drop the
> layer anyways, so I did it in a separate commit to simplify things.
>
>>   Corosync: remove recipe its in meta-networking.
>>   makedumpfile: remove as its in meta-oe
>>   iscsi-initiator-utils: drop bbappends
>>   meta-cge-common: Add README
> Fixed typo in subject.
>
>>  meta-cgl-common/README | 138
>> ++
>>  .../corosync/build-cleanup-configure-ac.patch  |  57 
>>  .../corosync/corosync/corosync-docs.patch  |  37 -
>>  .../corosync/corosync/corosync-notifyd.service |  13 --
>>  .../recipes-cgl/corosync/corosync/corosync.init| 160 -
>> 
>>  .../recipes-cgl/corosync/corosync/corosync.service |  26 
>>  .../corosync/corosync/fix-define-semun-union.patch |  20 ---
>>  .../corosync/corosync/groff-desc-path.patch|  12 --
>>  .../recipes-cgl/corosync/corosync/notifyd.init | 120 -
>> ---
>>  .../recipes-cgl/corosync/corosync/volatiles|   1 -
>>  .../recipes-cgl/corosync/corosync_1.4.8.bb |  88 -
>> ---
>>  .../files/alias-powerpc-powerpc32.patch|  18 ---
>>  .../recipes-cgl/makedumpfile/makedumpfile_1.5.8.bb |  20 ---
>>  .../iscsi-initiator-utils_%.bbappend   |   1 -
>>  meta-cgl-fsl-ppc/conf/layer.conf   |  14 --
>>  ...p-inherit-auth-capable-on-INIT-collisions.patch |  41 --
>>  ...erpc-Fix-64-bit-builds-with-binutils-2.24.patch |  80 ---
>>  .../linux/linux-qoriq-cgl-prt_3.12.bb  |  36 -
>>  18 files changed, 138 insertions(+), 744 deletions(-)
>>  create mode 100644 meta-cgl-common/README
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/build-cleanup-configure-ac.patch
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/corosync-docs.patch
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/corosync-notifyd.service
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/corosync.init
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/corosync.service
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/fix-define-semun-union.patch
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/groff-desc-path.patch
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/notifyd.init
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync/volatiles
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/corosync/corosync_1.4.8.bb
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/makedumpfile/files/alias-powerpc-powerpc32.patch
>>  delete mode 100644 meta-cgl-common/recipes-
>> cgl/makedumpfile/makedumpfile_1.5.8.bb
>>  delete mode 100644 meta-cgl-common/recipes-extended/iscsi-initiator-
>> utils/iscsi-initiator-utils_%.bbappend
>>  delete mode 100644 meta-cgl-fsl-ppc/conf/layer.conf
>>  delete mode 100644 meta-cgl-fsl-ppc/recipes-kernel/linux/files/Fix-
>> CVE-2014-5077-sctp-inherit-auth-capable-on-INIT-collisions.patch
>>  delete mode 100644 meta-cgl-fsl-ppc/recipes-
>> kernel/linux/files/powerpc-Fix-64-bit-builds-with-binutils-2.24.patch
>>  delete mode 100644 meta-cgl-fsl-ppc/recipes-kernel/linux/linux-
>> qoriq-cgl-prt_3.12.bb
>>
>> --
>> 2.7.4
>>
> This message, including attachments, is CONFIDENTIAL. It may also be 
> privileged or otherwise protected by law. If you received this email by 
> mistake please let us know by reply and then delete it from your system; you 
> should not copy it or disclose its contents to anyone. All messages sent to 
> and from Enea may be monitored to ensure compliance with internal policies 
> and to protect our business. Emails are not secure and cannot be guaranteed 
> to be error free as they can be intercepted, a mended, lost or destroyed, or 
> contain viruses. The sender therefore does not accept liability for any 
> errors or omissions in the contents of this message, which arise as a result 
> of email transmission. Anyone who communicates with us by email accepts these 
> risks.

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

Re: [yocto] [meta-security][rocko][PATCH] clamav: Add missing clamav.service file to SRC_URI

[akuster]

On 03/20/2018 09:28 PM, Jagadeesh Krishnanjanappa wrote:
> Please ignore this patch, it gives an error as it is unable to
> inherit multilib-alternatives.This class is part of our internal layer.

This patch still has value. it addresses the systemd service file
installation.
- armin
>
> Regards,
> Jagadeesh
>
> On Tue, Mar 20, 2018 at 12:20 PM, Jagadeesh Krishnanjanappa
> > wrote:
>
> This solves the below error when systemd is used as init manager,
> -- snip --
> ERROR: clamav-0.99.2-r0 do_package: SYSTEMD_SERVICE_clamav value
> clamav.service does not exist
> ERROR: clamav-0.99.2-r0 do_package: Function failed:
> systemd_populate_packages
> -- snip --
>
> Other issues:
> 1. Ship /lib/systemd/system/clamav-freshclam.service into
> ${PN}-freshclam
>    package, to solve below warning:
> -- snip --
> [10240] WARNING: QA Issue: clamav: Files/directories were
> installed but not shipped in any package:
>   /lib/systemd/system/clamav-freshclam.service
> -- snip --
>
> 2. Solve rpm conflict error in do_populate_sdk, when clamav and
> mlib-clamav
>    are specified using IMAGE_INSTALL.
> -- snip --
> do_populate_sdk fails with below error:
>   file /usr/bin/clamav-config conflicts between attempted installs
> of lib32-clamav-dev-0.99.2-r0.i586 and clamav-dev-0.99.2-r0.corei7_64
> -- snip --
>
> Signed-off-by: Jagadeesh Krishnanjanappa
> >
> ---
>  recipes-security/clamav/clamav_0.99.2.bb
>  | 11 +--
>  1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-security/clamav/clamav_0.99.2.bb
> 
> b/recipes-security/clamav/clamav_0.99.2.bb 
> index 5dfda8f..d7aa6d0 100644
> --- a/recipes-security/clamav/clamav_0.99.2.bb
> 
> +++ b/recipes-security/clamav/clamav_0.99.2.bb
> 
> @@ -14,6 +14,7 @@ SRC_URI =
> "git://github.com/vrtadmin/clamav-devel;branch=${PV}
>  \
>      file://clamd.conf \
>      file://freshclam.conf \
>      file://volatiles.03_clamav \
> +    file://${BPN}.service \
>      "
>
>  SRC_URI[md5sum] = "61b51a04619aeafd965892a53f86d192"
> @@ -26,7 +27,7 @@ SO_VER = "7.1.1"
>
>  EXTRANATIVEPATH += "chrpath-native"
>
> -inherit autotools-brokensep pkgconfig useradd systemd
> +inherit autotools-brokensep pkgconfig useradd systemd
> multilib-alternatives
>
>  UID = "clamav"
>  GID = "clamav"
> @@ -90,8 +91,13 @@ do_install_append() {
>      install -m 0644 ${WORKDIR}/volatiles.03_clamav 
> ${D}${sysconfdir}/default/volatiles/volatiles.03_clamav
>      sed -i -e 's#${STAGING_DIR_HOST}##g'
> ${D}${libdir}/pkgconfig/libclamav.pc
>      rm ${D}/${libdir}/libclamav.so
> +    if
> ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)};then
> +       install -D -m 0644 ${WORKDIR}/clamav.service
> ${D}${systemd_unitdir}/system/clamav.service
> +    fi
>  }
>
> +MULTILIB_ALTERNATIVES_${PN}-dev = "${bindir}/clamav-config"
> +
>  pkg_postinst_${PN} () {
>      if [ -z "$D" ] && [ -e /etc/init.d/populate-volatile.sh ] ; then
>          ${sysconfdir}/init.d/populate-volatile.sh update
> @@ -126,7 +132,8 @@ FILES_${PN}-freshclam = "${bindir}/freshclam \
>                          ${sysconfdir}/clamav
> ${sysconfdir}/default/volatiles \
>                          ${localstatedir}/lib/clamav \
>                          ${docdir}/${PN}-freshclam
> ${mandir}/man1/freshclam.* \
> -                        ${mandir}/man5/freshclam.conf.*"
> +                        ${mandir}/man5/freshclam.conf.* \
> +                       
> ${systemd_unitdir}/system/clamav-freshclam.service"
>
>  FILES_${PN}-dev = " ${bindir}/clamav-config ${libdir}/*.la \
>                      ${libdir}/pkgconfig/*.pc \
> --
> 2.7.4
>
>
>
>

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

Re: [yocto] New Release Number 2.99 in Bugzilla

[akuster]

Stephano


On 03/08/2018 10:46 AM, Stephano Cetola wrote:
> The Yocto Project team is moving to a new release planning process and I
> want to provide an overview as there will be some things I need from
> those of you making changes and adding things to Bugzilla.
>
> Overview:
> We are moving to a “Pull” process for planning rather than a “Push”
> process.  What this means is that we will start with an empty 2.6
> release bucket and pull bugs and enhancements in that map to our top
> priorities rather than push things out of a giant bucket.  We are hoping
> this will help us start 2.6 with a very clear idea as to what we will
> focus on and be much less overwhelming than pushing a giant snowball
> through each release.
>
> How does this effect you?
> If you are pushing bugs/enhancements to the next release or adding new
> bugs/enhancements for the next release you need to be aware of the
> following:
>
> -We have a M+ Future status that holds items that are important and need
> to be addressed soon.  This bucket is pretty big.
> -We have moved all 2.6 features and bugs to a 2.99 release.  This bucket
> is a temporary hold for the items that didn’t make it into 2.5 and are
> at the very top of our list for review to pull in.  We don’t want them
> to get lost in the M+ Future bucket.  Once 2.6 planning is complete,
> this 2.99 bucket will be empty and removed.
> -If you are adding new bugs and enhancements that you believe should be
> slotted for 2.6, please enter them as 2.99.
> -If you are pushing anything from 2.5 to 2.6, please enter it as 2.99.
>
> Please let me know if you have any questions about this.

thanks for the explanation. I wonder if this should be sent to core list
as I believe some bug categories may be non yocto project based or folks
using Poky may not be on list list, like bitbake, yocto-linux etc. Cross
posting may be ok in this case.

- Armn
>
> Thanks,
> Stephano
>

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

Re: [yocto] Yocto Project Technical Team Meeting

[akuster]

On 02/03/2018 09:25 PM, Stephano Cetola wrote:
> On 2/2/18 11:04 AM, Cetola, Stephano wrote:
>> Cetola, Stephano has invited you to Yocto Project Technical Team Meeting
>>
>> When:
>>
>> Occurs the first Tuesday of every month effective 2/6/18 from 8:00 AM to
>> 8:30 AM.
>>  
>> Organizer:
>>
>>  Cetola, Stephano 
>>
>> Description:
>>
>> When: Occurs every month on the first Tuesday of the month from 8:00 AM
>> to 8:30 AM effective 2/6/2018. (UTC-08:00) Pacific Time (US & Canada)
> It has been mentioned to me that there is some confusion on when this
> meeting occurs. I sent this invite using Outlook, which is a necessary
> evil here.
>
> The meeting is from 8:00 - 8:30 (UTC -08:00). I'm happy to send a new
> invite if enough people need one, but I want to minimize the noise here.
Same time, Same Bat Channel only hosted by Robin?

Is this link still correct?

https://www.yoctoproject.org/tools-resources/community/monthly-technical-call

- Armin

We
>
> Cheers,
> Stephano


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

Re: [yocto] [meta-security][PATCH v2] fscryptctl: add v0.1.0

[akuster]

On 10/23/2017 08:51 AM, André Draszik wrote:
> From: André Draszik 
>
> fscryptctl is a low-level tool written in C that handles
> raw keys and manages policies for Linux filesystem
> encryption [1].
>
> For a tool that presents a higher level interface and
> manages metadata, key generation, key wrapping, PAM
> integration, and passphrase hashing, see fscrypt [2].
>
> [1] https://lwn.net/Articles/639427
> [2] https://github.com/google/fscrypt
>
> Signed-off-by: André Draszik 
Merged,

Thanks,
Armin
>
> ---
> v2: add RRECOMMENDS on keyutils, as that might be useful when
> dealing with kernel keys.
> ---
>  recipes-security/fscryptctl/fscryptctl_0.1.0.bb | 27 
> +
>  1 file changed, 27 insertions(+)
>  create mode 100644 recipes-security/fscryptctl/fscryptctl_0.1.0.bb
>
> diff --git a/recipes-security/fscryptctl/fscryptctl_0.1.0.bb 
> b/recipes-security/fscryptctl/fscryptctl_0.1.0.bb
> new file mode 100644
> index 000..4f0b12c
> --- /dev/null
> +++ b/recipes-security/fscryptctl/fscryptctl_0.1.0.bb
> @@ -0,0 +1,27 @@
> +SUMMARY = "low-level tool handling Linux filesystem encryption"
> +DESCIPTION = "fscryptctl is a low-level tool written in C that handles raw 
> keys and manages \
> +policies for Linux filesystem encryption (https://lwn.net/Articles/639427). \
> +For a tool that presents a higher level interface and manages metadata, key \
> +generation, key wrapping, PAM integration, and passphrase hashing, see \
> +fscrypt (https://github.com/google/fscrypt)."
> +HOMEPAGE = "https://github.com/google/fscryptctl;
> +SECTION = "base"
> +LICENSE = "Apache-2.0"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
> +
> +SRCREV = "e4c4d0984dee2531897e13c32a18d5e54a2a4aa6"
> +SRC_URI = "git://github.com/google/fscryptctl.git"
> +
> +S = "${WORKDIR}/git"
> +
> +do_install() {
> +oe_runmake DESTDIR=${D}${bindir} install
> +}
> +
> +RRECOMMENDS_${PN} += "\
> +keyutils \
> +kernel-module-cbc \
> +kernel-module-cts \
> +kernel-module-ecb \
> +kernel-module-xts \
> +"

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

Re: [yocto] [layerindex][PATCH] Indicate if layer has YP Compatible certification

[akuster]

On 09/25/2017 04:41 PM, Amanda Brindle wrote:
> Allow admin to create Yocto Project versions with the version name,
> description, an icon link that represents that version, and a link that
> contains more information about the version.

Who are the Admins ?

- armin
>
> Admins who have the "set_yp_compatibility" permission can then
> decide if a layer has Yocto Project compatible certification,
> and if it does, admin can choose which version of Yocto Project
> the layer is compatible with. If a layer is deemed compatible,
> the version's icon will appear next to the layer's name, and
> the icon will redirect to the link with more information.
>
> Fixes [YOCTO #11452]
>
> Signed-off-by: Amanda Brindle 
> ---
>  layerindex/admin.py| 11 +--
>  layerindex/models.py   | 15 +++
>  layerindex/static/css/additional.css   |  5 +
>  templates/layerindex/detail.html   |  3 +++
>  templates/layerindex/layers.html   |  6 +-
>  templates/layerindex/reviewdetail.html |  3 +++
>  templates/layerindex/reviewlist.html   |  6 +-
>  7 files changed, 45 insertions(+), 4 deletions(-)
>
> diff --git a/layerindex/admin.py b/layerindex/admin.py
> index d25829a..a7d024b 100644
> --- a/layerindex/admin.py
> +++ b/layerindex/admin.py
> @@ -44,6 +44,9 @@ class BranchAdmin(CompareVersionAdmin):
>  layerdependency.save()
>  duplicate.short_description = "Duplicate selected Branches"
>  
> +class YPCompatibleVersionAdmin(CompareVersionAdmin):
> +pass
> +
>  class LayerItemAdmin(CompareVersionAdmin):
>  list_filter = ['status', 'layer_type']
>  save_as = True
> @@ -61,9 +64,12 @@ class LayerBranchAdmin(CompareVersionAdmin):
>  LayerMaintainerInline,
>  ]
>  def get_readonly_fields(self, request, obj=None):
> +readonly_fields = self.readonly_fields
>  if obj:
> -return self.readonly_fields + ('layer', 'branch')
> -return self.readonly_fields
> +readonly_fields += ('layer', 'branch')
> +if not request.user.has_perm('layerindex.set_yp_compatibility'):
> +readonly_fields += ('yp_compatible_version',)
> +return readonly_fields
>  
>  class LayerMaintainerAdmin(CompareVersionAdmin):
>  list_filter = ['status', 'layerbranch__layer__name']
> @@ -145,6 +151,7 @@ class RecipeChangesetAdmin(admin.ModelAdmin):
>  ]
>  
>  admin.site.register(Branch, BranchAdmin)
> +admin.site.register(YPCompatibleVersion, YPCompatibleVersionAdmin)
>  admin.site.register(LayerItem, LayerItemAdmin)
>  admin.site.register(LayerBranch, LayerBranchAdmin)
>  admin.site.register(LayerMaintainer, LayerMaintainerAdmin)
> diff --git a/layerindex/models.py b/layerindex/models.py
> index fb2e026..2297152 100644
> --- a/layerindex/models.py
> +++ b/layerindex/models.py
> @@ -141,6 +141,17 @@ class LayerItem(models.Model):
>  def __str__(self):
>  return self.name
>  
> +class YPCompatibleVersion(models.Model):
> +name = models.CharField('Yocto Project Version', max_length=25, 
> unique=True, help_text='Name of this Yocto Project compatible version (e.g. 
> "2.0")')
> +description = models.TextField(blank=True)
> +image_url = models.CharField('Image URL', max_length=300, blank=True)
> +redirect_url = models.CharField('Redirection URL', max_length=100, 
> blank=True)
> +
> +class Meta:
> +ordering = ('name',)
> +
> +def __str__(self):
> +return self.name
>  
>  class LayerBranch(models.Model):
>  layer = models.ForeignKey(LayerItem)
> @@ -152,11 +163,15 @@ class LayerBranch(models.Model):
>  vcs_last_rev = models.CharField('Last revision fetched', max_length=80, 
> blank=True)
>  vcs_last_commit = models.DateTimeField('Last commit date', blank=True, 
> null=True)
>  actual_branch = models.CharField('Actual Branch', max_length=80, 
> blank=True, help_text='Name of the actual branch in the repository matching 
> the core branch')
> +yp_compatible_version = models.ForeignKey(YPCompatibleVersion, 
> null=True, blank=True, on_delete=models.SET_NULL, help_text='Which version of 
> the Yocto Project Compatible program has this layer been approved for for?')
>  
>  updated = models.DateTimeField(auto_now=True)
>  
>  class Meta:
>  verbose_name_plural = "Layer branches"
> +permissions = (
> +("set_yp_compatibility", "Can set YP compatibility"),
> +)
>  
>  def sorted_recipes(self):
>  return self.recipe_set.order_by('pn', '-pv')
> diff --git a/layerindex/static/css/additional.css 
> b/layerindex/static/css/additional.css
> index 2a27712..324ee34 100644
> --- a/layerindex/static/css/additional.css
> +++ b/layerindex/static/css/additional.css
> @@ -232,3 +232,8 @@ blockquote.span7.warn {
>  .valign-middle {
>  vertical-align: middle;
>  }
> +
> +.yp-icon {
> +width: auto;
> +height: 1em;
> +}
> diff --git 

Re: [yocto] libgcrypt building fails for armv6 binaries.

[akuster]

On 09/22/2017 09:15 PM, Yusuke Mitsuki wrote:
> Hello yocto
>
> libgcrypt has problem that build for armv6.
> bitbake said error messages at do_compile as follows:
> ...(snip)...
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S: Assembler 
> messages:
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r9,r9' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r10,r10' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r11,r11' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r9,r9' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r10,r10' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r11,r11' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
> Error: selected processor does not support `rbit r9,r9' in ARM mode
> ...(snip)...
>
> I googled about this problem then I found the clue at here.
> https://mail-index.netbsd.org/pkgsrc-bugs/2017/08/01/msg062410.html
>
> I thought it fixed at libcrypt_1.8.1.
>
> I tried update to 1.8.1. It seems fine.
> So I suggest the libgcrypt updating for 1.8.1.
It may be too late to update  as we are in the stabilization phase of
the next release.
>
> By the way, I created the patch for this problem.
The is great and much appreciated.

> But I am not sure, where to send to this patch?
Yes it is a bit confusing and we should revisit the documentation.
> I could not found the guidelines of contributing [meta].
> I should send to OE-Core's ML? or  here directly?

The oe-core ML is the appropriate place.


>
> And, Would you let me know what strings of options to git send-email I
> should to set?
if you want to us git send mail, I use the following.

git send-email -1 -M --to  openembedded-c...@lists.openembedded.org
--subject-prefix=PATCH

regards,
Armin

> Thanks.


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

Re: [yocto] [meta-security][PATCH] packagegroups: fix invalid license file

[akuster]

On 09/15/2017 02:17 AM, jackie.hu...@windriver.com wrote:

From: Jackie Huang 

Use '${COMMON_LICENSE_DIR}/MIT' for MIT License to fix the warning:

| WARNING: packagegroup-core-security do_populate_lic:
   ${COREBASE}/LICENSE is not a valid license file, please use
   '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM.
   This will become an error in the future

Signed-off-by: Jackie Huang 


merged,
Thanks,
Armin

---
  meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb | 2 +-
  meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb | 2 +-
  meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb| 2 +-
  meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb| 2 +-
  recipes-security/packagegroup/packagegroup-core-security.bb | 2 +-
  5 files changed, 5 insertions(+), 5 deletions(-)

diff --git 
a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb 
b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
index 2d93aca..3b9d271 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
@@ -1,6 +1,6 @@
  DESCRIPTION = "Security packagegroup for TPM i2c support"
  LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
  
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
  
  inherit packagegroup

diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb 
b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
index 2db8521..25126ef 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
@@ -1,6 +1,6 @@
  DESCRIPTION = "Security packagegroup for Poky"
  LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
  
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
  
  inherit packagegroup

diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb 
b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
index 57b0722..13b505f 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
@@ -1,6 +1,6 @@
  DESCRIPTION = "Security packagegroup for Poky"
  LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
  
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
  
  inherit packagegroup

diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb 
b/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
index f7eee7c..2e9394f 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
@@ -1,6 +1,6 @@
  DESCRIPTION = "Security packagegroup for Poky"
  LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
  
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
  
  inherit packagegroup

diff --git a/recipes-security/packagegroup/packagegroup-core-security.bb 
b/recipes-security/packagegroup/packagegroup-core-security.bb
index cfd7918..6682d29 100644
--- a/recipes-security/packagegroup/packagegroup-core-security.bb
+++ b/recipes-security/packagegroup/packagegroup-core-security.bb
@@ -1,6 +1,6 @@
  DESCRIPTION = "Security packagegroup for Poky"
  LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
  
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
  
  inherit packagegroup


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

Re: [yocto] [meta-security][PATCH 0/4] samhain: fix several issues

[akuster]

On 09/15/2017 12:37 AM, jackie.hu...@windriver.com wrote:

From: Jackie Huang 

merged,
Thanks
- armin

--
The following changes since commit b646d8fdc08f8aac896a09bda0e16bac39e87612:

   nmap: update to 7.60 (2017-09-13 07:36:44 -0700)

are available in the git repository at:

   git://git.pokylinux.org/poky-contrib.git jhuang0/d_samhain_170915_0
   http://git.pokylinux.org/cgit.cgi//log/?h=jhuang0/d_samhain_170915_0

Jackie Huang (4):
   samhain: depends on attr when selinux is enabled
   samhain: fix for the PACKAGECONFIG
   samhain: avoid searching host dir for postgresql
   samhain: fix QA issue for GNU_HASH

  ...n-add-LDFLAGS-variable-for-samhain_setpwd.patch |  28 +
  ...mhain-avoid-searching-host-for-postgresql.patch | 134 +
  recipes-security/samhain/samhain.inc   |  28 +++--
  3 files changed, 178 insertions(+), 12 deletions(-)
  create mode 100644 
recipes-security/samhain/files/samhain-add-LDFLAGS-variable-for-samhain_setpwd.patch
  create mode 100644 
recipes-security/samhain/files/samhain-avoid-searching-host-for-postgresql.patch



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

Re: [yocto] [meta-security][PATCH 00/10] move tpm into its own layer

[akuster]

On 05/10/2017 12:46 AM, Dominig ar Foll (Intel Open Source) wrote:

Armin,

very interesting move. Could you tell us where is located your git repo ?

http://git.yoctoproject.org/cgit/cgit.cgi/meta-security/

currently the changes are in master-next

- armin

Regards

Dominig

Le 09/05/2017 à 16:46, Armin Kuster a écrit :

tpm recipes copied as-is

This was done to allow inclusion of TPM components independent of the rest of 
the layer.
minimizes layerdepends

fixed incorrect use of DISTRO_FEATURES

Updated tpm kernel configs to newer version

added a few new packagegroups

Armin Kuster (10):
   tpm: move to a sub layer
   change tpm from distro to machine feature
   meta-tpm: add base package group as was in meta-security
   packagegroup: remove tpm components
   tpm packagegroups: split into logical units
   tpm-i2c: some systems us i2c TPM
   kernel tpm rework
   tpm-image: used for testing for now.
   linux-stable: fix module selections
   tpm2: package groups fixes

  meta-tpm/README|  0
  meta-tpm/conf/layer.conf   | 13 ++
  meta-tpm/recipes-core/images/security-tpm-image.bb | 19 ++
  .../packagegroup/packagegroup-security-tpm-i2c.bb  | 19 ++
  .../packagegroup/packagegroup-security-tpm.bb  | 29 ++
  .../packagegroup/packagegroup-security-tpm2.bb | 18 ++
  .../packagegroup/packagegroup-security-vtpm.bb | 14 +++
  meta-tpm/recipes-kernel/linux/linux-yocto/tpm.cfg  |  8 ++
  meta-tpm/recipes-kernel/linux/linux-yocto/tpm.scc  |  3 +++
  meta-tpm/recipes-kernel/linux/linux-yocto/tpm2.cfg |  6 +
  meta-tpm/recipes-kernel/linux/linux-yocto/tpm2.scc |  3 +++
  .../recipes-kernel/linux/linux-yocto/tpm_i2c.cfg   | 15 +++
  .../recipes-kernel/linux/linux-yocto/tpm_i2c.scc   |  6 +
  .../recipes-kernel/linux/linux-yocto/tpm_x86.cfg   |  4 +++
  meta-tpm/recipes-kernel/linux/linux-yocto/vtpm.cfg |  5 
  meta-tpm/recipes-kernel/linux/linux-yocto/vtpm.scc |  4 +++
  .../recipes-kernel/linux/linux-yocto_4.%.bbappend  | 17 +
  .../Convert-another-vdprintf-to-dprintf.patch  |  0
  .../files/Use-format-s-for-call-to-dprintf.patch   |  0
  .../libtpm/files/fix_signed_issue.patch|  0
  .../recipes-tpm}/libtpm/libtpm_1.0.bb  |  0
  .../recipes-tpm}/swtpm/files/fix_fcntl_h.patch |  0
  .../swtpm/files/fix_lib_search_path.patch  |  0
  .../swtpm/files/fix_signed_issue.patch |  0
  .../recipes-tpm}/swtpm/files/ioctl_h.patch |  0
  .../recipes-tpm}/swtpm/swtpm-wrappers-native.bb|  0
  .../recipes-tpm}/swtpm/swtpm_1.0.bb|  0
  .../tpm-tools/files/tpm-tools-extendpcr.patch  |  0
  .../recipes-tpm}/tpm-tools/tpm-tools_git.bb|  0
  .../recipes-tpm}/tpm2.0-tools/tpm2.0-tools_git.bb  |  0
  .../tpm2.0-tss/tpm2.0-tss/ax_pthread.m4|  0
  .../tpm2.0-tss/fix_musl_select_include.patch   |  0
  .../recipes-tpm}/tpm2.0-tss/tpm2.0-tss_git.bb  |  0
  .../tpm2simulator/tpm2simulator-native_116.bb  |  0
  ...path-use-POSIX-getpwent-instead-of-getpwe.patch |  0
  .../recipes-tpm}/trousers/files/tcsd.service   |  0
  .../trousers/files/trousers-udev.rules |  0
  .../recipes-tpm}/trousers/files/trousers.init.sh   |  0
  .../recipes-tpm}/trousers/trousers_git.bb  |  0
  recipes-kernel/linux/linux-yocto_4.10.bbappend |  3 ---
  .../packagegroup/packagegroup-core-security.bb | 18 ++
  41 files changed, 185 insertions(+), 19 deletions(-)
  create mode 100644 meta-tpm/README
  create mode 100644 meta-tpm/conf/layer.conf
  create mode 100644 meta-tpm/recipes-core/images/security-tpm-image.bb
  create mode 100644 
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
  create mode 100644 
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
  create mode 100644 
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
  create mode 100644 
meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm.cfg
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm.scc
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm2.cfg
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm2.scc
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm_i2c.cfg
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm_i2c.scc
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm_x86.cfg
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/vtpm.cfg
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/vtpm.scc
  create mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto_4.%.bbappend
  rename {recipes-tpm => 
meta-tpm/recipes-tpm}/libtpm/files/Convert-another-vdprintf-to-dprintf.patch (100%)
  rename {recipes-tpm => 

Re: [yocto] [meta-security][PATCH 1/1] swtpm-wrappers: fix naming convention violation

[akuster]

On 04/25/2017 02:14 AM, Patrick Ohly wrote:

Native recipes must be called -native. This is more than just a
recommendation, there's actual code which checks for the suffix.

Not following that rule broke swtpm-wrappers when using the "usrmerge"
DISTRO_FEATURE, because the code in native.bbclass which cleans up
DISTRO_FEATURES for native recipes was skipped and thus swtpm-wrappers
ended up using different paths than the other native recipes.

Signed-off-by: Patrick Ohly 


merged.

thanks,
Armin

---
  recipes-tpm/swtpm/{swtpm-wrappers.bb => swtpm-wrappers-native.bb} | 0
  1 file changed, 0 insertions(+), 0 deletions(-)
  rename recipes-tpm/swtpm/{swtpm-wrappers.bb => swtpm-wrappers-native.bb} 
(100%)

diff --git a/recipes-tpm/swtpm/swtpm-wrappers.bb 
b/recipes-tpm/swtpm/swtpm-wrappers-native.bb
similarity index 100%
rename from recipes-tpm/swtpm/swtpm-wrappers.bb
rename to recipes-tpm/swtpm/swtpm-wrappers-native.bb


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

Re: [yocto] Morty 2.2.1 build failure

[akuster]

On 03/23/2017 12:25 PM, Paul Eggleton wrote:

That's really bizarre. There shouldn't be anything in a bitbake build that
could cause anything like this (other than possibly how intensive it is, which
might trigger out-of-memory or an underlying hardware/software failure).


I usually get my builds to reboot my system when I build on a loptop. I 
have not seen this on a tower style work station. You may want to play 
with the BB_NUMBER_THREADS=# and PARALLEL_MAKE = "-j #" settings in your 
local.conf.


- armin


Assuming the X session is ending is there anything in your ~/.xsession-errors
or /var/log/Xorg.*.log?

Cheers,
Paul

On Friday, 24 March 2017 5:58:24 AM NZDT Greg Wilson-Lindberg wrote:

Hi Paul,

I looked in the logs from the failure yesterday and couldn't find anything,
so I restarted the build and it ran for about another 1000 steps before
crashing again. I still can't find anything in any of the logs, syslog,
kern.log, auth.log, etc.

Cheers,
Greg


-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Thursday, March 23, 2017 2:49 AM
To: Greg Wilson-Lindberg <gwil...@sakuraus.com>
Cc: yocto@yoctoproject.org; akuster808 <akuster...@gmail.com>
Subject: Re: [yocto] Morty 2.2.1 build failure

On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg wrote:

I tried it again this morning and it did get past the file not found
error.
But when it gets above step 4000 somewhere it gets an error that kills
not just the yocto build but the full login session. I'm left staring
at the Linux Login screen.

Your machine isn't running out of RAM by any chance, triggering the OOM
killer? Anything indicative in your system logs?

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre




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

Re: [yocto] [meta-security][PATCH] swtpm: depends on expect-native and socat-native

[akuster]

On 03/22/2017 02:39 AM, Benjamin Gaignard wrote:

The configure script checks for expect and socat and
fails when it is not present.


merged,

thanks

Signed-off-by: Benjamin Gaignard 
---
  recipes-tpm/swtpm/swtpm_1.0.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-tpm/swtpm/swtpm_1.0.bb b/recipes-tpm/swtpm/swtpm_1.0.bb
index 0d3bab0..7b9662a 100644
--- a/recipes-tpm/swtpm/swtpm_1.0.bb
+++ b/recipes-tpm/swtpm/swtpm_1.0.bb
@@ -7,7 +7,7 @@ DEPENDS = "libtasn1 fuse expect socat glib-2.0 libtpm 
libtpm-native"
  
  # configure checks for the tools already during compilation and

  # then swtpm_setup needs them at runtime
-DEPENDS += "tpm-tools-native"
+DEPENDS += "tpm-tools-native expect-native socat-native"
  RDEPENDS_${PN} += "tpm-tools"
  
  SRCREV = "65d8e4d83447f4c13a41a6f995bd0490f49bc5ef"


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

Re: [yocto] Yocto Project Status WW47

[akuster]

Stephen


On 11/18/2016 08:35 AM, Jolley, Stephen K wrote:


Current Dev Position: YP 2.3 M1

Next Deadline: YP 2.3 M1 by Dec. 12, 2016

SWAT team rotation: Leo -> Juro

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:



Thanks for the updates.


·2.1.2 QA report is out and likely to be released imminently.

·The QA report for 2.1.2 is at: 
https://wiki.yoctoproject.org/wiki/WW46_-_2016-11-10_-_Test_Cycle_2.1.2_rc1


·At this point most 2.3 targeted features should have been identified 
in bugzilla. M1 is comparatively loaded compared to M2/M3 and some 
individuals have particularly heavy workloads so loading balancing is 
being done.


·We’ll run a 2.0.3 test build over the weekend to find out our status 
there.


·Backports of fixes to the morty release branch are now occurring, 
thanks Armin. Armin is looking like the principle morty maintainer for 
that stable release series.


·There are some changes planned to the getVar/getVarFlag expansion 
defaults and the old data store APIs are likely to be removed 
imminently. There is an email on the openembedded-architecture list 
about this.


·WDD is now climbing again unfortunately, we’ve wiped out half of the 
improvements we made in the 2.2 cycle.


Proposed upcoming dot releases:

YP 2.0.3 Release by Dec. 9, 2016

YP 2.2.1 Release by Jan. 20, 2017

YP 2.1.3 Release by May. 19, 2017



Would it be reasonable to target a "Code freeze/cutoff" (ie last day to 
accept patch for any of those dot releases) the week before or more to 
give Maintainers time to merge and run a test build(s)?


- Armin


Key YP 2.3 Dates:

YP 2.3 M1 Cutoff is Dec. 12, 2016

YP 2.3 M1 Release is Dec. 23, 2016

YP 2.3 M2 Cutoff is Jan. 23, 2017

YP 2.3 M2 Release is Feb. 3, 2017

YP 2.3 M3 Cutoff is Feb 27, 2017

YP 2.3 M3 Release is Mar. 10, 2017

YP 2.3 M4 Cutoff is April 3, 2017

YP 2.3 M4 Release is April 28, 2017

Tracking Metrics:

WDD 2516 (last week 2497)

(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

[If anyone has suggestions for other information you’d like to see on 
this weekly status update, let us know!]


Thanks,

*/Stephen K. Jolley/**//*

*Yocto Project Program Manager*

*INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *

(*Work Telephone*: (503) 712-0534

(*Cell*: (208) 244-4460

* *Email*:_stephen.k.jolley@intel.com_





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

Re: [yocto] Yocto Project Status WW45 - UPDATED

[akuster]

On 11/04/2016 10:06 AM, Jolley, Stephen K wrote:


Current Dev Position: YP 2.3 M1

Next Deadline: YP 2.3 M1 by Dec. 12, 2016

SWAT team rotation: Ross -> Randy

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

·2.2 was released!

·Patches are starting to be merged into master

·We are intending to have point releases for 2.0 and 2.1, this is 
dependent on good build test results.


·We are having various issues with the new autobuilder so it is still 
not in production use yet.


·There was a challenging taskhash mismatch test case this week which 
has resulted in some significant debugging improvements for taskhashes 
and basehashes which are now in master.


·2.3 planning is underway and RP will send more thoughts on the plans 
for that in the next couple of weeks.


·We are going to make a strong effort to load balance things up front 
this time so work is spread over M1-3 rather than the usual ‘front 
loaded’ everything in M1 approach which is currently how bugzilla looks.


Proposed upcoming dot releases:

YP 2.0.3 Release by Nov. 18, 2016

YP 2.1.2 Release by Dec. 9, 2016

YP 2.2.1 Release by Jan. 20, 2017


So is there a Morty Maintainer ?


Key YP 2.3 Dates:

YP 2.3 M1 Cutoff is Dec. 12, 2016

YP 2.3 M1 Release is Dec. 23, 2016

YP 2.3 M2 Cutoff is Jan. 23, 2017

YP 2.3 M2 Release is Feb. 3, 2017

YP 2.3 M3 Cutoff is Feb 27, 2017

YP 2.3 M3 Release is Mar. 10, 2017

YP 2.3 M4 Cutoff is April 3, 2017

YP 2.3 M4 Release is April 28, 2017

Tracking Metrics:

WDD 2422 (last week 2394)

(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

[If anyone has suggestions for other information you’d like to see on 
this weekly status update, let us know!]


Thanks,

*/Stephen K. Jolley/**//*

*Yocto Project Program Manager*

*INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *

(*Work Telephone*: (503) 712-0534

(*Cell*: (208) 244-4460

* *Email*:_stephen.k.jolley@intel.com_





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

Re: [yocto] General policies for CVE fixes

[akuster]

On 10/19/2016 03:42 AM, Sona Sarmadi wrote:

 From https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance:

General policies:

Fixes must go into master first unless they are applicable only to the
stable branch; if back-porting to an older stable branch, the fix
should first be applied to the newer stable branches before being
back-ported to the older branch

Does anyone know the reason for the policy above i.e. why fixes have
to go to master first?

1)  It makes more sense at least for users  to get CVE fixes as soon as
possible in the maintenance branches.

this is to ensure, that we do not regress next time when we release next
version from master. So its important to ensure that the fix has been
applied to master sometimes you can assert that the fix has gone into new
version of a package that is due to be uprevved in master and will be
done soonish. Such information is helpful when making security patches
for release branches.

Actually there was a suggestion at OEDEM on informing CVE ml that we
have as the CVE fixes get applied to metadata. Thats a good suggestion to
have implemented.


Thanks everyone for your explanation.

Yes regressions (forgetting to fix bugs in master) are bad.  I believe there
are other ways to avoid this, Yocto project has a bug reporting system to
have track of such things, right?
The issue there is if Jethro gets a fix and Krogoth, morty and mater  
need it as well, the bug system implies someone else is going to have to 
do the work.
That is the problem. Not too many people are stepping up to do the work 
in the other branches.




Maintenance branches are likely deployed in production systems, I think
Fixing security problems here should have higher priority.
You are more than welcome to submit patches for the stable branch you 
are concerned about knowing the patches wont be applied until the parent 
branches are addressed first.



  Don't you agree?

Perhaps we should discuss this at next OEDEM :)
We have and until more people step up to help, this will be a constant 
issue.


-armin


Cheers //Sona


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

Re: [yocto] Yocto Project Status WW40

[akuster]

On 09/30/2016 08:26 AM, Jolley, Stephen K wrote:


Current Dev Position: YP 2.2 M4

Next Deadline: YP 2.2 M4 which will be Oct. 3rd (5:00pm GMT)

SWAT team rotation: Joshua -> Armin

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

·We’re seeing a lot of good bug fixing on master, we still have quite 
a number of open medium+ bugs which I’d like to see fixed in 2.2.


·The 4.8 kernel is not out yet so the first rc build will likely be 
delayed until it is. We also haven’t run a pretest to verify the 
issues in M3 are fixed as we haven’t merged enough fixes yet so this 
isn’t a huge issue.




Will we delay the release if 4.8 is not released in time?


·The YP 2.2 branch name will be “morty”.

·I was asked to announce the release codenames earlier so the YP 2.3 
branch name will be “pyro”.


·There were some serious regressions on krogoth around 
useradd/systemd. I often hear complaints we don’t move fast enough 
with the stable release, this was a reminder of how we can get it 
badly wrong.




No kidding. How one benign looking change did so much damage. My 
apologies for not being more vigilant.


- armin


·The defect tracking metric dropped this week, we’re 50 points off the 
2.1 level and I’m hoping we can achieve a bug reduction to that level 
before release.


Key YP 2.2 Dates:

·YP 2.2 M4 cut off would be: 10/3/16

·YP 2.2 M4 release would be: 10/28/16

Tracking Metrics:

WDD 2451 (last week 2557)

(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

[If anyone has suggestions for other information you’d like to see on 
this weekly status update, let us know!]


Thanks,

*/Stephen K. Jolley/**//*

*Yocto Project Program Manager*

*INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *

(*Work Telephone*: (503) 712-0534

(*Cell*: (208) 244-4460

* *Email*:_stephen.k.jolley@intel.com_





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

Re: [yocto] Patchwork users: Help test new version

[akuster]

On 06/20/2016 10:47 AM, Michael Halstead wrote:
> Hello,
> 
> OpenEmbedded is nearly ready to upgrade to a new version of Patchwork.
> The new version offers several new features that will allow OpenEmbedded
> to improve developer workflow and automated checks on incoming patches.


> 
> If you are a Patchwork user please visit
> https://patchwork-next.openembedded.org/ and take a look. If you find
> anything amiss please e-mail me directly and include patchwork in the
> subject line.

great. I will take a look.

> 
> Thank you for your help upgrading this important system!
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] NTP

[akuster]

On 06/16/2016 11:33 PM, Anicic Damir (PSI) wrote:
> Hi!
> 
> I just realised that ntpd + ntpdate is not part of Yocto 2.1

ntpdate is in the ntpdate package and ntpd is in the ntp package.

The ntp recipe is in meta-openembedded/meta-networking

you will need to append these to your image install.

- armin
> 
> I found http://layers.openembedded.org/layerindex/recipe/2299/
> 
> but how to get it?
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.1 powerpc64 e6500 - postinstall intercept hook problems

[akuster]

On 06/15/2016 12:23 PM, Khem Raj wrote:
> 
>> On Jun 15, 2016, at 1:27 AM, Anicic Damir (PSI)  wrote:
>>
>> Hi !
>>
>> I am trying to build Yocto 2.1 for PowerPC64, e6500 CPU.
>>
>> I managed to build, with warnings that some steps will be postponed to first 
>> boot,
>> but if I add "read-only-rootfs" then warnings change to errors.
>>
>> The problem seems to be missing qemu-ppc64, see down "exit code: 127".
>> qemu-* executables ( tmp/sysroots/x86_64-linux/usr/bin/qemu-* ) are built, 
>> but qemu-ppc64 is missing.
>>
>> If I build qemu-ppc64 (qemu 2.6) myself (install it to /usr/local/bin which 
>> is in PATH),
>> then I get "Invalid instruction" from my qemu-ppc64.
>>
>>
>> My build (core-image-psi-gfa-cmd is basically core-image-full-cmdline ):
>>
>>   Build Configuration:
>>   BB_VERSION= "1.30.0"
>>   BUILD_SYS = "x86_64-linux"
>>   NATIVELSBSTRING   = "ScientificLinux-6.4"
>>   TARGET_SYS= "powerpc64-poky-linux"
>>   MACHINE   = "powerpc64-ppc64e6500"
>>   DISTRO= "gfa-ppc64e6500"
>>   DISTRO_VERSION= "2.1"
>>   TUNE_FEATURES = "m64 fpu-hard e6500 altivec"
>>   TARGET_FPU= ""
>>   meta
>>   meta-poky
>>   meta-yocto-bsp
>>   meta-gfa  = 
>> "krogoth-gfa-v2:898a78357e72fb80f1f8e26ba90bad5b7b054a4f"
>>
>>   NOTE: Preparing RunQueue
>>   NOTE: Executing SetScene Tasks
>>   NOTE: Executing RunQueue Tasks
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstall 
>> intercept hook 'update_gio_module_cache' failed (exit code: 127)! See log 
>> for details!
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: The postinstalls for the 
>> following packages will be postponed for first boot: libglib-2.0-0
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] 
>> core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 
>> 'WARNING:'):
>>   [log_check] WARNING: The postinstall intercept hook 
>> 'update_gio_module_cache' failed (exit code: 127)! See log for details!
>>
>>   WARNING: core-image-psi-gfa-cmd-1.0-r0 do_rootfs: [log_check] 
>> core-image-psi-gfa-cmd: found a warning message in the logfile (keyword 
>> 'WARNING:'):
>>   [log_check] WARNING: The postinstalls for the following packages will be 
>> postponed for first boot: libglib-2
>>
>>
>> If I build core-image-psi-gfa-cmd ( which is basicaly core-image-lsb-sdk ),
>> then there are few more postinstall problems, too:
>>   The postinstalls for the following packages will be postponed for first 
>> boot:
>>  libgdk-pixbuf-2.0-loader-ico libgdk-pixbuf-2.0-loader-bmp 
>> libgdk-pixbuf-2.0-loader-jpeg
>>  libgdk-pixbuf-2.0-loader-png   libgdk-pixbuf-2.0-loader-gif 
>> libgdk-pixbuf-2.0-loader-xpm libgdk-pixbuf-2.0-loader-ani
>>
>> all with the same qemu-ppc64 problem.

There is no official qemuppc64 on OE. I do have it in my own bsp layer.
I will be submitting patches soon.

- armin
> 
> 
> we do not have qemuppc64 working correctly in all cases. We now depend on 
> Qemu to do some compile tasks which are not easily cross compilable. Those 
> will fail.
> 
>>
>>
>> I have additionally eudev postinstall problem (generating hwdb.bin) 
>> -probably also qemu related
>>
>>
>> Please help.
>>
>> Kind regards,
>>
>> Damir
>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org 
>> https://lists.yoctoproject.org/listinfo/yocto 
>> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Status WW24

[akuster]

On 06/10/2016 08:21 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.2 M1
> 
> Next Deadline: YP 2.2 cut off: June 13, 2016 [3 days - Monday!]
> 
> 
> SWAT team rotation: Jussi -> Maxim
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> 
> Key Status/Updates:
> 
> *We continue to see various python v3 issues however these are on the 
> most part comparatively minor.
> 
> *The Centos 7 auobuilder issues look to have been caused by XFS, 
> switching to ext4 seems to have resolved it.
> 
> *We're expecting some large patchsets for toaster bootstrap v2 -> v3 
> and changes to move OE-Core/Sato to gtk3+, am hoping to get these into M1.
> 
> *Richard is starting a discussion on multi-configuration builds on 
> the openembedded-architecture list.
> 
> *YP 2.0.2 was released last week
> 
> *We're now working on 2.1.1 with trial builds in preparation for a 
> release

Can I get a sense of when this might happen? when is a code freeze for
this. I am wondering if I have time for another pass through master and
submitted patches. As the Yocto Project follows a more formalized
process, I am hoping I can get a heads up on when a new release is going
to happen.

- armin
> 
> *2.2 M1 is due next week
> 
> 
> Key YP 2.2 Dates:
> 
> *YP 2.2 M1 cut off would be: 6/13/16
> 
> *YP 2.2 M1 release would be: 6/24/16
> 
> *YP 2.2 M2 cut off would be: 7/18/16
> 
> *YP 2.2 M2 release would be: 7/29/16
> 
> *YP 2.2 M3 cut off would be: 8/29/16
> 
> *YP 2.2 M3 release would be: 9/9/16
> 
> *YP 2.2 M4 cut off would be: 10/3/16
> 
> *YP 2.2 M4 release would be: 10/28/16
> 
> 
> Tracking Metrics:
> 
> WDD 2599 (last week 2622)
> 
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> 
> Key Status Links for YP:
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
> 
> [If anyone has suggestions for other information you'd like to see on this 
> weekly status update, let us know!]
> 
> Thanks,
> 
> Stephen K. Jolley
> Yocto Project Program Manager
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
> *   Work Telephone:(503) 712-0534
> *Cell:   (208) 244-4460
> * Email:stephen.k.jol...@intel.com
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.0.2 (Jethro 14.0.2) Released

[akuster]

On 06/03/2016 06:10 PM, Tracy Graydon wrote:

Hello,,

Tracy,



The latest release of the Yocto Project 2.0.2 (jethro-14.0.2) is now available
for download at:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/poky-fido-14.0.2.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/RELEASENOTES

Full pass test report is available at:

https://wiki.yoctoproject.org/wiki/WW23_-_2016-05-24_-_Full_Pass_2.0.2.rc1
is there an easy way to find the test results from the previous update 
releases and the initial version release?




Thanks to everyone for all their hard work on this release!

+1

- armin


Sincerely,

Tracy Graydon
Yocto Project
Build and Release

--
yocto-2.0.2 Errata


Release Name: eclipse-poky-kepler-jethro-14.0.2
Branch: kepler/jethro
Tag: kepler/jethro-14.0.2
Hash: cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
md5: 1a542aecf32a80e546689a435bf53d11
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/eclipse-poky-kepler-jethro-14.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/eclipse-poky-kepler-jethro-14.0.2.tar.bz2

Release Name: eclipse-poky-luna-jethro-14.0.2
Branch: luna/jethro
Tag: luna/jethro-14.0.2
Hash: 45aa5c77523bdf051d548fff4305382942db2ebb
md5: e8c251d3e469d260b6beea00b00dc614
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/eclipse-poky-luna-jethro-14.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/eclipse-poky-luna-jethro-14.0.2.tar.bz2

Release Name: eclipse-poky-mars-jethro-14.0.2
Branch: mars/jethro
Tag: mars/jethro-14.0.2
Hash: 1d179ddcbd1983bf7bcfe98efdcbb186bdccca4f
md5: 14e7528f8b13bb9b31fdb2be3da0a3f1
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/eclipse-poky-mars-jethro-14.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/eclipse-poky-mars-jethro-14.0.2.tar.bz2

Release Name: meta-qt3-jethro-14.0.2
Branch: jethro
Tag: jethro-14.0.2
Hash: b08996efbfb3b26e62b608f34ebf5e671b36ec61
md5: ffb7af0fef8e3c1f04e0a595848a102e
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/meta-qt3-jethro-14.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/meta-qt3-jethro-14.0.2.tar.bz2

Release Name: poky-jethro-14.0.2
Branch: jethro
Tag: jethro-14.0.2
Hash: dade0e68c645473d94e1b05020b064df40677e81
md5: 854586669612e553f9cb59bf8c329a65
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2


---
  Known Issues
---
n/a

---
Security Fixes
---
gcc: Security Fix CVE-2016-4490
gcc: Security fix CVE-2016-2226
gcc: Security fix CVE-2016-4489
gcc: Security fix CVE-2016-4488
openssh: Security Fix CVE-2016-3115
busybox: Security fix CVE-2016-2147
busybox: Security Fix CVE-2016-2148
libtiff: Security fix CVE-2015-8664 and 8683
openssl: 1.0.2d -> 1.0.2h (mainly for CVEs)
glibc: Fix CVE-2015-8778
bind: CVE-2016-1285 CVE-2016-1286
dhcp: CVE-2015-8605
openssl: Security fix CVE-2016-0800
wpa-supplicant: Fix CVE-2015-8041

---
Fixes
---
wic: insert local Python paths at front
build-appliance-image: Update to jethro head revision
poky.conf: Bump version for 2.0.2 jethro release
build-appliance-image: Update to jethro head revision
gdb: Backport patch to changes with AVX and MPX
yocto-bsp: Set correct default branches and branches base for i386, qemu and 
x86_64 archs
yocto-bsp: fix default kernel for x86_64 arch
conf/distro/poky.conf: use example.com for connectivity check
openssl: prevent ABI break from earlier jethro releases
Revert "kernel/kernel-arch: Explicitly mapping between, i386/x86_64 and x86 for 
kernel ARCH"
glew: Correct version in autotooling patches
gdb: fix QA warning (uClibc)
binutils: backport bug fix to the 2.25 branch for jethro
boot-directdisk.bbclass: remove HDDIMG before create
opkg: backport fix for double remove of packges
license.bbclass: fix warnings when run in unprivileged "container" env
tzdata: update to 2016d
tzcode: update to 2016d
tzcode: update to 2016c
tzdata: update to 2016c
tzcode: update to 2016b
tzdata: update to 2016b
yocto-project-qs: Updated the minnowboard example.
poky.ent: Added lower-case distro name variable.
lttng-tools: fix regression tests hang
ncurses: update SRC_URI
python3: fix building nativesdk-python3
systemd-serialgetty: allow baud rate overriding
boost: ensure boost to remain an empty metapackage
systemd: chown hwdb.bin to root:root for do_rootfs
cdrtools: update SRC_URI
gcc-cross-canadian.inc: add INSANE_SKIP_ to avoid build warning
systemd: fix segfault on shutdown
nfs-utils: bugfix: adjust name of statd service unit
busybox_git: Fix SRCREV
busybox-1.23: Backport patch to fix 

Re: [yocto] Yocto Project Status WW22

[akuster]

On 05/27/2016 08:14 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.2 M1
> 
> Next Deadline: YP 2.2 cut off: June 13, 2016
> 
> 
> SWAT team rotation: Tracy -> Alejandro
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> 
> Key Status/Updates:
> 
> *Python3 is nearly ready to merge, 4 oe-selftest issues remain and 
> some toaster issues. There are likely others but the tests aren't showing 
> them and I'm not getting bug reports so the code will merge once the known 
> issues are addressed.
> 
> *gcc6 is about ready to merge, just one issue, linux-yocto-4.1 on 
> beaglebone to address
> 
> *Patches are being held up as some large series (python3, gcc6) are 
> needing testing and we're trying to get these done before moving to other 
> patches. We're aware there is a backlog building again and will work through 
> that as time and autobuilder resources allow.
> 
> *RP is out of contact Fri-Mon due to vacation/national holidays so 
> this may delay some final merges, mut is continuing development. RP typically 
> does a lot of testing over weekends to make the most of the autobuilder but 
> this won't happen and hence there will be a slow down.
> 

If the autobuilder is going to idle this weekend, can we build
krogoth-next from

git://git.yoctoproject.org/poky-contrib akuster/krogoth-next

- armin


> *YP 1.8.2 passed QA and is due for release shortly.
> 
> *YP 2.0.2 is in QA and will be out next week.
> 
> 
> Key YP 2.2 Dates:
> 
> *YP 2.2 M1 cut off would be: 6/13/16
> 
> *YP 2.2 M1 release would be: 6/24/16
> 
> *YP 2.2 M2 cut off would be: 7/18/16
> 
> *YP 2.2 M2 release would be: 7/29/16
> 
> *YP 2.2 M3 cut off would be: 8/29/16
> 
> *YP 2.2 M3 release would be: 9/9/16
> 
> *YP 2.2 M4 cut off would be: 10/3/16
> 
> *YP 2.2 M4 release would be: 10/28/16
> 
> 
> Tracking Metrics:
> 
> WDD 2574 (last week 2626)
> 
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> 
> Key Status Links for YP:
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
> 
> [If anyone has suggestions for other information you'd like to see on this 
> weekly status update, let us know!]
> 
> Thanks,
> 
> Stephen K. Jolley
> Yocto Project Program Manager
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
> *   Work Telephone:(503) 712-0534
> *Cell:   (208) 244-4460
> * Email:stephen.k.jol...@intel.com
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-security][PATCH] Use bb.utils.contains instead of base_contains because it is deprecated

[akuster]

On 05/25/2016 01:24 AM, Thomas Perrot wrote:
> Signed-off-by: Thomas Perrot 
> ---
>  recipes-kernel/linux/linux-yocto_4.1.bbappend | 8 

merged.

>  recipes-security/clamav/clamav_0.99.1.bb  | 2 +-
>  recipes-security/sssd/sssd_1.13.3.bb  | 2 +-
>  recipes-tpm/trousers/trousers_0.3.13.bb   | 4 ++--

these last three are fixed in master-next. I just merged over master-next.

Thanks,

- armin
>  4 files changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-yocto_4.1.bbappend 
> b/recipes-kernel/linux/linux-yocto_4.1.bbappend
> index 1043d5c..dc90e31 100644
> --- a/recipes-kernel/linux/linux-yocto_4.1.bbappend
> +++ b/recipes-kernel/linux/linux-yocto_4.1.bbappend
> @@ -2,8 +2,8 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-4.1:"
>  
>  # Tomoyo kernel support
>  SRC_URI += "\
> - ${@base_contains('DISTRO_FEATURES', 'tomoyo', ' 
> file://ccs-tools-yocto.4.1.patch', '', d)} \
> - ${@base_contains('DISTRO_FEATURES', 'tomoyo', ' 
> file://ccs-tools-yocto_security.patch', '', d)} \
> - ${@base_contains('DISTRO_FEATURES', 'tomoyo', ' file://tomoyo.cfg', '', 
> d)} \
> - ${@base_contains('DISTRO_FEATURES', 'tomoyo', ' file://tomoyo.scc', '', 
> d)} \
> + ${@bb.utils.contains('DISTRO_FEATURES', 'tomoyo', ' 
> file://ccs-tools-yocto.4.1.patch', '', d)} \
> + ${@bb.utils.contains('DISTRO_FEATURES', 'tomoyo', ' 
> file://ccs-tools-yocto_security.patch', '', d)} \
> + ${@bb.utils.contains('DISTRO_FEATURES', 'tomoyo', ' file://tomoyo.cfg', 
> '', d)} \
> + ${@bb.utils.contains('DISTRO_FEATURES', 'tomoyo', ' file://tomoyo.scc', 
> '', d)} \
>   "
> diff --git a/recipes-security/clamav/clamav_0.99.1.bb 
> b/recipes-security/clamav/clamav_0.99.1.bb
> index edccc78..461015f 100644
> --- a/recipes-security/clamav/clamav_0.99.1.bb
> +++ b/recipes-security/clamav/clamav_0.99.1.bb
> @@ -30,7 +30,7 @@ GID = "clamav"
>  
>  PACKAGECONFIG ?= "ncurses openssl bz2 zlib "
>  PACKAGECONFIG += " ${@bb.utils.contains("DISTRO_FEATURES", "ipv6", "ipv6", 
> "", d)}"
> -PACKAGECONFIG += "${@base_contains('DISTRO_FEATURES', 'systemd', 'systemd', 
> '', d)}"
> +PACKAGECONFIG += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 
> 'systemd', '', d)}"
>  PACKAGECONFIG[pcre] = "--with-pcre=${STAGING_LIBDIR},  --without-pcre, 
> libpcre"
>  PACKAGECONFIG[xml] = "--with-xml=${STAGING_LIBDIR}/.., --with-xml=no, 
> libxml2,"
>  PACKAGECONFIG[json] = "--with-libjson=${STAGING_LIBDIR}, --without-libjson, 
> json,"
> diff --git a/recipes-security/sssd/sssd_1.13.3.bb 
> b/recipes-security/sssd/sssd_1.13.3.bb
> index d538af3..fd4f2a2 100644
> --- a/recipes-security/sssd/sssd_1.13.3.bb
> +++ b/recipes-security/sssd/sssd_1.13.3.bb
> @@ -24,7 +24,7 @@ CACHED_CONFIGUREVARS = 
> "ac_cv_member_struct_ldap_conncb_lc_arg=no \
>  "
>  
>  PACKAGECONFIG ?="nss"
> -PACKAGECONFIG += "${@base_contains('DISTRO_FEATURES', 'selinux', 'selinux', 
> '', d)}"
> +PACKAGECONFIG += "${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 
> 'selinux', '', d)}"
>  
>  PACKAGECONFIG[ssh] = "--with-ssh, --with-ssh=no, "
>  PACKAGECONFIG[samba] = "--with-samba, --with-samba=no, samba"
> diff --git a/recipes-tpm/trousers/trousers_0.3.13.bb 
> b/recipes-tpm/trousers/trousers_0.3.13.bb
> index 7001788..e274972 100644
> --- a/recipes-tpm/trousers/trousers_0.3.13.bb
> +++ b/recipes-tpm/trousers/trousers_0.3.13.bb
> @@ -17,7 +17,7 @@ SRC_URI[md5sum] = "ad508f97b406f6e48cd90e85d78e7ca8"
>  SRC_URI[sha256sum] = 
> "bb908e4a3c88a17b247a4fc8e0fff3419d8a13170fe7bdfbe0e2c5c082a276d3"
>  
>  inherit autotools pkgconfig useradd update-rc.d
> -inherit 
> ${@base_contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', d)}
> +inherit 
> ${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', 
> d)}
>  
>  PACKAGECONFIG ?= "gmp "
>  PACKAGECONFIG[gmp] = "--with-gmp, --with-gmp=no, gmp"
> @@ -33,7 +33,7 @@ do_install_append() {
>  install -d ${D}${sysconfdir}/udev/rules.d
>  install -m 0644 ${WORKDIR}/trousers-udev.rules 
> ${D}${sysconfdir}/udev/rules.d/45-trousers.rules
>  
> -if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then
> +if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; 
> then
>  install -d ${D}${systemd_unitdir}/system
>  install -m 0644 ${WORKDIR}/tcsd.service 
> ${D}${systemd_unitdir}/system/
>  sed -i -e 's#@SBINDIR@#${sbindir}#g' 
> ${D}${systemd_unitdir}/system/tcsd.service
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] any pointers to a yocto-based image to use as a live install utility?

[akuster]

Robert,


On 05/25/2016 03:18 AM, Robert P. J. Day wrote:
> 
>   specifically in the context of powerpc systems, are there any
> suggestions for an image that could be used to boot an older powerpc
> system, running completely out of ram, and using that as an install
> utility which would then be responsible for detecting/formatting a
> hard drive, creating/formatting filesystems, downloading/installing
> the OS, post-install configuration and so on?

This sounds like an installer MV has and that I have been given approval
to release (just haven’t had the time to submit it).  Its X86 centric ie
uses grub and support efi

It boots up from an iso image and runs a ncurses based interface that
allows you to select HD, create partitions and filesystem types. It will
install what ever image you built. It creates grub conf and installs it.
The installer bit is written in python.

> 
>   i realize that's a spectacularly imprecise request -- in a general
> sense, it involves just starting with a regular image, then adding
> utilities that run around doing all of the above, but if there's
> anything that already takes one most of the way there, that'd be
> great.
> 

Does this sound like something you are thing about?

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

Re: [yocto] https://layers.openembedded.org/

[akuster]

On 5/15/16 3:22 PM, Paul Eggleton wrote:
> On Sun, 15 May 2016 14:17:26 akuster808 wrote:
>> Is the layer index down?
> 
> It has been yes - Michael has been looking into it and I believe he's located 
> the problem - for now it's still unavailable though I expect it will be back 
> imminently.

Working now. thanks.

 -armin
> 
> Cheers,
> Paul
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bugzilla.yoctoproject.org policy for bugs against multiple releases

[akuster]

On 04/18/2016 03:26 AM, Burton, Ross wrote:
> Hi,
> 
> At the moment we don't really have a policy for oe-core bugs in
> bugzilla.yoctoproject.org that apply to multiple releases, for example
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=9400.  This is a CVE bug
> that should be fixed in all supported branches, and indeed Sona has sent
> patches for Fido/Dizzy/Jethro/master.  Of course now we've got to track
> where these patches are in the submission process and ensure that we don't
> drop any of these, 

If the worry is about patches being left out than every change requires
a bug number and needs to be managed to ensure a clone is created for
any branch affected by the fix.

but bugzilla only has a single target milestone for each
> bug.
> 
> I propose that for bugs such as this
 we file a bug report for master and
> then clone it (there's a Clone This Bug button at the bottom) for each
> stable release that is affected.

This also means maintainers who cherry-pick fixes from another branch
would have to amend the commit to change the bug number. Do we really
want to add to the workload of the maintainers?

  Then each bug can have it's own target
> milestone set and we can be sure that the patches don't get left out of
> being merged and that QA can effectively verify each branch.
> 
> Any objection or feedback? 

This is why I stopped opening Yocto Bugs. I would rather spend my time
fixing things than managing them.

- Armin

(the first person to suggest moving to Jira gets
> to manually review all CVEs from CVE-1999-0001 onwards are fixed in
> krogoth).

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

Re: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Feb. 2, 2016 8:00 AM US Pacific Time

[akuster]

On 02/02/2016 08:19 AM, Jolley, Stephen K wrote:
> Attendees: Armin, Stephen, Joshua, Belen, Sona, Richard, Ross,
> 
> 
> 
> AR: Armin - Develop a bugzilla enhancement request to handle patches for 
> older stable branches.

bug is 9037

- armin
> 
> 
> 
> Agenda:
> 
> 
> 
> * Opens collection - 5 min (Stephen)
> 
> * Yocto Project status - 5 min (Stephen/team)
> 
> YP 2.1 M2 rc1 is in QA.  Should be out soon.
> 
> YP 2.0.1 rc2 came out of QA, but because we had CVE's after it went in, and a 
> number of issues.  We will do an rc3 as soon as we can get fixes ready.
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features
> 
> * Opens - 10 min
> 
> Armin - Discussed change process for patches for older stable branches.
> 
> Richard - Python expansion changes are being discussed on the architecture 
> list.  Theses might break something.  But after the changes are made we will 
> fix them. Overall we think this will fix other important issues.
> 
> Richard - Change are being discussed to make files options.  It might also 
> break something, but it fixes a number of long term issues.
> 
> * Team Sharing - 10 min - Nothing.
> 
> 
> 
> 
> Thanks,
> 
> Stephen K. Jolley
> Yocto Project Program Manager
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
> *   Work Telephone:  (503) 712-0534
> *Cell:(208) 244-4460
> * Email: stephen.k.jol...@intel.com
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Glibc 2.24 _might_ require minimum kernel version 3.2

[akuster]

On 01/31/2016 09:41 AM, Khem Raj wrote:
> Hi
> 
> This is FYI, as I have sent a RFT for glibc 2.24, there might be another 
> change
> coming which is under discussion on glibc mailing lists which is on
> supported minimum
> kernel version bump to 3.2 since 2.6.32 will be EOLed this summer [1]
> 
> If anyone is planning on using upcoming yocto/OE release and sticking
> to kernels older than  3.2 then please plan for upgrading your kernel.

Nope.

- armin
> 
> Thanks
> -Khem
> 
> [1] - https://sourceware.org/ml/libc-alpha/2016-01/msg00885.html
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Embedded Linux Conference, YP DevDay, and OEDAM

[akuster]

On 01/27/2016 10:15 AM, Jeff Osier-Mixon wrote:
> If you are planning to attend the Embedded Linux Conference in San
> Diego this April, I wanted to let you know about the Yocto Project
> Developer Day that the team is planning. This will be similar to
> previous DevDays, with hands-on training in both introductory and
> advanced tracks. The day will happen just after ELC, on April 7 at the
> Marriott in downtown San Diego, just across from the ELC venue. We'll
> have more details posted later this week.
> 
> The project is also a sponsor for the event and we will have a booth.
> If you have something cool that you have been working on and would
> like to show it off in the booth during the conference, let me know
> and we'll see what we can do to make some space for your project.

I will be bring at least one demo. Not sure if its cool.

> 
> For those also in the OpenEmbedded community, there will be an OE
> developer's meeting and working session on Friday, April 8. This is a
> working session for OE members (not an educational session, sorry!)
> and space is limited, so if you plan to attend, please let me know so
> I can plan space accordingly.

I will be there. I take it there will be a wiki sigh up like before?

- armin
> 
> thanks!
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ipv6 testing

[akuster]

Larry,

On 01/15/2016 10:52 AM, Larry Goss wrote:
> Hi,
> 
> Does Yocto do any IPv6 conformance testing?

AFAIK, the project does not preform conformance testing.

regards,
Armin
> 
> Thanks,
> 
> Larry Goss
> Sr. Field Applications Engineer
> Enea North America
> Email: larry.g...@enea.com
> Phone: (603) 475-1087
> 
> http://www.enea.com/
> 
> 
> This message, including attachments, is CONFIDENTIAL. It may also be 
> privileged or otherwise protected by law. If you received this email by 
> mistake please let us know by reply and then delete it from your system; you 
> should not copy it or disclose its contents to anyone. All messages sent to 
> and from Enea may be monitored to ensure compliance with internal policies 
> and to protect our business. Emails are not secure and cannot be guaranteed 
> to be error free as they can be intercepted, amended, lost or destroyed, or 
> contain viruses. The sender therefore does not accept liability for any 
> errors or omissions in the contents of this message, which arise as a result 
> of e-mail transmission. Anyone who communicates with us by email accepts 
> these risks.
> 
> 
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Package naming "exceptions" in Yocto

[akuster]

On 01/13/2016 11:43 PM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 

Since you ask about "Yocto" naming in the Poky distribution I have the
following comments:

The Reference to "Yocto" should only be in terms of the project. The
Soures you refer to in support of the "Poky" distro.
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check. 

The Yocto project should not have any specific packages. Its "Poky". In
fact in the last OEDAME it was decided to rename the meta-yocto* layers
to meta-poky*.  I was hoping would have been changed by now.

People are saying "Yocto linux" which is wrong. Its the Yocto Project
which has a test distro named "Poky".

Just ask Phil B.


> 
>  
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can. 

There may be a need to have a mapping for upstream names to packages
named within OE. They may not all be 1:1. Or in the case of someone
outside the project runs this in there distro they can.

regards,
Armin

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

Re: [yocto] [meta-security][PATCH] Remove recipe for the kernel 3.14 from master branch, to fix a build error. ERROR: No recipes available for: meta-security/recipes-kernel/linux/linux-yocto_3.14.bbap

[akuster]

Thomas,

thanks.

On 01/04/2016 10:31 AM, Thomas Perrot wrote:
> Signed-off-by: Thomas Perrot 
> ---
>  recipes-kernel/linux/linux-yocto_3.14.bbappend | 4 
>  1 file changed, 4 deletions(-)
>  delete mode 100644 recipes-kernel/linux/linux-yocto_3.14.bbappend
> 
> diff --git a/recipes-kernel/linux/linux-yocto_3.14.bbappend 
> b/recipes-kernel/linux/linux-yocto_3.14.bbappend
> deleted file mode 100644
> index b46419c..000
> --- a/recipes-kernel/linux/linux-yocto_3.14.bbappend
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> -
> -# Tomoyo kernel support
> -SRC_URI += "${@base_contains('DISTRO_FEATURES', 'tomoyo', ' 
> file://tomoyo.cfg', '', d)}"
> 

merged to master next

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

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

[akuster]

On 11/09/2015 05:42 PM, Robert Yang wrote:
> 
> I think that the codename is not fido for 1.7 ?

its Dizzy.

- armin
> 
> // Robert
> 
> On 11/10/2015 03:45 AM, Flanagan, Elizabeth wrote:
>> Hello,
>>
>> The latest release of the Yocto Project 1.7.3 (dizzy-12.0.3) is now
>> available
>> for download at:
>>
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>>
>> A gpg signed version of these release notes is available at:
>>
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/RELEASENOTES
>>
>> Full pass test report is available at:
>>
>> https://wiki.yoctoproject.org/wiki/Ww41_-_2015-10-08_-_Full_Pass_1.7.3.rc1
>>
>>
>> Thanks go out to everyone for all their hard work during this release!
>>
>> Sincerely,
>>
>> Elizabeth Flanagan
>> Yocto Project
>> Build and Release
>>
>> -
>> yocto-1.7.3 Errata
>>
>> Release Name:  eclipse-poky-kepler-12.0.3
>> Branch: kepler/dizzy
>> Tag: luna/dizzy-12.0.3
>> Hash:  cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
>> md5: e7eca889b7a6efffa815581fee50b657 
>> eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
>>
>>
>> Release Name:  eclipse-poky-luna-12.0.3
>> Branch: luna/dizzy
>> Tag: luna/dizzy-12.0.3
>> Hash: 45aa5c77523bdf051d548fff4305382942db2ebb
>> md5: ebcf90e66bae33519387f299ca0c908a 
>> eclipse-poky-luna-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2
>>
>>
>> Release Name:  meta-qt3-12.0.3
>> Branch: dizzy
>> Tag: dizzy-12.0.3
>> Hash:  3016129d90b7ac8517a5227d819f10ad417b5b45
>> md5: 77f5c7cb8b3523862086dd9e6271b79d  meta-qt3-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2
>>
>>
>> Release Name:  poky-12.0.3
>> Branch: dizzy
>> Tag: dizzy-12.0.3
>> Hash:  b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94
>> md5: 7d3196798cb5e78e6b7f89e03edcf9e7  poky-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>>
>> ---
>> Security Fixes
>> ---
>> bind: CVE-2015-1349 CVE-2015-4620 CVE-2015-5722
>> icu: CVE-2014-8146-CVE-2014-8147
>> gnutls: CVE-2015-3308
>> qemu-slirp: CVE-2014-3640
>> qemu-vnc: CVE-2014-7815
>> qemu: CVE-2014-7840
>> bind9.9.5: CVE-2015-5477
>> libxml2: Security Advisory - libxml2 - CVE-2015-1819
>> rpm: Fix CVE-2013-6435
>> rpm: Fix CVE-2014-8118
>> dbus: CVE-2015-0245: prevent forged ActivationFailure
>> unzip: fix four CVE defects
>> unzip: Security Advisory -CVE-2014-9636 and CVE-2015-1315
>> gpgme: fix CVE-2014-3564
>> glibc: CVE-2015-1781: resolv/nss_dns/dns-host.c buffer overflow
>> qemu: fix CVE-2015-3456
>> ppp: Security Advisory - CVE-2015-3310
>> libsndfile: Security Advisory - libsndfile - CVE-2014-9496
>>
>> ---
>> Fixes
>> ---
>> build-appliance-image: Update to dizzy head revision
>> poky.conf: Bump version for 1.7.3 dizzy release
>> sstate: run recipe-provided hooks outside of ${B}
>> oprofileui: Use inherit gettext
>> rootfs.py: show intercept script output in log.do_rootfs
>> postinst_intercept: allow to pass variables with spaces
>> rootfs.py: Allow to override postinst-intercepts location
>> base.bbclass: Note when including pn with INCOMPATIBLE_LICENSES
>> autotools.bbclass: mkdir ${B} -> mkdir -p ${B}
>> perf: mkdir ${B} -> mkdir -p ${B}
>> bitbake: prserv/serv: Improve exit handling
>> bitbake: bitbake: cooker: properly fix bitbake.lock handling
>> bitbake: runqueue: Add message to explain the problem if diffsigs
>> multiple tasks don't exist
>> oeqa/selftest: fix test_incremental_image_generation for changes in
>> log output
>> qemurunner: Improves checking for server and target IPs on qemus
>> parameters
>> oeqa/utils/qemurunner: fix logging
>> oeqa/QemuRunner: don't use bb for logging
>> license.bbclass: fix unexpected operator for LICENSE values with space
>> license_class: fix license.manifest shows LICENSE field differently to
>> recipe
>> connman-conf: fix SRC_URI_append
>> sstate: Use SSTATE_DIR for FILESPATH
>> gnome: move introspection options to gnomebase
>> tzdata, tzcode-native: drop older versions 2014h, 2015b
>> grub-efi: Add backslash lost from previous commit
>> grub-efi: Use the backport patch from grub
>> license_class: Fix choose_lic_set into incompatible license
>> dpkg: Fix tarfix.patch
>> dpkg: Fix for 

Re: [yocto] RFC: Yocto LTS?

[akuster]

On 10/15/15 8:49 AM, Philip Balister wrote:
> On 10/14/2015 12:26 PM, Chris Simmonds wrote:
>>
>> On 14/10/15 17:27, Mark Hatle wrote:
>>> On 10/14/15 8:28 AM, Chris Simmonds wrote:
 Hi,

 Is there a statement about the period of support for a Yocto release?
 Looking through the updates, it seems that 12 months is typical, a was
 the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
 declaration anywhere that this is the expected norm.

 Leading on from that, is 12 months enough? Most projects have a
 lifecycle that is much longer. Is there an argument for an LTS Yocto
 release, maybe once a year? If not, what is the recommended way for a
 project developer to keep a distribution up to date in the light of the
 several well-publicised security flaws that have been discovered over
 the last year or so and the new ones that will no doubt be discovered in
 the future?
>>>
>>> https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_overall_support_plan_for_the_Yocto_Project.3F
>>>
>>> =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. 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.
>>>
>>>
>>>
>>> Effectively this means that support is on the last two releases.  Releases 
>>> are
>>> typically released every 6 months.  After that point it is usually 
>>> supported by
>>> OSVs, or others that offer commercial services.  In the past we have done a 
>>> few
>>> very late security fixes past the 'last two releases' point, however that 
>>> has
>>> been for unique situations.
>>>
>>> You should consider keeping current with the Yocto Project releases or 
>>> consider
>>> commercial support if you need more then an approx 12 - 18 month support 
>>> cycle.
>>>
>>> --Mark
>>>
>>
>> Thanks, that is all clear now.
> 
> We wouldn't be opposed to a group of people supporting a release for
> longer. But they would need to provide the people to do the work. LTS
> work is hard.

Not to mention keeping build infrastructure setup, copies of supported
OS working, QA and Target machines working. As an OSV, its not uncommon
to support a distro for 10 or more years.

- Armin
> 
> Philip
> 
>>
>> Chris
>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Status WW40

[akuster]

Stephen,

Isn't the next meeting next Tuesday? Will there be a meeting since ELCE
is in full swing next week?

- armin

On 10/02/2015 08:26 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.0 Final (rc1 build in QA)
> Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015
> 
> SWAT team rotation: Ross -> Cristian
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> Key Status/Updates:
> 
>   *   Two failures were encountered during the rc1 build. There is fix queued 
> for the wic selftest issue, the other -lsb kernel module test sanity failures 
> are still being investigated.
>   *   Many fixes for issues were merged into master including some of the 
> 'random' failures, thanks to all who've worked on them!
>   *   The rc1 build is being put through tests by QA
>   *   Prelink looks like it may be broken in release for non FHS/LSB library 
> setups
>   *   A successful fido 1.8.1 point release build was queued for QA, 2.0 is 
> taking priority
>   *   Now the sstate issue is fixed, a 1.7.3 build will also be made soon as 
> autobuilder time is available.
>   *   Reminder:
>  *   We have renamed YP 1.9 to YP 2.0.
>  *   The current version that is in development will launch as YP 2.0 in 
> October, 2015.
>  *   The release name for YP 2.0 is 'jethro'.
> 
> Key YP 1.9/2.0 Dates:
> YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA)
> YP 2.0 final Release Target: Before Oct. 30, 2015
> 
> Key Status Links for YP:
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status
> https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule
> https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features
> 
> Tracking Metrics:
> WDD 2170 (last week 2165 )
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> [If anyone has suggestions for other information you'd like to see on this 
> weekly status update, let us know!]
> Thanks,
> 
> Stephen K. Jolley
> Yocto Project Program Manager
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
> *   Work Telephone:  (503) 712-0534
> *Cell:(208) 244-4460
> * Email: stephen.k.jol...@intel.com
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto compliance

[akuster]

Hello,

shouldn't we add '1.8' as a check box?

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

Re: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, May 5, 2015 8:00 AM US Pacific Time

[akuster]

Stephen,

For the next agenda or reply.

1) Yocto version after 1.9. is it 1.10 or 2.0?

2) I heard at OEDAM that there is a bug triage meeting. Is there 
information on this somewhere?


regards,
Armin.


On 05/05/2015 08:13 AM, Jolley, Stephen K wrote:

Attendees: Stephen, Armin, Jussi, Sona, Michael, Mark, Richard, Denys,
Alex V., Saul, Cristian,

*AR: Stephen – Insure Benjamin knows he has SWAT.*

Agenda:

* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features

·YP 1.9 Planning is still in progress; but mostly done.

·YP 1.9 M1 Cut off is June 23, 2015.

·YP 1.7.2 rc3 should be out of QA by EOW.

·Meta-Intel should start QA as soon as 1.7.2 is done.

·YP 1.6.3 should start as soon as meta-intel comes out of QA.

* SWAT team rotation: Randy - Benjamin

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

* Opens - 10 min

* Team Sharing - 10 min

Richard – Due to new items being added and improvements made in YP,
build performance is slowing increasing.  If anyone has ideas on how to
improve on this, it would be welcome.

Cristian – Switch to bluez 5 from bluez 4 might cause some errors.
Please report anything that becomes an issue.

Thanks,

*/Stephen K. Jolley/**//*

*Yocto Project Program Manager*

*INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *

(*Work Telephone*: (503) 712-0534

(*Cell*: (208) 244-4460

* *Email*:_stephen.k.jolley@intel.com_




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

Re: [yocto] OpenEmbedded Developer America's Meeting

[akuster]

Hello Folks,

OEDAM is nearing. If you have not signed up, please do so. It will help 
me with head count for badges.


We also need more subject matter the Agenda.  If you have any topics or 
ideas, please submit them.


kind regards,
Armin

On 02/10/2015 12:27 PM, Philip Balister wrote:

We've scheduled a meeting in San Jose at a Monte Vista facility for
March 27-28. This is after ELC (also in San Jose). There is a Yocto
Project developer Day the day after ELC.

I've made a page on the wiki to start collecting information:

http://openembedded.org/wiki/OEDAM_2015

To get an idea of what we cover, see the page from the prior year:

http://openembedded.org/wiki/OEDAM_2014

I apologize for the late notice. There were issues that led to a delay
with dates due to the YP Dev day.

Philip


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

Re: [yocto] [Question] How to walkaround this warning

[akuster]

I think it means the package would prefer to use 'UID' = tss and needs 
something like inheriting useradd + setup, otherwise it defaults to root.


I will take a look at the recipe since I did the last update and did 
notice that message.


- armin

On 02/16/2015 09:07 PM, Bian, Naimeng wrote:

Hi folks

I built my image and got the following warning message in do_rootfs.
--
Output from btrfs-tools-3.14.2+git0+24cf4d8c3e-r0@core2_64:
warning: user tss does not exist - using root
warning: group pulse does not exist - using root
--

My poky is 1.7.1 as below
--
DISTRO = poky
DISTRO_NAME = Poky (Yocto Project Reference Distro)
DISTRO_VERSION = 1.7.1
DISTRO_CODENAME = dizzy
-

Any suggestion, thanks.

Cheers
  Bian


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

Re: [yocto] OpenEmbedded Developer America's Meeting

[akuster]

On 02/10/2015 12:47 PM, Denys Dmytriyenko wrote:

On Tue, Feb 10, 2015 at 03:27:23PM -0500, Philip Balister wrote:

We've scheduled a meeting in San Jose at a Monte Vista facility for


Correction, it's MontaVista with an 'a':
http://en.wikipedia.org/wiki/MontaVista

Do you have an address of said facility?



 2315 North 1st Street, San Jose, CA 95131

 In the Farm House out back. Behind the two high-rise buildings.

- Armin


March 27-28. This is after ELC (also in San Jose). There is a Yocto
Project developer Day the day after ELC.

I've made a page on the wiki to start collecting information:

http://openembedded.org/wiki/OEDAM_2015

To get an idea of what we cover, see the page from the prior year:

http://openembedded.org/wiki/OEDAM_2014

I apologize for the late notice. There were issues that led to a delay
with dates due to the YP Dev day.

Philip
--
___
Openembedded-members mailing list
openembedded-memb...@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-members

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

Re: [yocto] [meta-selinux][PATCH] ustr: fix typo in SRC_URI

[akuster]

Phillip,

thanks.

- armin

On 02/04/2015 10:17 AM, Philip Tricca wrote:

Hello Armin,

I've submitted a very similar patch a few days earlier. This was bundled
up into a larger series that *should* get meta-selinux master building
again. See:
https://lists.yoctoproject.org/pipermail/yocto/2015-January/023314.html

Philip

On 01/30/2015 10:02 PM, Armin Kuster wrote:

From: Armin Kuster akus...@mvista.com

This fixes
ERROR: Fetcher failure: Fetch command failed with exit code 8, output:
http://www.and.org/ustr/$%7BBPV%7D/ustr-1.0.4.tar.bz2:
2015-01-30 18:26:38 ERROR 404: Not Found.

Changed BPV to PV

Signed-off-by: Armin Kuster akus...@mvista.com
---
  recipes-extended/ustr/ustr_1.0.4.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-extended/ustr/ustr_1.0.4.bb 
b/recipes-extended/ustr/ustr_1.0.4.bb
index a0a1e41..cdb78ad 100644
--- a/recipes-extended/ustr/ustr_1.0.4.bb
+++ b/recipes-extended/ustr/ustr_1.0.4.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = 
file://LICENSE;md5=c79c6e2ae13418d16d7dc82df960a1e7 \
file://LICENSE_MIT;md5=c61e779b782608472bd87593c3c3916f

  SRC_URI = \
-http://www.and.org/ustr/${BPV}/${BPN}-${PV}.tar.bz2 \
+http://www.and.org/ustr/${PV}/${BPN}-${PV}.tar.bz2 \
  file://ustr-makefile-fix.patch;patch=1 \
  file://ustr-fix__va_copy-not-defined.patch;patch=2 \
  file://ustr-c99-inline.patch;patch=3




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

Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade

[akuster]

Khem,

If I knew what testing' entailed I would through some time at this.

- Armin

On 02/02/2015 02:02 AM, Khem Raj wrote:

Hi All

I have put together upgrade to gcc 4.9.2 as well as glibc 2.21 (
upcoming ) on  a contrib branch ( top 2 patches) its has not got much
testing besides x86 qemu thus far.

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-glibc-upgrade

I would like to request some help in testing these out in your
respective environments and please report any issues you see so we can
start sorting them out at earlier and making its way into OE-Core.

Thanks for your help

-Khem


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

Re: [yocto] HEADSUP - CVE 2015-023 remote code execution in glibc

[akuster]

Alexandr,


On 01/28/2015 03:17 AM, Damian, Alexandru wrote:

More details

http://www.openwall.com/lists/oss-security/2015/01/27/9

redhat bug and patch

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-0235

Do we need to open a bug to track this ?


 I am working on patches already. if you opened a bug, please send me 
the #.


- Armin



--
Alex Damian
Yocto Project
SSG / OTC



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

Re: [yocto] [OE-core] Package Upgrading for 1.8

[akuster]

On 10/30/2014 11:21 AM, Saul Wold wrote:


Folks,

Just a reminder now that master is open again for patches, now is a
great time to consider doing package Updates.  Based on some rough
estimates from 1.7 we did around 300 updates from 34 contributors, that
got us about 73% packages upgrades.

We currently have about 180 packages due to be updated based on the
Package Reporting from this last week, about 65 of those where not
updated in 1.7 so should be given some priority (see attached file),
there are also 10 that need maintainers, let me know if you are
interested in any of them.


I will take pinentry.

- Armin


Here are the stats from 1.7 on who has upgraded packages (I guess I
don't have enough to do!).  Thanks to everyone who contributed package
updates.

  61 Saul Wold
  43 Cristian Iorga
  25 Ross Burton
  23 Bruce Ashfield
  15 Armin Kuster
  14 Richard Purdie
  12 Laurentiu Palcu
  11 Paul Eggleton
   9 Hongxu Jia
   9 Cristiana Voicu
   9 Chen Qi
   8 Valentin Popa
   7 Chong Lu
   7 Carlos Rafael Giani
   6 Khem Raj
   5 Tim Orling
   4 Roxana Ciobanu
   4 Robert Yang
   4 Marko Lindqvist
   4 Mark Hatle
   3 Paul Barker
   3 Maxin B. John
   2 Yasir-Khan
   2 Nicolas Dechesne
   2 Fathi Boudra
   1 Ricardo Neri
   1 Peter Seebach
   1 Peter Kjellerstedt
   1 Martin Jansa
   1 Jackie Huang
   1 Darren Hart
   1 Ciobanu Roxana
   1 Chunrong Guo
   1 Andreas Müller





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

Re: [yocto] [OE-core] Carrier Grade layer proposal

[akuster]

Bruce,

So how / where do I start on the kernel part?

- Armin

On 07/22/2014 08:58 AM, Bruce Ashfield wrote:

On 14-07-22 11:54 AM, akuster wrote:

Alexandru,

Regarding  a few packages in category CD.

I have latest samhain building as well as grsecurity (pax patches
applied against 3.14.12) in a branch in my meta-security tree.  I have a
bit more testing to do before I was going to post them.


And on this note, we should consider the kernel parts and see if getting
them into a common location is a good idea.

We already have the linux-yocto tree, and it tracks LTSI, has CVE and
-stable tracking, and is maintained to support the set of reference
boards.

Creating yet more reference kernel trees doesn't help our goal of
fewer trees and a discrete set of kernel versions.

Just something to consider.

Cheers,

Bruce



grsecurity and samhain aren't CGL specific and they maybe belong in a
more generalize layer? just a thought.

regards,
Armin


On 07/22/2014 03:52 AM, Alexandru Vaduva wrote:

Hello Joe,

Here at Enea we are preparing the steps needed for publishing the
layer on the open embedded meta layers initiative:
http://layers.openembedded.org/layerindex/branch/master/layers/
For this we started working at a web page that should contain all the
relevant information regarding meta-cgl. It will be available in a
couple of weeks. Until then the layer will be available internally and
the patches should
be submitted as the README states: on the eneali...@lists.enea.com
mailing list. We will try to make the switch to Open Embedded mailing
list as quick as possible.

Regarding the other B, C and D packages  that we will try to add into
the meta-cgl layer, I will post this information below, but keep in
mind that this information will also be available on the web page.
Category B packages:
- ifenslave
- evlog
- crash
- mipv6-daemon-umip
- openl2tp
Category CD packages:
- drbd
- grsecurity
- logcheck
- makedumpfile
- numactl
- ocfs2-tools
- pam_passwdqc
- samhain
- ltt-usertrace
- ftrace
The above lists correspond with only the P1 requirements that we try
to fulfill for the moment. If there are any questions and/or
suggestions regarding this CGL initialtive please address them to me
and I will try to offer a response in the
shortest time possible.


Thanks,
Alex

-Original Message-
From: Joe MacDonald [mailto:j...@deserted.net]
Sent: Monday, July 21, 2014 10:58 PM
To: Alexandru Vaduva
Cc: Jeff Osier-Mixon; yocto@yoctoproject.org
Subject: Re: [yocto] [OE-core] Carrier Grade layer proposal

Hey Alex,

I've been away from this for a bit but now I'm getting time to look at
it again and I was wondering if you had any deeper level of detail you
could share about the work going on in meta-cgl.  Obviously since this
is a new registration and one that will look rather different from all
of the other CGL registrations currently, those of us in the CGL
workgroup were quite interested to see this happen.  Personally I'm
also interested in this since it's the kind of thing I've been doing
for a long time now and if I can, I'd like to help out.  In
particular, if you've got a list of, say, the category B+ items, that
might be something I can do that will be independent of your work on
the more active cat-A stuff.  OTOH, cat-A is easy to work on since
those are the items I saw when I was working with meta-cgl a month or
so back.  I know you guys are focused on your part of it, but if you
had sort of a here's how to help us guide, that'd be awesome.

Also, I probably missed it, but is the intent to use either the yocto
list or the oe list for all meta-cgl discussions, or do you have a
dedicated list we can sign up for?  I see you have guidance for
sending submissions to meta-cgl, but is that a list that's open to the
community, or is it an internal alias / distribution list for Enea?

Thanks,
-J.


On Mon, Jul 7, 2014 at 2:43 PM, Alexandru Vaduva
alexandru.vad...@enea.com wrote:

Hello Jeff,

The errors are package related.
Meta-cgl can be seen as a non BSP specific layer (it can be viewed as
the LSB from poky).
I already started fixing a number, of the already existing errors and
the patches will be added upstream after proper testing.
I will continue the bug fixing and package integration (into the
core-image-cgl image) process and after that is finished I will
continue with the Category B packages.

I will also try to keep you guys informed about the latest updates,
mainly on the YPTM, but for those who cannot wait that much, there is
the Git repository with which they can interact:
http://git.enea.com/git/?p=linux/meta-cgl.git;a=summary


Have a good day,
Alex


-Original Message-
From: jefro@gmail.com [mailto:jefro@gmail.com] On Behalf Of
Jeff Osier-Mixon
Sent: Monday, July 07, 2014 9:22 PM
To: Alexandru Vaduva
Subject: Re: [OE-core] Carrier Grade layer proposal

Thanks