[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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[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 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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 to do that? > If not do you have any idea how I can implement it? > > Thanks > > -- > Fabien > -- > ___ > 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] 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 certificates seem to be installed. :-) Thanks Georg -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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-native/6.1.2-r0/archiver-work//recipe- sysroot-native/etc/quiltrc push' exited with 0 Output: /bin/sh: quilt: command not found ERROR: gmp-native-6.1.2-r0 do_unpack_and_patch: Function failed: patch_do_patch ERROR: Logfile of failure stored in: /home/aragua/src/poky/build2/tmp/work/x86_64-linux/gmp- native/6.1.2-r0/temp/log.do_unpack_and_patch.8027 ERROR: Task (virtual:native:/home/aragua/src/poky/meta/recipes- support/gmp/gmp_6.1.2.bb:do_unpack_and_patch) failed with exit code '1' I tried to drop native from COPYLEFT_RECIPE_TYPES without effect. Where can I add quilt-native dependency? For information I use pyro release. Is there any known bug for that release? Thanks On Tue, 2018-08-07 at 10:10 +0100, Burton, Ross wrote: > 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 to do that? > > If not do you have any idea how I can implement it? > > > > Thanks > > > > -- > > Fabien > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto -- Fabien -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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.1.2-r0 do_unpack_and_patch: Command Error: 'quilt > --quiltrc > /home/aragua/src/poky/build2/tmp/work/x86_64-linux/gmp-native/6.1.2-r0/archiver-work//recipe- > sysroot-native/etc/quiltrc push' exited with 0 Output: > /bin/sh: quilt: command not found > ERROR: gmp-native-6.1.2-r0 do_unpack_and_patch: Function failed: > patch_do_patch > ERROR: Logfile of failure stored in: > /home/aragua/src/poky/build2/tmp/work/x86_64-linux/gmp- > native/6.1.2-r0/temp/log.do_unpack_and_patch.8027 > ERROR: Task (virtual:native:/home/aragua/src/poky/meta/recipes- > support/gmp/gmp_6.1.2.bb:do_unpack_and_patch) failed with exit code '1' > > I tried to drop native from COPYLEFT_RECIPE_TYPES without effect. > > Where can I add quilt-native dependency? > > For information I use pyro release. Is there any known bug for that release? > > Thanks > > On Tue, 2018-08-07 at 10:10 +0100, Burton, Ross wrote: >> 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 to do that? >> > If not do you have any idea how I can implement it? >> > >> > Thanks >> > >> > -- >> > Fabien >> > -- >> > ___ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto > -- > Fabien -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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: > > > > 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-native/6.1.2-r0/archiver-work//recipe- > > sysroot-native/etc/quiltrc push' exited with 0 Output: > > /bin/sh: quilt: command not found > > ERROR: gmp-native-6.1.2-r0 do_unpack_and_patch: Function failed: > > patch_do_patch > > ERROR: Logfile of failure stored in: > > /home/aragua/src/poky/build2/tmp/work/x86_64-linux/gmp- > > native/6.1.2-r0/temp/log.do_unpack_and_patch.8027 > > ERROR: Task (virtual:native:/home/aragua/src/poky/meta/recipes- > > support/gmp/gmp_6.1.2.bb:do_unpack_and_patch) failed with exit code '1' > > > > I tried to drop native from COPYLEFT_RECIPE_TYPES without effect. > > > > Where can I add quilt-native dependency? > > > > For information I use pyro release. Is there any known bug for that release? > > > > Thanks > > > > On Tue, 2018-08-07 at 10:10 +0100, Burton, Ross wrote: > > > 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 to do that? > > > > If not do you have any idea how I can implement it? > > > > > > > > Thanks > > > > > > > > -- > > > > Fabien > > > > -- > > > > ___ > > > > yocto mailing list > > > > yocto@yoctoproject.org > > > > https://lists.yoctoproject.org/listinfo/yocto > > > > -- > > Fabien -- Fabien -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[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://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: · 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. · YP 2.5.1 is in QA. See https://wiki.yoctoproject.org/wiki/2.5_QA_Status. It just started and is 0% complete. · There was a nasty regression in do_package where hardlinks were not being preserved. This has been fixed and shows up clearly in the performance monitoring charts. A new automated test was added to detect this problem earlier in future. · We’re going to enable oe-selftest parallelism by default on the new autobuilder infrastructure as the critical race issues we had are fixed. · The multiconfig dependencies code merged. · The layerindex library code merged. · The sstate equivalency server work from Joshua/Garmin has review still pending. · The kernel-devsrc rework from Bruce/Windriver is pending patch resubmission. · With 2.5.1 built, stable release work is now focusing on the 2.4 (rocko) series. · There were cmake fixes and improvements to the SDK including the addition of new automated tests to ensure this doesn’t regress. Planned Releases for YP 2.6: · YP 2.6 M2 Build is in QA. · YP 2.6 M2 Release Target was July 27, 2018 · YP 2.6 M3 Build Target is Aug. 27, 2018 · YP 2.6 M3 Release Target is Sept. 7, 2018 · YP 2.6 M4 Build Target is Oct. 1, 2018 · YP 2.6 M4 Release Target is Oct. 26, 2018 Planned upcoming dot releases: · YP 2.5.1 (Sumo) is in QA. · YP 2.4.4 (Rocko) will be targeted after YP 2.6 M4 is done. · YP 2.5.2 (Sumo) will be targeted after YP 2.4.4 is done. Tracking Metrics: · WDD 2590 (last week 2620) (https://wiki.yoctoproject.org/charts/combo.html) · Poky Patch Metrics oTotal patches found: 1608 (last week 1619) oPercentage of patches in the Pending State: 730 (45%) [last week 740 (46%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status https://wiki.yoctoproject.org/wiki/Yocto_2.6_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.6_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 INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 •Cell:(208) 244-4460 • Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[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. • YP 2.5.1 is in QA. See https://wiki.yoctoproject.org/wiki/2.5_QA_Status. It just started and is 0% complete. Opens/Status: Richard gave an update on the technical issues we have seen. See the weekly status report. Discuss the schedule coming up. Noted that the error log purge has happened. Discussed the need of documentation on the new features being added. Christopher discussed a patch he has submitted and Ross is working on testing. The issues around this were discussed. Ayman is new to the project and was asking how long it takes to come up to speed. Richard gave him feedback to get help on the mailing list and the IRC channel directly. Books and stack overflow are also available. Also discussed that he should use the quick documentation on the YP website. Rich wants to know if any update is planned to secure boot layers around TPM 2. A discussion proceeded about how to get the updates done. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 •Cell: (208) 244-4460 • Email:stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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 Von: yocto-boun...@yoctoproject.org im Auftrag von Erik Nellessen Gesendet: Donnerstag, 2. August 2018 10:28 An: burton, ross Cc: yocto@yoctoproject.org Betreff: Re: [yocto] Non-deterministic build error in package gcc-source Hi Ross, thanks for your response! I deactivated the archiver and started about 40 builds. The problem did not occur. We discussed the different archiver modes. For us, it is probably the best solution to run the archiver with the following configuration: ARCHIVER_MODE[src] ?= "original" ARCHIVER_MODE[diff] ?= "1" To get the original source files and the patches. I am running some builds right now to evaluate if this configuration runs without problems. In any case I would like to report a bug concerning the problems when running the archiver in patched mode. I tried to create a Bugzilla account, but it was not possible, because all of my tries were automatically cancelled. I wrote an email to mich...@yoctoproject.org and hope to get an account soon. Kind regards, Erik Von: Burton, Ross Gesendet: Dienstag, 31. Juli 2018 22:18 An: Erik Nellessen Cc: yocto@yoctoproject.org Betreff: Re: [yocto] Non-deterministic build error in package gcc-source Obvious short answer is do you actually need to use the archiver in patched mode? Changing to a different mode, or disabling the archiver entirely, may solve this. Long answer is this is most likely a race in the archiver, so filing a bug with as many details as you can would be good. Ross On 30 July 2018 at 08:48, Erik Nellessen wrote: > We are building an operating system based on poky > (f0ec7c8b2dc1797ba22c45653a5f182b63354092, bitbake: toaster: add 'Sumo' to > release selection). > > > Sometimes (about 1 in 10 times) our build fails, because the task > do_ar_patched fails for package gcc-source-7.3.0-7.3.0-r0. > > > The short error message: > > 14:44:09 Exception: FileNotFoundError: [Errno 2] No such file or directory: > '/home/jenkins/workspace/_Config_mguard_0.1.0_MG-254-QLU3J23WOWLZZG76AVHU5BVY3M7SIU3EOQQQSUQNOEXHTXRFTQMQ_2/build/qemux86-64_tmp/work-shared/gcc-7.3.0-r0/gcc-7.3.0/gcc/gengtype-lex.c' > 14:44:09 > 14:44:09 ERROR: gcc-source-7.3.0-7.3.0-r0 do_ar_patched: Function failed: > do_ar_patched > 14:44:09 ERROR: Logfile of failure stored in: > /home/jenkins/workspace/_Config_mguard_0.1.0_MG-254-QLU3J23WOWLZZG76AVHU5BVY3M7SIU3EOQQQSUQNOEXHTXRFTQMQ_2/build/qemux86-64_tmp/work-shared/gcc-7.3.0-r0/temp/log.do_ar_patched.43242 > 14:44:09 NOTE: recipe gcc-source-7.3.0-7.3.0-r0: task do_ar_patched: Failed > 14:44:09 ERROR: Task > (/home/jenkins/workspace/_Config_mguard_0.1.0_MG-254-QLU3J23WOWLZZG76AVHU5BVY3M7SIU3EOQQQSUQNOEXHTXRFTQMQ_2//mguard/poky/meta/recipes-devtools/gcc/gcc-source_7.3.bb:do_ar_patched) > failed with exit code '1' > > I attached the full error message as a text file. > > > Does anybody know this error message? Does anybody experience similar > problems with non-deterministic build failure? > > > Kind regards, > > Erik > > .. > Phoenix Contact GmbH & Co. KG > > Sitz der Gesellschaft / registered office of the company: 32825 Blomberg > USt-Id-Nr.: DE124613250 > Pers. haftende Gesellschafterin / personally liable partner: Phoenix Contact > Verwaltungs GmbH > Amtsgericht Lemgo HRB 5273 / district court Lemgo HRB 5273 > Kom. Ges. Amtsgericht Lemgo HRA 3746 / limited commercial partnership > district court Lemgo HRA 3746 > Geschäftsführer / Executive Board: Frank Stührenberg (Vorsitzender / Chief > Executive Officer), Roland Bent, Prof. Dr. Gunther Olesch, Axel Wachholz > ___ > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren, jegliche anderweitige > Verwendung sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorized copying, disclosure, distribution or other use of the material > or parts thereof is strictly forbidden. > ___ > > -- > ___ > yocto mailing list
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, Facebook and Arm to the advisory board. See [1] for a full list of the YP members. * Richard Purdie is now being funded by the Yocto Project to continue in his role as the overall project architect. * Nicolas Dechesne (Linaro) has taken over the community manager role from Jefro * Lieu Ta (WindRiver) has taken over the advisory board chairperson role from Jefro * Andreea Volosincu (WindRiver) has taken on the advocacy lead role from Tracey Erway * Discussions about the future governance of the project with a view to modernisation and clarification are now ongoing but are based upon the strong foundations above. As usual, the Yocto Project will attend the ELC-E conference in October, in Edimburgh, and we hope to see you there, so that you can meet all of us! Feel free to reach out to me, if you have any specific questions! [1] https://www.yoctoproject.org/ecosystem/members/ cheers nico On Wed, May 9, 2018 at 5:33 AM Zoran Stojsavljevic wrote: > > Once I (at least I can speak for myself) embarked on this YOCTO ship, > voluntarily, I do not consider leaving it. I like the concept, > although there are problems with it. > > I could not commit too much time to it (since I have another > commitments), but I keep one eye on it, primarily trying to learn, > and, as abilities allow, to help. > > Big IT players' politics is driven primarily by interest. And interest > is changing over Time, due to Global Policies and Economy shifting... > Well! > > Zoran > ___ > > On Tue, May 8, 2018 at 11:20 PM, Jeff Osier-Mixon wrote: > > Many projects function this way. It is one of the strengths of the open > > source process. > > > > I'd be happy to answer any questions. > > > > > > On Mon, May 7, 2018 at 9:53 PM, Zoran Stojsavljevic > > wrote: > >> > >> Very interesting, indeed! Newer knew that Richard (Purdie) is/was > >> INTEL employee!? > >> > >> This announcement gives several (conspiracy?) theories... Some > >> official, some unofficial. ;-) > >> > >> As independent thinker... IMHO. > >> > >> Time Will Tell! > >> > >> Zoran Stojsavljevic > >> ___ > >> > >> On Mon, May 7, 2018 at 11:53 PM, Jeff Osier-Mixon wrote: > >> > Hello everyone. I'd like to briefly address rumors around Richard > >> > Purdie's > >> > transition from Intel to a more neutral position, and Intel's reduction > >> > in > >> > resources for the project. > >> > > >> > We set up the Yocto Project in 2010 through Linux Foundation, with over > >> > 20 > >> > member organizations, so it would function as a true open source project > >> > - > >> > neutral, unbiased, and well distributed. Those things are what make open > >> > source projects less vulnerable to any one person or company. This is > >> > actually a very exciting transitional time for the project, and all > >> > existing > >> > member organizations are fully behind the project. We will let people > >> > know > >> > details as they are available. > >> > > >> > Meanwhile, the 2.5 "Sumo" release is on the way and should be released > >> > soon, > >> > the 2.6 planning process has started in earnest (please participate!), > >> > and > >> > we are excited to see what the future has in store for the project. > >> > > >> > -- > >> > Jeffrey “Jefro” Osier-Mixon, Intel Corporation > >> > Open Source Community Ecosystem Strategist > >> > > >> > > >> > -- > >> > ___ > >> > yocto mailing list > >> > yocto@yoctoproject.org > >> > https://lists.yoctoproject.org/listinfo/yocto > >> > > > > > > > > > > > -- > > Jeffrey “Jefro” Osier-Mixon, Intel Corporation > > Open Source Community Ecosystem Strategist > > > -- > ___ > 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] 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 or COMMON_EXTRA_OECONF_append_pn-*recipename* *Which one to use?* Say for extra compilation options for php from *local.conf* , do I use*?* PACKAGECONFIG[php]="--enable-ftp --enable-sysvshm --enable-sysvmsg --enable-sysvsem --enable-debug" or PACKAGECONFIG_append_pn-php = "--enable-ftp --enable-sysvshm --enable-sysvmsg --enable-sysvsem --enable-debug" or COMMON_EXTRA_OECONF_append_pn-php = "--enable-ftp --enable-sysvshm --enable-sysvmsg --enable-sysvsem --enable-debug" Thanks, S -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
