I don't think so, that adding bbfatal into this recipe is a good
solution. Someone could build the busybox with /bin/sh linking into
.suid eg. for more secure. We can leave live with this one as before.
Andrej
On 11/09/2017 02:25 PM, Nathan Rossi wrote:
> Add a sanity check during the do_compile
The following commit added the FL_LPAE flag to FL_FOR_ARCH7VE, but
neglected to also add it to the armv7ve compatible cores defined in
arm-cores.def.
https://github.com/gcc-mirror/gcc/commit/af2d9b9e58e8be576c53d94f30c48c68146b0c98
The result is that gcc 6.4 now refuses to allow -march=armv7ve
== Series Details ==
Series: gcc6: enable FL_LPAE flag for armv7ve cores
Revision: 1
URL : https://patchwork.openembedded.org/series/9693/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been exec
The default systemd-tmpfiles config file expects to be able to create
files etc belonging to the wheel system group. Currently the wheel
group is created at run time by systemd-sysusers, but that doesn't
happen if systemd-sysusers is disabled (as it currently is by default
when building with musl l
The following commit added the FL_LPAE flag to FL_FOR_ARCH7VE, but
neglected to also add it to the armv7ve compatible cores defined in
arm-cores.def.
https://github.com/gcc-mirror/gcc/commit/af2d9b9e58e8be576c53d94f30c48c68146b0c98
The result is that gcc 6.4 now refuses to allow -march=armv7ve
On 11/01/2017 08:30 AM, Khem Raj wrote:
> Hi Martin/Armin
>
> I looked at the first report with musl from Martin. Most of the
> failures are familiar except 2 I think which I plan to look at. I
> haven't blacklisted them intentionally, to get annoyed enough to keep
> fixing them as time permits.
Got it, thanks. My patch *should* just convert runtime failures into
compile-time failures, but it looks like we're seeing actual runtime
failures, so I'll try to figure out what happened.
On 11/08/2017 12:31 PM, Burton, Ross wrote:
Thanks for reminding me. :)
1/2 is queued but 2/2 was impli
On Thu, Nov 9, 2017 at 12:54 PM, Burton, Ross wrote:
> How does this help? A bbappend is parsed after the bb so it can just assign
> to SRCREV.
>
> Also is it actually useful to change the git url but apply the same patches?
>
yes, this helps with using local forks of upstream and at the same
ti
How does this help? A bbappend is parsed after the bb so it can just
assign to SRCREV.
Also is it actually useful to change the git url but apply the same patches?
Ross
On 9 November 2017 at 01:58, Khem Raj wrote:
> This makes it easy to override them in bbappends
>
> Signed-off-by: Khem Raj
On Thu, 26 Oct 2017 10:33:19 -0700
leonardo.sandoval.gonza...@linux.intel.com wrote:
RP indicated two scenarios that this v1 won't work:
1) if oe-selftest comes from a tarball (together with the other repo files)
2) if other no-poky layers are present on current BBLAYERS.
I will review both item
From: Erik Botö
The current implementation is broken when the localpath is a link.
Then only a symlink would be created on the target, instead of copying
the actual file.
[YOCTO #11524]
Signed-off-by: Erik Botö
Signed-off-by: Stephano Cetola
---
meta/lib/oeqa/utils/sshcontrol.py | 9 +++-
From: Erik Botö
This matches how it is called, and how it is named in qmeu target.
[YOCTO #11524]
Signed-off-by: Erik Botö
Signed-off-by: Stephano Cetola
---
meta/lib/oeqa/controllers/masterimage.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/controllers
From: Erik Botö
On systemd systems calling reboot over an ssh connection doesn't
return as expected causing an exception, therefore wrap the call
to reboot in order to avoid this issue.
Also sync the filesystems before rebooting cause otherwise, it will be
done as part of the reboot and could ta
Backporting fixes since I never got these into 2.4.
Requested by erik.b...@pelagicore.com.
This fixes [YOCTO #11524]
Erik Botö (4):
masterimage.py: fix issue with calling reboot on masterimage/DUT
masterimage.py: fix stop()
masterimage.py: rename parameter "params" in start() to
"extra
From: Erik Botö
The stop() function is called in the context of the masterimage,
so self.master should be used instead of self.connection which is
undefined at that time.
[YOCTO #11524]
Signed-off-by: Erik Botö
Signed-off-by: Stephano Cetola
---
meta/lib/oeqa/controllers/masterimage.py | 2 +
Ping, is there any plan to include this patch in a short term?
Regards.
On 11/03/2017 01:46 PM, Isaac Hermida wrote:
> WPA2 is vulnerable to replay attacks which result in unauthenticated users
> having access to the network.
>
> * CVE-2017-13077: reinstallation of the pairwise key in the Four-wa
On 11/08/2017 05:31 PM, Mark Hatle wrote:
BTW. If you really don't want to use debugedit then you could use
something simple like a quick hack to list all sources I wrote some
time ago:
https://lists.fedorahosted.org/archives/list/elfutils-devel@lists.fedor
ahosted.org/message/VZP4G5N2ELYZEDAB3Q
FYI: You can use PV = "2.0.99+2.1.0-beta3" to make sure that it's sorted
higher than any 2.0.* release and that final 2.1.0 again sorts higher than
this beta3 without PE bump.
On Thu, Nov 9, 2017 at 4:23 PM, akuster808 wrote:
>
>
> On 11/08/2017 11:05 AM, Martin Jansa wrote:
>
> The only change
On 11/08/2017 11:05 AM, Martin Jansa wrote:
> The only change from previous report is slightly newer oe-core and bitbake.
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='4'|Failed tasks
From: Patrick Vacek
For recipes that depend on native ca-certificates.crt, /etc should be
added to the list of directories that automatically populate the
sysroot, otherwise the file may not be there.
Signed-off-by: Patrick Vacek
---
meta/recipes-support/ca-certificates/ca-certificates_2017071
This upgrade is critical as it fixes the support for Linux 4.14 LTS kernel.
The changlog is:
2017-10-05 LTTng modules 2.9.5
* Fix: update block instrumentation for 4.14 kernel
* Revert "Fix: update block instrumentation for kernel 4.14"
2017-10-03 (National Techies Day) LTTng mod
Add a sanity check during the do_compile task to fail if the suid
busybox provides /bin/sh. This is considered as a hard fail since not
only is providing sh as suid problematic for security reasons but also
because the sh configured for suid is less functional than the nosuid
configured sh and brea
On Thu, 2017-11-09 at 14:04 +0100, Patrick Ohly wrote:
> On Thu, 2017-11-09 at 11:55 +, Richard Purdie wrote:
> >
> > + # We only want to print runqemu stdout/stderr if there is a
> > test
> > case failure
> > + buffer = True
> Does the value matter? The other code only seems to check fo
On 11/08/2017 05:31 PM, Mark Hatle wrote:
So a couple of questions.
- What exactly breaks currently when you let debugedit rewrite the
debuginfo source paths?
Alexander has more info then I do here, but I believe running it against grub
modules breaks the modules.
Here's how you can repr
On Thu, 2017-11-09 at 11:55 +, Richard Purdie wrote:
> + # We only want to print runqemu stdout/stderr if there is a test
> case failure
> + buffer = True
Does the value matter? The other code only seems to check for the
presence of the "buffer" attribute.
Changing this to "buffer = Fal
If we don't remove the handler we end up with duplicate log messages
which is undesireable.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/utils/qemurunner.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/qemurunner.py
b/meta/lib/oeqa/utils/qemurunn
This ensures the console is kept clear of confusing output but that
the main logs contain good debugging information.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/core/target/ssh.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib
Bitbake logs info messages to the console. These messages are really
there as debugging information. At the debug level, they will be shown
in failure logs and in the task logs but not on the console which
is what we want in this case.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/utils/qemuru
In general we don't need to see the output of runqemu however if it fails
we do. Use the buffer option that already exists in TestResult but allow
us to trigger it on a per test basis.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/core/runner.py| 8
meta/lib/oeqa/selftest/
The logger handling in oeqa was confused at best. This patch:
a) Passes in a logger through various qemu runner pieces
b) Uses that logger consistently in the code
c) Creates a logger for QemuRunner outside the bitbake namespace
meaning we don't conflict with the tinfoil logging changes
The re
I have no idea why we didn't do this but it means the code has nowhere
to log to unless we do this. This means we can then use the logger
to log data to the task logs.
Signed-off-by: Richard Purdie
---
meta/classes/testimage.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
This funciton appears completely unused, drop it.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/targetcontrol.py | 29 ++---
1 file changed, 2 insertions(+), 27 deletions(-)
diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index 3255e3a..e17
Fix the bashism in the suid check. This ensures that the check works
correctly on hosts that default sh to e.g. dash. If this check fails the
suid shell workaround does not remove sh from the suid binary and
results in the target system containing a busybox.suid with sh as well
as /bin/sh -> /bin/b
On Thu, Nov 9, 2017 at 10:43 AM, Andrea Adami wrote:
> On Wed, Nov 8, 2017 at 8:05 PM, Martin Jansa wrote:
>> The only change from previous report is slightly newer oe-core and bitbake.
>>
>>
>> http://www.openembedded.org/wiki/Bitbake_World_Status
>>
>> == Number of issues - stats ==
>> {| class
On Wed, Nov 8, 2017 at 8:05 PM, Martin Jansa wrote:
> The only change from previous report is slightly newer oe-core and bitbake.
>
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='4'|Failed tasks!!|Sign
(ping) for this backport patch.
Thx.
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Arturo
Buzarra
Sent: Thursday, November 02, 2017 14:47
To: openembedded-core@lists.openembedded.org
Subjec
36 matches
Mail list logo
