|
Additional hardening options
Another quirk of this - with dunfell, the buildepoxy SDK test fails on Ubuntu 18.04 with -fstack-clash-protection because the version of meson in dunfell uses the same LDFLAGS value for both host and
Another quirk of this - with dunfell, the buildepoxy SDK test fails on Ubuntu 18.04 with -fstack-clash-protection because the version of meson in dunfell uses the same LDFLAGS value for both host and
|
By
Paul Eggleton
· #55987
·
|
|
Inclusive Language Proposal for YP/OE
The layer index does already support this, it's just not exposed (at the time I introduced it - some time ago - I thought it might encourage people to deviate from the release branch names, but in hin
The layer index does already support this, it's just not exposed (at the time I introduced it - some time ago - I thought it might encourage people to deviate from the release branch names, but in hin
|
By
Paul Eggleton
· #55973
·
|
|
Additional hardening options
Hi folks I've been looking into a couple of compiler flags for hardening that I think we might want to consider enabling by default in security-flags.inc: 1) -fstack-clash-protection This option was i
Hi folks I've been looking into a couple of compiler flags for hardening that I think we might want to consider enabling by default in security-flags.inc: 1) -fstack-clash-protection This option was i
|
By
Paul Eggleton
· #55972
·
|
|
[meta-qt4]
Hi Jared / all My apologies - I've applied the fix and pushed it to master, thank you! I think it's fair to say this layer is pretty much unmaintained at the moment. I'd be more than happy if someone
Hi Jared / all My apologies - I've applied the fix and pushed it to master, thank you! I think it's fair to say this layer is pretty much unmaintained at the moment. I'd be more than happy if someone
|
By
Paul Eggleton
· #55294
·
|
|
glibc -fstack-protector-strong
Hi folks I'm looking at how -fstack-protector-strong might be enabled in the glibc recipe. It looks like it should already be enabled by default via --enable-stack-protector=strong in EXTRA_OECONF, ho
Hi folks I'm looking at how -fstack-protector-strong might be enabled in the glibc recipe. It looks like it should already be enabled by default via --enable-stack-protector=strong in EXTRA_OECONF, ho
|
By
Paul Eggleton
· #55079
·
|
|
[layerindex-web][PATCH] Add SPDX license headers to layerindex-web source files
Hi Ida My sincere apologies for the delay. I have now integrated this, but I did have to make a few changes: 1) Dropped the newline changes; these weren't related and also modified files that we want
Hi Ida My sincere apologies for the delay. I have now integrated this, but I did have to make a few changes: 1) Dropped the newline changes; these weren't related and also modified files that we want
|
By
Paul Eggleton
· #53203
·
|
|
Bug 10699 - Ensure consistency in repository URLs
#yocto
#python
Hi folks my replies inline below Actually for this issue we're not concerned with SRC_URI, just the repo URL at the layer level - the database is normalised so that the latter is mostly in one place.
Hi folks my replies inline below Actually for this issue we're not concerned with SRC_URI, just the repo URL at the layer level - the database is normalised so that the latter is mostly in one place.
|
By
Paul Eggleton
· #50997
·
|
|
Automated script to know all the Recipes details
Hi there So if you're familiar with Python you could fairly quickly write a script to iterate over recipes and get these values using tinfoil: https://wiki.yoctoproject.org/wiki/TipsAndTricks/Tinfoil
Hi there So if you're familiar with Python you could fairly quickly write a script to iterate over recipes and get these values using tinfoil: https://wiki.yoctoproject.org/wiki/TipsAndTricks/Tinfoil
|
By
Paul Eggleton
· #50939
·
|
|
RFC: Devtool support to read BB_ENV_EXTRAWHITE variables and parse the env variables same as bitbake
Hi Chandana, Assuming you are quoting the command verbatim, the issue here is that the shell is evaluating TOPDIR, so devtool doesn't even get to see the reference. Granted, even if you use single quo
Hi Chandana, Assuming you are quoting the command verbatim, the issue here is that the shell is evaluating TOPDIR, so devtool doesn't even get to see the reference. Granted, even if you use single quo
|
By
Paul Eggleton
· #50061
·
|
|
[layerindexweb][PATCH 0/7] Django 2.2 Upgrade
Hi Amber Thanks for doing this! I've just merged the patches this morning. Next we need to figure out how to do the upgrade on the live site - which is a little tricky given the current state of the R
Hi Amber Thanks for doing this! I've just merged the patches this morning. Next we need to figure out how to do the upgrade on the live site - which is a little tricky given the current state of the R
|
By
Paul Eggleton
· #49770
·
|
|
QA notification for completed autobuilder build (yocto-3.1.rc2)
Release notes draft attached, including a dedication to Scott (wasn't sure where to put that so I've just left it at the top) and contributors list. Let me know if you notice anything missing/incorrec
Release notes draft attached, including a dedication to Scott (wasn't sure where to put that so I've just left it at the top) and contributors list. Let me know if you notice anything missing/incorrec
|
By
Paul Eggleton
· #49165
·
|
|
Root login not working with Warrior
Or perhaps more reasonably, does it contain the name of the device you are attempting to log in via? Cheers Paul
Or perhaps more reasonably, does it contain the name of the device you are attempting to log in via? Cheers Paul
|
By
Paul Eggleton
· #47982
·
|
|
Root login not working with Warrior
Hi Teemu Is there an /etc/securetty file and if so what does it contain? Cheers Paul
Hi Teemu Is there an /etc/securetty file and if so what does it contain? Cheers Paul
|
By
Paul Eggleton
· #47981
·
|
|
[layerindex-web][PATCH] Fix parsing after AVAILABLE_LICENSES change
In OE-Core commit 8c9ef587fe499c612a878a1ab42092eb79b334ef an AVAILABLE_LICENSES variable was added in license.bbclass where its value is assigned with immediate expansion ( :=3D ) with the result tha
In OE-Core commit 8c9ef587fe499c612a878a1ab42092eb79b334ef an AVAILABLE_LICENSES variable was added in license.bbclass where its value is assigned with immediate expansion ( :=3D ) with the result tha
|
By
Paul Eggleton
· #47871
·
|
|
[layerindex-web][PATCH] requirements.txt: bump Django version to fix CVE-2019-19844
Fixes a vulnerability in the password reset process due to insufficiently stringent validation of unicode email addresses. https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ https://n
Fixes a vulnerability in the password reset process due to insufficiently stringent validation of unicode email addresses. https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ https://n
|
By
Paul Eggleton
· #47778
·
|
|
[layerindex-web][PATCH 0/5] Misc bug fixes [cover letter only]
Updates some bundled components (jQuery, Chart.js, Bootstrap) and fixes a couple of bugs in the layer update script and background task display for admins. The following changes since commit f84223f47
Updates some bundled components (jQuery, Chart.js, Bootstrap) and fixes a couple of bugs in the layer update script and background task display for admins. The following changes since commit f84223f47
|
By
Paul Eggleton
· #47594
·
|
|
Missing layer in the layer index
Actually looking at the new repo I think I know what might have happened. The layer index does not currently handle layers that don't have a master branch perfectly; it could be that the original repo
Actually looking at the new repo I think I know what might have happened. The layer index does not currently handle layers that don't have a master branch perfectly; it could be that the original repo
|
By
Paul Eggleton
· #47563
·
|
|
Missing layer in the layer index
Oddly there are no maintainer records and no layer branch records either, hence why the layer doesn't show up properly. I'm unsure how it would have got into that state or how long it's been there, bu
Oddly there are no maintainer records and no layer branch records either, hence why the layer doesn't show up properly. I'm unsure how it would have got into that state or how long it's been there, bu
|
By
Paul Eggleton
· #47559
·
|
|
[warrior] [meta-qt4] recipes-qt4: qt4-embedded: fix build on GCC v8
We've all done it at some point ;) Cheers Paul
We've all done it at some point ;) Cheers Paul
|
By
Paul Eggleton
· #47428
·
|
|
[warrior] [meta-qt4] recipes-qt4: qt4-embedded: fix build on GCC v8
Hi Quentin So I tested this and the name of the patch doesn't match up with the change to SRC_URI. I have however gone ahead and fixed it and merged it to warrior, but if you could please ensure you t
Hi Quentin So I tested this and the name of the patch doesn't match up with the change to SRC_URI. I have however gone ahead and fixed it and merged it to warrior, but if you could please ensure you t
|
By
Paul Eggleton
· #47420
·
|