On Thu, Sep 15, 2016 at 4:41 AM, Burton, Ross wrote:
>
> On 12 September 2016 at 07:13, Sujith H wrote:
>
>> +# PIC can't be enabled for 32-bit x86 and cyclone5
>> INSANE_SKIP_${PN}_append_x86 = " textrel"
>> +INSANE_SKIP_${PN}_append_cyclone5 = "
On 2016-09-14 04:46 PM, Bystricky, Juro wrote:
I am pretty sure I glimpsed the messages:
Child process timeout after 2 seconds.
Child process exit status 4: lock_held
on several occasions recently, just before my Xserver was restarted and I was
kicked back to the login prompt.
I
On Wed, Sep 14, 2016 at 10:01:01PM +0100, Burton, Ross wrote:
> On 14 September 2016 at 18:12, Patrick Williams wrote:
>
> > mkfs.minix and fsck.minix are likely rarely used, so split
> > them into their own packages to reduce the footprint of
> > util-linux. This follows the
On Wed, Sep 14, 2016 at 11:23:47PM +0200, Martin Jansa wrote:
> It was also proposed and discussed some 15 months ago and it was packaging
> issue not handling hardlinks correctly:
> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/103939.html
>
> I believe this was fixed
Note that we're past M3 now, so this will have to wait until 2.3.
Ross
On 14 September 2016 at 15:25, Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:
> On Wed, Sep 14, 2016 at 9:30 AM, Fabio Berton
> wrote:
> > * Remove patch maxsize.patch already
Due to the variable IMGDEPLOYDIR being recently re-defined, the Build Appliance
image
ended up being created in a wrong location.
This patch assures the final ZIP image is created in identical location as
before:
tmp/deploy/images//Yocto_Build_Apliance.zip
[YOCTO#10274]
Signed-off-by:
On 12 September 2016 at 07:13, Sujith H wrote:
> +# PIC can't be enabled for 32-bit x86 and cyclone5
> INSANE_SKIP_${PN}_append_x86 = " textrel"
> +INSANE_SKIP_${PN}_append_cyclone5 = " textrel"
>
Can this be generalised or is it absolutely specific to cyclone5? If it
Previous work to clean up the license QA code (oe-core fbdf977) had the side
effect that failing the license sanity check (bad or missing LIC_FILES_CHKSUM)
would emit an error message but wouldn't actually abort the build.
Solve this by changing populate_lic_qa_checksum() so that it tracks if the
To help debug failures, redirect stderr to stdout in oeSDKTest.run() and
oeSDKExtTest.run().
Signed-off-by: Ross Burton
---
meta/lib/oeqa/oetest.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oeqa/oetest.py b/meta/lib/oeqa/oetest.py
It was also proposed and discussed some 15 months ago and it was packaging
issue not handling hardlinks correctly:
http://lists.openembedded.org/pipermail/openembedded-core/2015-April/103939.html
I believe this was fixed then, but maybe it got broken again?
On Wed, Sep 14, 2016 at 9:50 PM, André
On 14 September 2016 at 22:06, Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:
> Ok; but this means it should be right?
>
> If so, we can work on a recipe for it. It is better to avoid bundled
> copies of recipe specially because security flaws...
>
Nothing else wants it, cmake ships
On Wed, Sep 14, 2016 at 5:59 PM, Burton, Ross wrote:
>
> On 14 September 2016 at 18:50, Otavio Salvador
> wrote:
>>
>> Why jsoncpp cannot be also linked?
>
> Because it's not in oe-core.
Ok; but this means it should be right?
If so, we
On 14 September 2016 at 18:12, Patrick Williams wrote:
> mkfs.minix and fsck.minix are likely rarely used, so split
> them into their own packages to reduce the footprint of
> util-linux. This follows the pattern of cramfs support
> within util-linux.
>
Minix is so unlikely
On 14 September 2016 at 18:50, Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:
> Why jsoncpp cannot be also linked?
>
Because it's not in oe-core.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
I am pretty sure I glimpsed the messages:
Child process timeout after 2 seconds.
Child process exit status 4: lock_held
on several occasions recently, just before my Xserver was restarted and I was
kicked back to the login prompt.
I typically ran several parallel bitbake
On 9/14/16 5:34 AM, Sona Sarmadi wrote:
> The upgrade addresses CVE-2016-3116:
>
> - Validate X11 forwarding input. Could allow bypass of
> authorized_keys command= restrictions,
> found by github.com/tintinweb.
> Thanks for Damien Miller for a patch. CVE-2016-3116
thanks,
I will pull this
On 9/14/16 2:43 AM, Richard Purdie wrote:
> On Wed, 2016-09-14 at 12:06 +0300, Alexander Kanavin wrote:
>> On 09/14/2016 11:49 AM, Sona Sarmadi wrote:
>>> https://matt.ucc.asn.au/dropbear/CHANGES
>>> .
>>> 2016.72 - 9 March 2016<<< dropbear version this CVE has
>>> been fixed
>>> -
On 14 Sep 2016 5:40 p.m., "Patrick Williams" wrote:
>
> The /sbin/fsck.ext[234] programs currently installed are all
> the same binary as e2fsck. The package provides an option to
> have fsck.ext[234] be symlinked to /sbin/e2fsck instead. This
> reduces the uncompressed
On Wed, Sep 14, 2016 at 1:41 PM, Ross Burton wrote:
> The intention here was "everything but jsoncpp is system provided" so use the
> convenience option to ensure this remains true in the future.
>
> Signed-off-by: Ross Burton
Why jsoncpp cannot be
When building busybox, an occasional error was observed.
The error is consistently the same:
libbb/appletlib.c:164:13: error: 'NUM_APPLETS' undeclared (first use in this
function)
while (i < NUM_APPLETS) {
The reason is the include file where NUM_APPLETS is defined is not yet
generated (or
(Resending updated patches... hopefully got it right this time)
There is an occasional race observed when building Busybox.
It has been discussed on Busybox mailing list (see:
https://www.mail-archive.com/busybox@busybox.net/msg23244.html )
There were several Busybox attempts to fix this issue:
MIPS64 target was being configured for linux-mips which defaults to
MIPS32. Doesn't cause any issue as far as I can see but it would be
wiser to use the correct target configuration.
Also add MIPS64le configuration which is missing.
Signed-off-by: Zubair Lutfullah Kakakhel
The intention here was "everything but jsoncpp is system provided" so use the
convenience option to ensure this remains true in the future.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/cmake/cmake_3.6.1.bb | 9 ++---
1 file changed, 2 insertions(+), 7
By default cmake will auto-detect if a library is present on the host and if it
isn't present will use an internal fork. For some libraries using the internal
fork is preferable as it can be built with less dependencies, but for others
we're either already building it or the impact of building it
cmake doesn't use autotools, the functions get replaced by either cmake.bbclass
(target) or the recipe itself (native) leaving just lots of superfluous
dependencies.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/cmake/cmake-native_3.6.1.bb | 15 +++
On 14 September 2016 at 12:24, Markus Lehtonen <
markus.lehto...@linux.intel.com> wrote:
> +if not tasks1:
> +pkg_op = '++'
> +elif not tasks2:
> +pkg_op = '--'
>
BTW, I've been reading buildstats-diff output all day and find the lack of
whitespace between
On Wed, Sep 14, 2016 at 9:30 AM, Fabio Berton
wrote:
> * Remove patch maxsize.patch already applied upstream.
>
> * Add patch Skip-empty-section-fixes-66.patch to prevent errors like:
>
> /
> |ERROR: go-cross-1.6.2-r0 do_populate_sysroot_setscene:
>
On 09/14/2016 02:56 AM, Robert Yang wrote:
On 09/14/2016 02:32 PM, Bruce Ashfield wrote:
On 09/13/2016 10:21 PM, Robert Yang wrote:
Hi Bruce,
All the kernel 4.1 and 4.4 buildings are down on autobuilder:
From: Christian Schuler
The ${WORKDIR}/git refers to the source folder S which is different in
the case of an external source build.
Signed-off-by: Christian Schuler
Signed-off-by: Pascal Bach
---
The upgrade addresses CVE-2016-3116:
- Validate X11 forwarding input. Could allow bypass of
authorized_keys command= restrictions,
found by github.com/tintinweb.
Thanks for Damien Miller for a patch. CVE-2016-3116
References:
https://matt.ucc.asn.au/dropbear/CHANGES
* Remove patch maxsize.patch already applied upstream.
* Add patch Skip-empty-section-fixes-66.patch to prevent errors like:
/
|ERROR: go-cross-1.6.2-r0 do_populate_sysroot_setscene:
'('patchelf-uninative',
|'--set-interpreter', '/home/user/src/prj/build/tmp/sysroots-uninative/
On 14 September 2016 at 06:08, wrote:
> * Added libs:
> - container
> - context
> - coroutine
> - exception
> - graph_parallel
> - locale
> - math
> - mpi
> - wave
>
I don't see packages created for mpi, graph_parallel or exception. Is this
When 'git request-pull' fails it makes sense to remove output
directory. Otherwise create-pull-request will complain that
output directory already exists on the next run.
Signed-off-by: Ed Bartosh
---
scripts/create-pull-request | 1 +
1 file changed, 1 insertion(+)
New script for comparing buildstats from two separate builds. The script
has two modes: normally it prints the differences in task execution
(cpu) times but using --ver-diff option makes it just print the recipe
version differences without any cpu time data. Other command line
options are provided
On 09/14/2016 01:24 PM, Sona Sarmadi wrote:
Thanks guys for your feedbacks. I agree that by default we shouldn't upgrade
package
versions in stable branches as far as possible but sometimes we have to. If
there isn't a
suitable patch I personally prefer upgrading (only if it is minor changes)
> >> That said, I vote for updating to the version that comes with the
> >> fix.
> >> Backporting fixes should not be the default in the stable yocto
> >> releases; we should trust the upstream more.
> >
> > Taking that argument to the extreme, we should update all versions in
> > the "stable"
On 09/14/2016 12:43 PM, Richard Purdie wrote:
That said, I vote for updating to the version that comes with the
fix.
Backporting fixes should not be the default in the stable yocto
releases; we should trust the upstream more.
Taking that argument to the extreme, we should update all versions
On 13 September 2016 at 22:52, Juro Bystricky
wrote:
> +++ b/meta/recipes-core/busybox/busybox/busybox-kbuild-race-
> fix-commit-d8e61bb.patch
> @@ -0,0 +1,45 @@
> +From d8e61bbf13d0cf38d477255cfd5dc71c5d51d575 Mon Sep 17 00:00:00 2001
> +From: Denys Vlasenko
The following changes since commit 4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac:
oeqa.runtime.smart: work around smart race issues (2016-09-09 12:12:17 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/rq
There might be a race issue when multi runqemu processess are
running at the same time:
| Traceback (most recent call last):
| File
"/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-ipk/build/scripts/runqemu",
line 920, in
| ret = main()
| File
On Wed, 2016-09-14 at 12:06 +0300, Alexander Kanavin wrote:
> On 09/14/2016 11:49 AM, Sona Sarmadi wrote:
> >
> > https://matt.ucc.asn.au/dropbear/CHANGES
> > .
> > 2016.72 - 9 March 2016<<< dropbear version this CVE has
> > been fixed
> > - Validate X11 forwarding input. Could allow
On 09/14/2016 11:49 AM, Sona Sarmadi wrote:
https://matt.ucc.asn.au/dropbear/CHANGES
.
2016.72 - 9 March 2016<<< dropbear version this CVE has been fixed
- Validate X11 forwarding input. Could allow bypass of authorized_keys command=
restrictions,
found by github.com/tintinweb.
Hi guys,
I need your advice how to address this CVE in krogoth (master is not affected)
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3116
I couldn't find a patch for this specific CVE in dropbear git or somewhere
else, if we want to address this issue it seems that we need to update
On 09/04/2016 07:21 PM, Marek Vasut wrote:
Upgrade U-Boot to the latest version.
The latest version meanwhile changed to 2016.09, can you update to that?
Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
Use md5 sum instead of mtime as the "digest" method for rpm_sys channel.
The digest is used to determine if the channel has been updated. It was
found out that mtime was not a reliable digest. On some systems mtime
of the rpm db does not get updated after every transaction if transactions
(smart
When reading smartpm sources more closely I found out that it has an internal
utility function for doing file hashes. It does hashing in a more memory
efficient way, processing the file in chunks. Thus, it is better to use it
instead of blindly reading the whole file into memory as v1 of this
On 09/14/2016 02:32 PM, Bruce Ashfield wrote:
On 09/13/2016 10:21 PM, Robert Yang wrote:
Hi Bruce,
All the kernel 4.1 and 4.4 buildings are down on autobuilder:
On 09/13/2016 10:21 PM, Robert Yang wrote:
Hi Bruce,
All the kernel 4.1 and 4.4 buildings are down on autobuilder:
48 matches
Mail list logo