[yocto] git.yoctoproject.org - Certificate expired

Hi all, the certificate installed under https://git.yoctoproject.org expired about one hour ago. My CI is not longer building. Anyone else experiencing the same problem? Is a new certificate going to be installed soon? Regards Georg -- ___ yocto mai

[yocto] Extract GPL sources

Hello I need to extract all *GPL* sources patched related to an image in order to publish them. I want to do it automatically, ie 'bitbake myimage -c extract-gpl-sources' Is there a mechanism to do that? If not do you have any idea how I can implement it? Thanks -- Fabien -- _

Re: [yocto] Extract GPL sources

Have a look at the archiver class. Ross On 7 August 2018 at 09:29, Fabien Lahoudere wrote: > Hello > > I need to extract all *GPL* sources patched related to an image in order to > publish them. > I want to do it automatically, ie 'bitbake myimage -c extract-gpl-sources' > Is there a mechanism

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

Am 2018-08-07 08:59, schrieb Georg Lutz: Hi all, the certificate installed under https://git.yoctoproject.org expired about one hour ago. My CI is not longer building. Anyone else experiencing the same problem? Is a new certificate going to be installed soon? OK, works again. New certifica

Re: [yocto] Extract GPL sources

Thanks Ross, I have an issue when using the archiver: local.conf: INHERIT += "archiver" ARCHIVER_MODE[src] = "patched" COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*' ERROR: gmp-native-6.1.2-r0 do_unpack_and_patch: Command Error: 'quilt --quiltrc /home/aragua/src/poky/build2/tmp/work/x86_64-linux/gmp-n

Re: [yocto] Extract GPL sources

I believe this is fixed in Pyro 2.3.4. Ross On 7 August 2018 at 11:15, Fabien Lahoudere wrote: > Thanks Ross, > > I have an issue when using the archiver: > > local.conf: > > INHERIT += "archiver" > ARCHIVER_MODE[src] = "patched" > COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*' > > ERROR: gmp-native-6

Re: [yocto] Extract GPL sources

Thanks Ross it works fine now. On Tue, 2018-08-07 at 11:38 +0100, Burton, Ross wrote: > I believe this is fixed in Pyro 2.3.4. > > Ross > > > On 7 August 2018 at 11:15, Fabien Lahoudere > wrote: > > Thanks Ross, > > > > I have an issue when using the archiver: > > > > local.conf: > > > > IN

[yocto] Yocto Project Status WW32’18

Current Dev Position: YP 2.6 M3. Next Deadline: YP 2.6 M2 Release Target was July 27, 2018 SWAT Team Rotation: · SWAT lead is currently: Armin · SWAT team rotation: Armin -> Maxin on Aug. 10, 2018 · SWAT team rotation: Maxin -> Chen on Aug. 17, 2018 · https://

[yocto] Minutes: Yocto Project Technical Team Meeting

Attendees: Stephen, Armin, Trevor, Richard, Nick, Ayman, Alex, Christopher, Scott, David, Alejandro, Ross, Denys, Joshua, Manju, Rich, Randy, YP Status: • YP 2.6 M2 is in QA. See https://wiki.yoctoproject.org/wiki/2.6_QA_Status. It is 99% complete and should complete this week. • Y

Re: [yocto] Non-deterministic build error in package gcc-source

> Anyhow I would still like to report the bug. Are there any other ways than using Bugzilla? No, bugzilla is the only bug tracking system for oe-core. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Non-deterministic build error in package gcc-source

We got about 60 stable builds with the archiver configured in source "original" and diff "1" mode as described in my last mail. So for us, this seems to solve the problem. Anyhow I would still like to report the bug. Are there any other ways than using Bugzilla? Kind regards, Erik ___

Re: [yocto] Yocto Project changes in progress

hi there, There have been various changes in the project recently which have caused concern for some users and contributors. I wanted to update everyone with the most recent developments. It is worth highlighting the recent news that: * The Yocto Project recently welcomed two new platinum members

Re: [yocto] How to pass compilation options from local.conf?

Hi, The manual is quite confusing: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-PACKAGECONFIG There are several methods to pass compilation options to a package from *local.conf*: PACKAGECONFIG[f1] or PACKAGECONFIG_append_pn-*recipename* or PACKAGECONFIG_CONFARGS