> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Wednesday, November 01, 2017 16:35
> To: Huang, Jie (Jackie)
> Cc: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [PATCH 1/2] glibc: re-package for libnss-db
>
> On Tue, Oct 31, 2017 at 7:
From: Jackie Huang
v2 comments:
Add a note for external toolchain in the commit log.
--
The following changes since commit 514a808f21c37b6ad704ce397bb2740ecc9a93bc:
ref-manual: Updates to "Image Generation" section. (2017-10-30 15:55:08 +)
are available in the git repository at:
git:/
From: Jackie Huang
On other distros like ubuntu/centos, libnss-db usually provides:
- The libraries
- The Makefile to create database
(in /var/db for centos, /var/lib/misc/ for ubuntu)
- The makedb command (it's in glibc-common for centos7)
What we had is:
- The libraries are in glibc-extra-ns
From: Jackie Huang
We don't have /etc/netgroup by default, so do not
cache for netgroup by default to avoid:
nscd[529]: 529 disabled inotify-based monitoring for file `/etc/netgroup': No
such file or directory
nscd[529]: 529 stat failed for file `/etc/netgroup'; will try again later: No
such fi
Rich Felker (10):
fix use of memset without declaration in sched.h cpu set macros
fix access by setjmp and longjmp to __hwcap on arm built as thumb2
for executing init array functions, use function type with prototype
fix read-after-free type error in pthread_detach
fi
busybox init is not intended to be used with initscripts, which is for
sysvinit.
Please check packagegroup-core-boot.bb for more info.
Best Regards,
Chen Qi
On 11/01/2017 02:04 PM, wenzong@windriver.com wrote:
From: Wenzong Fan
* check for the existence of /etc/default/rcS
* minor fixes
On 11/01/2017 08:51 PM, Otavio Salvador wrote:
Hello,
On Wed, Nov 1, 2017 at 4:04 AM, wrote:
From: Wenzong Fan
Disable 'mountall.sh' to avoid system halt while the init manager is
set as 'busybox'.
In busybox init, the 'SIGUSR1' was handled as 'halt', calling to the
'mountall.sh' would t
On 1 November 2017 at 22:04, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2017-10-31 at 21:25 -0200, Otavio Salvador wrote:
> > On Tue, Oct 31, 2017 at 9:16 PM, Burton, Ross
> > wrote:
> > >
> > > On 21 October 2017 at 13:06, Richard Purdie
> > > wrote:
> > > >
> > > > d
When building for aarch64 (ie relying only on generic C code rather
than asm) libgmp.so contains undefined references to __gmpn_add_nc
and __gmpn_sub_nc which causes attempts to link with -lgmp to fail:
| .../usr/lib/libgmp.so: undefined reference to `__gmpn_sub_nc'
| .../usr/lib/libgmp.so: unde
== Series Details ==
Series: "[v7] wayland : Bump to version..." and 2 more
Revision: 1
URL : https://patchwork.openembedded.org/series/9586/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been e
This patch modify the way we manage wayland path issues.
Instead of patching each recipe to make it work with wayland and its protocols,
it is better to patch wayland to fix its path issues.
So wayland-scanner.pc, wayland-client.pc and wayland-protocols.pc are patched
to change paths.
Then we ca
Update weston release to 3.0.0.
Two patches added:
- fix-missing-header.patch:
fix a build issue when musl is used as libc.
- weston-gl-renderer-Set-pitch-correctly-for-subsampled-textures.patch:
fix display issue with YUV420/I420 format, that could result in a crash.
Signed-off-by
Signed-off-by: Fabien Lahoudere
---
.../recipes-graphics/wayland/{wayland_1.13.0.bb => wayland_1.14.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-graphics/wayland/{wayland_1.13.0.bb => wayland_1.14.0.bb}
(92%)
diff --git a/meta/recipes-graphics/wayland/way
Fixes the following issue when trying to build npm based recipes:
| npm ERR! As of npm@5, the npm cache self-heals from corruption issues and
data extracted from the cache is guaranteed to be valid. If you want to make
sure everything is consistent, use 'npm cache verify' instead.
| npm ERR! If y
On Tue, 2017-10-31 at 21:25 -0200, Otavio Salvador wrote:
> On Tue, Oct 31, 2017 at 9:16 PM, Burton, Ross
> wrote:
> >
> > On 21 October 2017 at 13:06, Richard Purdie
> > wrote:
> > >
> > > diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-
> > > internal
> > > index e6cd141..abc5
On 11/01/2017 06:28 PM, Catalin Enache wrote:
In the PatternMatch function in fontfile/fontdir.c in libXfont through 1.5.2
and 2.x before 2.0.2, an attacker with access to an X connection can cause
a buffer over-read during pattern matching of fonts, leading to information
disclosure or a crash (
On Wed, Nov 01, 2017 at 03:08:10PM +0100, Fabien Lahoudere wrote:
> On Tue, 2017-10-31 at 15:29 -0400, Denys Dmytriyenko wrote:
> > On Mon, Oct 30, 2017 at 02:30:08PM +0100, Fabien Lahoudere wrote:
> > > On Tue, 2017-10-17 at 15:00 -0400, Denys Dmytriyenko wrote:
> > > > I don't believe we reached
In the PatternMatch function in fontfile/fontdir.c in libXfont through 1.5.2
and 2.x before 2.0.2, an attacker with access to an X connection can cause
a buffer over-read during pattern matching of fonts, leading to information
disclosure or a crash (denial of service). This occurs because '\0'
cha
On 10/31/2017 03:15 AM, Markus Lehtonen wrote:
Hi,
Please see the 6th patch ("devtools/images: add python-pgo-image") in my
patchset for python-pgo-image.
I'd like the profiling to work out-of-the-box, without requiring some
strange-ish (i.e. modification of HOSTTOOLS) changes in local.conf.
T
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.
infact none of the build failures are due to musl lim
On 2017-11-01 04:38 AM, Alexander Kanavin wrote:
Their data is not of sufficient quality unfortunately. For Python they
report 3.7.0 as the latest version even though it won't be released
until june 2018. Python 2.x is neglected altogether. Latest 3.6 version
is 3.6.3 released a month ago, but
On Tue, 2017-10-31 at 15:29 -0400, Denys Dmytriyenko wrote:
> On Mon, Oct 30, 2017 at 02:30:08PM +0100, Fabien Lahoudere wrote:
> > On Tue, 2017-10-17 at 15:00 -0400, Denys Dmytriyenko wrote:
> > > I don't believe we reached an agreement on the pitch patch belonging
> > > here...
> > >
> >
> > T
Sanity check for future packages.
[YOCTO #10944]
Signed-off-by: Markus Lehtonen
---
meta/classes/update-alternatives.bbclass | 4
1 file changed, 4 insertions(+)
diff --git a/meta/classes/update-alternatives.bbclass
b/meta/classes/update-alternatives.bbclass
index 65cae7002f..aa01058cf9
This kludge is not needed anymore, now that syslog packages (or any
other package) don't use update-alternatives for managing SysV init
scripts.
This reverts commit fc89a3f739ff25306ea91d9bdb424fc8389bdf72.
[YOCTO #10944]
---
meta/classes/update-alternatives.bbclass | 29 +++-
Make lsbinitscripts (r)conflict with initscripts-functions package.
[YOCTO #10944]
Signed-off-by: Markus Lehtonen
---
meta/recipes-extended/lsb/lsbinitscripts_9.72.bb | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/meta/recipes-extended/lsb/lsbinitscripts_9.72.bb
b/
Using update-alternatives for managing init scripts has proved to be
problematic. And, sysklogd rconflicts with other syslog daemons so there
is no point in using update-alternatives from this perspective, either.
[YOCTO #10944]
Signed-off-by: Markus Lehtonen
---
meta/recipes-extended/sysklogd/
In order to make that the default provider for initd-functions.
[YOCTO #10944]
Signed-off-by: Markus Lehtonen
---
meta/recipes-core/initscripts/initscripts_1.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb
b/meta/recipes-core/initscri
Stop using update-alternatives for managing /etc/init.d/functions. Also,
make the initscripts-functions subpackage to (runtime) conflict with
lsbinitscripts.
[YOCTO #10944]
Signed-off-by: Markus Lehtonen
---
meta/classes/update-rc.d.bbclass | 3 +--
meta/conf/distro/include/defa
This patchset does away with the usage of update-alternatives for managing init
scripts. Using u-a for initscripts cause race/ordering issues with package
scriptlets doing daemon stop/start/enable at package installation time. The
patchset also reverts a kludge that was introduced in
update-alterna
On Tue, Oct 31, 2017 at 04:08:58PM +0100, Nicolas Dechesne wrote:
> On Tue, Oct 31, 2017 at 2:33 PM, Ed Bartosh
> wrote:
> >
> > On Mon, Oct 30, 2017 at 08:53:09PM +0100, Artur Mądrzak wrote:
> > > The WIC's 'part' can now give a name for GPT partition in WKS file.
> > > It's similar to '--label'
Hello,
On Wed, Nov 1, 2017 at 4:04 AM, wrote:
> From: Wenzong Fan
>
> Disable 'mountall.sh' to avoid system halt while the init manager is
> set as 'busybox'.
>
> In busybox init, the 'SIGUSR1' was handled as 'halt', calling to the
> 'mountall.sh' would trigger the signal with:
> + kill -USR1
Hi Armin,
I'll leave this question to Khem, this was my just 2nd build with musl,
Khem is doing musl builds for very long time and fixing all the issue he
finds, maybe some of the issues detected in world builds already have fixes
in Khem's queue.
Regards,
On Wed, Nov 1, 2017 at 5:53 AM, akuster
== Series Details ==
Series: wic: add 'part-name' argument for naming GPT
Revision: 1
URL : https://patchwork.openembedded.org/series/9571/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been exe
On 10/31/2017 11:03 PM, Randy MacLeod wrote:
On 2017-10-31 01:43 PM, Alexander Kanavin wrote:
This greatly reduces the amount of recipes for which upstream
version check fails: from about 30 to about 8.
Has anyone looked into piggy-backing off:
https://release-monitoring.org/
Currently 157
The WIC's 'part' can now give a name for GPT partition in WKS file.
It's similar to '--label', but is naming partintions instead file systems.
It's required by some bootloaders to partitions have specified names.
Signed-off-by: Artur Mądrzak
---
scripts/lib/wic/help.py | 2 ++
On Tue, Oct 31, 2017 at 7:03 PM, Huang, Jie (Jackie)
wrote:
>
>
>> -Original Message-
>> From: Khem Raj [mailto:raj.k...@gmail.com]
>> Sent: Wednesday, November 01, 2017 03:40
>> To: Huang, Jie (Jackie)
>> Cc: Patches and discussions about the oe-core layer
>> Subject: Re: [OE-core] [PATCH
On 10/31/2017 08:02 PM, Patchwork wrote:
* Issue Series does not apply on top of target branch
[test_series_merge_on_head]
Suggested fixRebase your series on top of targeted branch
Targeted branch master (currently at 3b413a8057)
This is because the patches need to be ap
37 matches
Mail list logo
