ntpd: NTP server denial of service flaw
CVE: CVE-2016-6301
Signed-off-by: Andrej Valek
Signed-off-by: Pascal Bach
---
.../busybox/busybox/CVE-2016-6301.patch| 37 ++
meta/recipes-core/busybox/busybox_1.24.1.bb| 1 +
2 files changed, 38 insertions(+)
cre
Sending report email was not working correctly if the script was given
an html report path that contained directory components.
Signed-off-by: Markus Lehtonen
---
scripts/contrib/oe-build-perf-report-email.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/contrib/oe-
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: den 5 april 2017 16:44
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCHv2 3/3] base-files: profile: Simplify
> setting variables conditionall
Upstream has removed the 1.14.1 release from ftp.gnu.org and
moved on to the latest 1.14.2. Since we don't want to upgrade
at this point of time, temporarily move the SRC_URI to yoctoproject
mirror.
Signed-off-by: Maxin B. John
---
meta/recipes-extended/ed/ed_1.14.1.bb | 3 ++-
1 file changed, 2
From: Choong YinThong
Fedorahosted.org was retired on March 1st, 2017.
Replace all fedorahosted.org SRC_URI with source pagure.io and github.com.
Choong YinThong (8):
selftest/recipetool: replace fedorahosted.org SRC_URI with github.com
source
xmlto: replace fedorahosted.org SRC_URI with
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/lib/oeqa/selftest/recipetool.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/recipes-devtools/xmlto/xmlto_0.0.28.bb | 4 ++--
1 file changed, 2 in
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/recipes-extended/libuser/libuser_0.62.bb | 6 +++---
1 file changed,
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com. This github link
is distributions to fedoreproject.org and the contact
Mailing list: cronie-devel AT lists.fedorahosted DOT org
[YOCTO #11226]
Signed-off-by: Choong YinTh
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to update
the SRC_URI to point to github.com.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb | 14 ++
1 file changed, 10 insertions(+), 4 deletions
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/recipes-extended/logrotate/logrotate_3.9.1.bb | 19 +++
1 file changed, 15 insertions(+), 4 delet
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/recipes-extended/newt/libnewt_0.52.19.bb | 4 ++--
1 file changed, 2
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.
[YOCTO #11226]
Signed-off-by: Choong YinThong
---
meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb | 4 ++--
1 file
== Series Details ==
Series: Remove all use of fedorahosted SRC_URI [YOCTO #11226] (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/6116/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tes
On mercredi 5 avril 2017 09:30:52 CEST Jussi Kukkonen wrote:
> This apparently breaks key generation with openssl-native because the file
> doesn't exist.
Looking at the recipe right now, I understand why key generation is broken for
native build (I should have been more careful). I see two ways
* V2:
Use '/usr/bin/env foo' rather than /usr/bin/foo or /bin/foo as shebang.
// Robert
The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:
oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir
(2017-04-06 10:13:34 +0100)
are available in the gi
The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
#define BINPRM_BUF_SIZE 128
There would be errors when @PERL@ (hostools/perl) is longer than 128,
use '/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
doesn't work:
/usr/bin/env: perl -w: No s
The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
#define BINPRM_BUF_SIZE 128
There would be errors when @PERL@ (hostools/perl) is longer than 128,
use '/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
doesn't work:
/usr/bin/env: perl -w: No s
The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
#define BINPRM_BUF_SIZE 128
So there would be errors when /path/to/hosttools/perl is longer than 128.
Set ac_cv_path_PERL to "/usr/bin/env perl" to fix the problem.
Signed-off-by: Robert Yang
---
meta/recipes
Fixed when len(TMPDIR) = 410:
Can't exec "/bin/sh": Argument list too long at /usr/lib/perl/5.18/IO/File.pm
line 65.
This is becuase it has a lot of m4 files, use relative path for them
can fix the problem.
Signed-off-by: Robert Yang
---
meta/recipes-devtools/guile/guile_2.0.14.bb | 3 +++
1
Fixed when len(TMPDIR) = 410:
Can't exec "/bin/sh": Argument list too long at /usr/lib/perl/5.18/IO/File.pm
line 65.
This is becuase it has a lot of m4 files, use relative path for them
can fix the problem.
Signed-off-by: Robert Yang
---
meta/recipes-devtools/m4/m4-1.4.18.inc | 3 +++
1 file
The shebang's length is usually 128 as defined in /usr/include/linux/binfmts.h:
#define BINPRM_BUF_SIZE 128
So there would be errors when /path/to/hosttools/perl is longer than 128.
This patch fixes the problem when POSIX_SHELL and perl are used as the
interpreters.
Signed-off-by: Robert Yang
The shebang's length is usually 128 as defined in /usr/include/linux/binfmts.h:
#define BINPRM_BUF_SIZE 128
So there would be errors when /path/to/hosttools/bash is longer than 128:
/bin/sh: ./doltcompile: [snip]: bad interpreter: No such file or directory
Set ac_cv_path_DOLT_BASH to "/usr/bin
Hi Brian and RP,
This patch can't fix the problem of scripts/oe-run-native, it only can
run the native tools which is depended by meta-ide-support, for example:
$ bitbake bmap-tools-native meta-ide-support
$ oe-run-native bmaptool --help # exmaple from dev-manual-start.xml
Error: Unable to find
On 6 April 2017 at 12:23, David Vincent wrote:
>
> On mercredi 5 avril 2017 09:30:52 CEST Jussi Kukkonen wrote:
> > This apparently breaks key generation with openssl-native because the
file
> > doesn't exist.
>
> Looking at the recipe right now, I understand why key generation is
broken for
> nat
Signed-off-by: Martin Jansa
---
meta/recipes-core/udev/eudev_3.2.1.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/udev/eudev_3.2.1.bb
b/meta/recipes-core/udev/eudev_3.2.1.bb
index 4a1a26aade..bdfb5441ad 100644
--- a/meta/recipes-core/udev/eudev_3.2.1.b
On Tue, 2017-04-04 at 14:10 +0300, Ed Bartosh wrote:
> Added new parameter 'api' to sparse_copy function to specify
> underlying filemap API to use. By default sparse_copy will
> try both available APIs.
>
> Added test case for sparse_copy to wic test suite.
>
> Signed-off-by: Ed Bartosh
> ---
>
We need the bitbake bug in recrdeptask handling of missing tasks fixed in
order to apply a fix for OE-Core.
Signed-off-by: Richard Purdie
---
meta/conf/sanity.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/sanity.conf b/meta/conf/sanity.conf
index 616f11c..46b
We've had a lot of users running into RSS issues where -initial recipes
were being installed into sysroots alongside their counterparts and
causing overlapping files issues.
In general this was through do_build dependencies. Such dependencies are
bad in general and I'd encourage people to compare
On Thu, 2017-04-06 at 08:48 +0300, Dmitry Rozhkov wrote:
> On Thu, 2017-04-06 at 05:32 +, Patchwork wrote:
> >
> > == Series Details ==
> >
> > Series: python3: fix run-time deps for core python3 libraries
> > (rev2)
> > Revision: 2
> > URL : https://patchwork.openembedded.org/series/6164/
On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote:
> This commit updates the recipe to the last upstream tag. Then, as the
> tarball no longer contains the pre-generated Makefile, inherit from
> autotools
>
> [...]
> -PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl
> selinux', d
Added new parameter 'api' to sparse_copy function to specify
underlying filemap API to use. By default sparse_copy will
try both available APIs.
Added test case for sparse_copy to wic test suite.
Signed-off-by: Ed Bartosh
---
meta/lib/oeqa/selftest/wic.py | 29 +
scr
From: Ming Liu
Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a cross recipe even they are not
in use at all.
This can lead a lot of churn when the cross sysroot are shared by
machines while they have defined different TARGET_* flags.
An
From: Ming Liu
Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a cross-canadian recipe even they
are not in use at all.
This can lead a lot of churn when the cross-canadian sysroot are shared
by machines while they have defined different T
From: Ming Liu
I had found a lot of churn in sysroots when multiple MACHINEs are
sharing a same build folder, which is the case in my company, after
digging into it, I found it's caused by the TARGET_-* flags, they
are exported but not in use at all, they should be replaced by
particular flags fo
From: Ming Liu
Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a crosssdk recipe even they are
not in use at all.
This can lead a lot of churn when the crosssdk sysroot are shared by
machines while they have defined different TARGET_* flag
From: Ming Liu
Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a nativesdk recipe even they are
not in use at all.
This can lead a lot of churn when the nativesdk sysroot are shared by
machines while they have defined different TARGET_* fl
Hello,
Le 06/04/2017 à 13:38, Richard Purdie a écrit :
> On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote:
>> This commit updates the recipe to the last upstream tag. Then, as the
>> tarball no longer contains the pre-generated Makefile, inherit from
>> autotools
>>
>> [...]
>> -PACKAGECONF
We never need these tasks as dependencies of other sstate tasks since
they're only ever needed to build artefacts so we can always skip them
and save some time/space.
Signed-off-by: Richard Purdie
---
meta/classes/sstate.bbclass | 4
1 file changed, 4 insertions(+)
diff --git a/meta/classe
I still don't understand why not use standard update-alternatives and
install another package with your favorite openssl.conf which has higher
ALTERNATIVE_PRIORITY.
This way u-a will switch to new config even when you just install the
package which require it on the target later and will switch ba
As Fedora 26 has a new gcc [1] and a new system pkg-config implementation [2] I
wanted to do some testing on that host OS so that we might be able to get some
fixes in before Pyro/2.3 is released.
The following series were the only changes required to start building (I have
tested core-image-mini
Backport a fix from upstream for a -Wformat-truncation=2 warning
and implement a simple fix for a -Wimplicit-fallthrough warning.
Signed-off-by: Joshua Lock
---
.../elfutils-0.168/Fix_one_GCC7_warning.patch | 44 ++
.../elfutils/elfutils-0.168/fallthrough.patch | 36
Building gcc-cross-initial with GCC7 on the host fails due to the
comparison of a pointer to an integer in ubsan_use_new_style_p, which
is forbidden by ISO C++:
ubsan.c:1474:23: error: ISO C++ forbids comparison between pointer and
integer [-fpermissive]
|| xloc.file == '\0' || xloc.file[0]
Ping.
Any further comments on this change?
I covered at least one additional use case not covered by
generic symlink-relative.py call at post stage:
It is buildtools-tarball, where may add ca-certificates to use with
curl.
Change is simple: we create relative symlinks in update-ca-certificates
On Thu, Apr 6, 2017 at 6:23 AM, Joshua Lock wrote:
> As Fedora 26 has a new gcc [1] and a new system pkg-config implementation [2]
> I
> wanted to do some testing on that host OS so that we might be able to get some
> fixes in before Pyro/2.3 is released.
>
> The following series were the only ch
Hi,
Is there any hidden pointer within these static dev packages. i
expected the library to be .a format. what can i understand from these
static dev packages, plz let me know.
Thanks
On Wed, Apr 5, 2017 at 2:37 PM, Ravi chandra reddy
wrote:
> Hi,
> is this what you are talking abo
Changed dependency task for syslinux from do_build to
do_populate_sysroot as do_build dependency caused conflicts in
populating image recipe sysroot using conflicting recipes. This
makes do_image_wic task to fail with FileExistsError trying to
copy the same file from two conflicting recipes.
This
Acked-by: Aníbal Limón
On 04/05/2017 08:36 AM, Patrick Ohly wrote:
> I started applying yocto-compat-layer to some real BSP layers and ran
> into some usability issues with the tool.
>
> I also didn't want to do the root cause analysis manually, so I
> automated the dependency analysis and the r
From: Leonardo Sandoval
The unit test requires x11 as distro feature, otherwise it will fail
while building the test requirements.
[YOCTO #10903]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/recipetool.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/selft
This bashism prevents functions from working on systems without bash,
ie. on systems with busybox shell or debian dash. Replace them with
bourne-compatible command instead.
Signed-off-by: Marek Vasut
Cc: Ross Burton
Cc: Richard Purdie
---
NOTE: Does this lsbscripts have upstream somewhere ?
---
== Series Details ==
Series: lsb: Remove bashisms from the rc.d functions
Revision: 1
URL : https://patchwork.openembedded.org/series/6209/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been exe
On Thu, Apr 6, 2017 at 9:20 AM, Ravi chandra reddy wrote:
> Hi,
> Is there any hidden pointer within these static dev packages. i
> expected the library to be .a format. what can i understand from these
> static dev packages, plz let me know.
Can you expand on what you're trying to accomplis
From: Martin Kelly
meta/conf/bitbake.conf puts python2.7 into the HOSTTOOLS variable but not
python2, so only python2.7 is guaranteed. In addition, on some distros -- such
as Amazon Linux -- /usr/bin/python2 doesn't exist but python2.7 does. So, use
python2.7 for the --python= argument in the qem
From: Martin Kelly
Currently, the following situation fails:
- Build an SDK and image. Make the image support graphics but not X11.
- Extract SDK and copy image somewhere outside of the Yocto workspace. Do
runqemu on the image.
This results in the error:
"Could not initialize SDL(No available
From: Martin Kelly
Currently, the following situation fails:
- Build an SDK and image. Make the image support graphics but not X11.
- Extract SDK and copy image somewhere outside of the Yocto workspace. Do
runqemu on the image.
This results in the error:
"Could not initialize SDL(No available
Hi,
I am trying to generate LibIIO [open source by Analog Devices], however
there is dependancy on Libxml2.
problem with Libxml2, it is dependant on *python*-lib, libdl, libz, libzma,
libm
for some reason with Yocto built Libxml2.so, i am encountering "undefined
references error", which i am
On Thursday, 6 April 2017 1:36:05 AM NZST you wrote:
>AssertionError: False is not true : Layer meta- changed 120
> signatures, initial differences (first hash without, second with layer):
BTW, rather than self.assertTrue(False, ... ) you can just use self.fail(...)
and then you avoid thi
Fixes for lib/oe/sstatesig.py corresponding to the bitbake-diffsigs
patchset I just sent to bitbake-devel.
The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:
oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir
(2017-04-06 10:13:34 +0100)
are av
In find_siginfo(), which is used by bitbake-diffsigs among other things,
avoid adding a siginfo file from the sstate-cache where we've already
collected a sigdata file from the stamps directory with the same hash.
This avoids the possibility that the top two files (as picked by default
using the bi
When comparing signatures with bitbake-diffsigs -t or bitbake -S
printdiff, we use this find_siginfo() function implemented in this
module to find the siginfo/sigdata files corresponding to the tasks
we're looking for. However, native sstate files go into a
NATIVELSBSTRING subdirectory and there wa
Hi,
On Thu, Apr 6, 2017 at 10:11 PM, Ravi chandra reddy
wrote:
> Hi,
> I am trying to generate LibIIO [open source by Analog Devices],
> however there is dependancy on Libxml2.
>
For libiio there is a recipe in meta-openembedded [1]. Are you using that
one?
[1] http://layers.openembedded.o
Update Upstream-Status tags and apply 010-fix-rpmatch.patch
unconditionally, since it's merged unconditionally upstream.
Signed-off-by: Andre McCurdy
---
.../mtd/mtd-utils/0001-Fix-build-with-musl.patch | 15
.../mtd/mtd-utils/010-fix-rpmatch.patch| 45
The mismatched checksums cause fatching failed in my setup.
Signed-off-by: Jianxun Zhang
---
I am not sure why I got this issue today, but it seems the upstream package has
different checksums.
Maintainer could help to check if this is a false patch.
meta/recipes-extended/ethtool/ethtool_4.8.
See other ethtool change on ML from this week.
On Fri, Apr 7, 2017 at 12:58 AM, Jianxun Zhang <
jianxun.zh...@linux.intel.com> wrote:
> The mismatched checksums cause fatching failed in my setup.
>
> Signed-off-by: Jianxun Zhang
> ---
> I am not sure why I got this issue today, but it seems the
On Wed, 2017-04-05 at 23:41 -0700, Robert Yang wrote:
> The following changes since commit
> 3a1cce659156ef2654a55a6e3c6922fa2dc780e4:
>
> glibc: fix nativesdk ldd RTLDLIST (2017-04-05 23:22:06 +0100)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-cor
If you want to be able to use -fstack-protector then you need the
runtime support - you can either write this yourself or use libssp
supplied with GCC. If you're using GCC then it seems likely that you'd
just be using libssp, so include in the SDK by default; however use
RRECOMMENDS just in case it
Backport this to morty since if you want runtime support for stack-smashing
protection when building with gcc you need this library.
The following changes since commit ddf907ca95a19f54785079b4396935273b3747f6:
Revert "file: update SRCREV for 5.28 to fix fetch fail on missing commit"
(2017-03-
Hi Robert,
I was definitely looking at only the extract-rootfs issue and didn't
remember seeing your above patch. I agree that we need a broader solution
than the one I did. I tried applying yours but had some issues. Your patch
did fix the runqemu-extract-rootfs, but not when I had INHERIT+= " r
On 04/07/2017 10:48 AM, Brian Avery wrote:
Hi Robert,
I was definitely looking at only the extract-rootfs issue and didn't remember
seeing your above patch. I agree that we need a broader solution than the one I
did. I tried applying yours but had some issues. Your patch did fix the
runqemu-e
If the cwd is named "buildhistory" and the user hasn't specified an
alternative path on the command line, then assume that the current
directory is the buildhistory directory. This makes it easier to run
buildhistory-diff and also interact with the buildhistory git repository
as you no longer have
Having added writing out of the task signature list to buildhistory
(when BUILDHISTORY_FEATURES includes "task"), we now need a way to
compare the list. This just shows which tasks have been added / changed
signature / removed.
Signed-off-by: Paul Eggleton
---
meta/lib/oe/buildhistory_analysis.p
If you're looking to compare task signatures between builds, that can
actually be a bit difficult to do if you don't have anything printed
out (e.g. from an error) with some signatures to look for. buildhistory
already makes a commit (or several commits) for each build, so we can
actually write the
If we want to determine what changed since the last build, one angle
from which to look at it is to check the signatures. However, if we
don't actually have the signatures from the last build we don't have
anywhere to start. Save the signatures on each build in order to give us
the starting point.
Append to the value with appendVarFlag() instead of setting it outright,
so that we can also append to it in other places. Accordingly, this
varflag is pipe-separated (since we want to be able to exclude any
string fragment, in this case including the leading space), thus put a
leading pipe charact
Use the code underpinning bitbake-diffsigs to add an option to
buildhistory-diff to determine and display the differences between the
actual signature inputs, with a twist - we collapse identical
changes across different tasks, showing only the most recent task to
have that difference, meaning that
Save a file per task listing sha256sums for each file staged, i.e.
the output of the task. Some caveats:
1) This only covers sstate tasks since it uses SSTATEPOSTUNPACKFUNCS,
however those are generally the most interesting in terms of output
anyway.
2) The signature is taken before applying
* 54807d47 aarch64: add single instruction math functions
* b6e1fe0d fix strptime output for %C without %y
* 834ef7af fix processing of strptime %p format
* 85dfab7e fix off-by-one in strptime %j
* 9571c531 regex: fix newline matching with negated brackets
* e6917ece increase limit on locale name l
On 6 April 2017 at 19:41,
wrote:
> From: Leonardo Sandoval
>
> The unit test requires x11 as distro feature, otherwise it will fail
> while building the test requirements.
>
How about changing the test recipe to something non-x11 instead?
>
> [YOCTO #10903]
>
> Signed-off-by: Leonardo Sandova
Remove the fake news about mkfontscale-native needing x11.
Signed-off-by: Jussi Kukkonen
---
meta/recipes-graphics/xorg-font/xorg-font-common.inc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/meta/recipes-graphics/xorg-font/xorg-font-common.inc
b/meta/recipes-graphics/xorg-font/xorg-fon
Build does not need libx11, so also does not need the distro feature.
Signed-off-by: Jussi Kukkonen
---
meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb
b/meta/recipes-graphics/xorg-app/mk
There seems to be no advantage to letting distro features affect
native builds. There is a significant disadvantage: a change to
DISTRO_FEATURES will trigger a lot of unnecessary native tasks. In a
test like this:
$ bitbake core-image-minimal
# append " systemd" to DISTRO_FEATURES
$ bitbake c
Build does not need libx11, so also does not need the distro feature.
Signed-off-by: Jussi Kukkonen
---
meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb
b/meta/recipes-graphics/xorg-app
Avoid signifant native task churn when DISTRO_FEATURES is changed
by defining a fixed DISTRO_FEATURES value (default is "") for native
recipes.
The xorg changes are all removals of x11 requirements (that were not
real) from recipes that have native versions.
I added a configuration default in bit
On Fri, 2017-04-07 at 08:38 +1200, Paul Eggleton wrote:
> On Thursday, 6 April 2017 1:36:05 AM NZST you wrote:
> >AssertionError: False is not true : Layer meta- changed 120
> > signatures, initial differences (first hash without, second with layer):
>
> BTW, rather than self.assertTrue(Fa
84 matches
Mail list logo
