I have compared no/suid links between these versions. So, I was trying
to enable the same applets like in older version and do not enable the
new one. Some applets could not be disabled (they are automatically
enabled) due to dependencies.
For this version of defconfig the new applets are:
chrt
ct
On Tue, Oct 3, 2017 at 7:25 PM, Marek Vasut wrote:
> On 10/04/2017 04:01 AM, Andre McCurdy wrote:
>> On Tue, Oct 3, 2017 at 2:54 PM, Juro Bystricky
>> wrote:
>>> With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b
>>
>> That revision doesn't exist in oe-core...
>
it exists in poky, sometim
On 10/04/2017 04:01 AM, Andre McCurdy wrote:
> On Tue, Oct 3, 2017 at 2:54 PM, Juro Bystricky
> wrote:
>> With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b
>
> That revision doesn't exist in oe-core...
Also, isn't there some sort of standardized format for listing git
commit IDs in commi
On Tue, Oct 3, 2017 at 2:54 PM, Juro Bystricky wrote:
> With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b
That revision doesn't exist in oe-core...
> some nios2 builds
> (uboot, core-image-minimal, etc) were broken due to db trying to use ARM
> instructions
> in mutexes. The reason was d
The patch is uclibc specific and reference to it was removed from the
systemd recipe in:
http://git.openembedded.org/openembedded-core/commit/?id=653704e9cf325cb494eb23facca19e9f05132ffd
Signed-off-by: Andre McCurdy
---
...r-getty-to-agetty-in-console-setup-system.patch | 44
On Fri, 2017-09-29 at 14:15 +, Matt Madison wrote:
> When building for a target whose architecture matches
> the build host's, the second pass through make.bash
> to build the shareable runtime would also overwrite
> the target's static cgo library with host-compatibile
> binaries.
>
> Fix thi
On Fri, 2017-09-29 at 14:15 +, Matt Madison wrote:
> When building for a target whose architecture matches
> the build host's, the second pass through make.bash
> to build the shareable runtime would also overwrite
> the target's static cgo library with host-compatibile
> binaries.
>
> Fix thi
With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b some nios2 builds
(uboot, core-image-minimal, etc) were broken due to db trying to use ARM
instructions
in mutexes. The reason was db "configure" used the cached entry from nios2-linux
(which was incorrect). So the remedy was to remove the i
On 10/03/2017 10:44 PM, Bystricky, Juro wrote:
>
>> While I understand ARM/ is wrong, why is removing the db_cv_mutex a
>> correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
>> explain that.
>
> With the relatively recent commit
> http://git.yoctoproject.org/cgit.cgi/poky/c
> While I understand ARM/ is wrong, why is removing the db_cv_mutex a
> correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
> explain that.
With the relatively recent commit
http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/recipes-support/db?id=f4e8e9242c5df095b52688b08
On 10/03/2017 09:51 PM, Juro Bystricky wrote:
> This fixes broken nios2 builds that involve db recipes.
While I understand ARM/ is wrong, why is removing the db_cv_mutex a
correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
explain that.
> Signed-off-by: Juro Bystricky
> ---
This fixes broken nios2 builds that involve db recipes.
Signed-off-by: Juro Bystricky
---
meta/site/nios2-linux | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/site/nios2-linux b/meta/site/nios2-linux
index 2f4e570..5bae748 100644
--- a/meta/site/nios2-linux
+++ b/meta/site/nios2-linux
@
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks !!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||all ||already-stripped ||libdir
||textrel ||build-deps ||file-rdep
I just stumbled upon something odd in package.bbclass. In commit
ede381d5 from January 2011 (the code hasn't changed since), the
use of the ${PACKAGELOCK} lock file was changed to shared to
improve parallelism. However, when looking at the actual change
it becomes confusing. I have included it
On Tue, Oct 3, 2017 at 8:38 AM, Andrej Valek wrote:
> Update busybox to version 1.27.2
> Fix CVE-20177-5325
>
> Changes:
> - busybox: 1.24.1 -> 1.27.2:
> - fixed link creation to shell
> - reported bug with suid shells
> [https://bugs.busybox.net/show_bug.cgi?id=10346]
> - removed and modifie
On 10/03/2017 06:03 PM, jef.drie...@niko.eu wrote:
Burton, Ross [ross.bur...@intel.com]
On 3 October 2017 at 11:03, wrote:
Note: base-files-emperor is the package with the custom init scripts. I added:
PROVIDES = "initscripts"
And in conf/machine/emperor.conf, I added:
PREFERRED_PROVIDER_in
- fixed link creation to shell
- reported bug with suid shells
[https://bugs.busybox.net/show_bug.cgi?id=10346]
- removed and modified already merged patches
- updated defconfig regarding to new version
Signed-off-by: Andrej Valek
Signed-off-by: Radovan Scasny
---
...ss-interface-device-name-
Update busybox to version 1.27.2
Fix CVE-20177-5325
Changes:
- busybox: 1.24.1 -> 1.27.2:
- fixed link creation to shell
- reported bug with suid shells
[https://bugs.busybox.net/show_bug.cgi?id=10346]
- removed and modified already merged patches
- updated defconfig regarding to new version
Signed-off-by: Radovan Scasny
Signed-off-by: Andrej Valek
---
.../busybox/busybox/CVE-2011-5325.patch| 481 +
meta/recipes-core/busybox/busybox_1.27.2.bb| 1 +
2 files changed, 482 insertions(+)
create mode 100755 meta/recipes-core/busybox/busybox/CVE-2
Burton, Ross [ross.bur...@intel.com]
> On 3 October 2017 at 11:03, wrote:
>> Note: base-files-emperor is the package with the custom init scripts. I
>> added:
>>
>> PROVIDES = "initscripts"
>>
>> And in conf/machine/emperor.conf, I added:
>>
>> PREFERRED_PROVIDER_initscripts = "base-files-emperor
On 3 October 2017 at 11:03, wrote:
>
> Note: base-files-emperor is the package with the custom init scripts. I
> added:
>
> PROVIDES = "initscripts"
>
> And in conf/machine/emperor.conf, I added:
>
> PREFERRED_PROVIDER_initscripts = "base-files-emperor"
>
If your initscripts package is a replace
> I'd definitely be curious as to where initscripts is coming from in the SDK.
> You can use bitbake -g to generate dependency charts.
There are quite some packages which depend on initscripts:
$ bitbake -g image-sdk-niko -c populate_sdk
NOTE: Started PRServer with DBfile:
/home/jdi/develop/y
Alexander Kanavin:
> You can use bbappend to instead replace the standard files with the ones
> that you want installed. Or you can add PROVIDES = "initscripts" to your
> recipe with the 'custom' initscripts, and set
> PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that
> installe
Remember to upgrade dbus-test at the same time as otherwise you break
dbus-test.
Ross
On 21 September 2017 at 08:46, Fan Xin wrote:
> Upgrade dbus from 1.10.20 to 1.10.22
>
> Signed-off-by: fan@jp.fujitsu.com
> ---
> meta/recipes-core/dbus/dbus_1.10.20.bb | 180
> --
> -Original Message-
> From: Fupan Li
>
> The patch recipes-core/openjdk/patches-openjdk-8/openjdk8-fix-adlc-
> flags.patch
> had tried to fix this issue, and it tried to filter out the
> TARGET_FLAGS/TARGET_
> CXXFLGAS, but for the flags such as "-fno-lifetime-dse" was added to
> CFLAGS/
After 02457ef7f600ce954874e2d11e74b1c6daaa3bfc, PSEUDO for
postinst-useradd-* scripts get to use only one PSEUDO_LOCALSTATEDIR
which is set under recipes ${WORKDIR}.
When the those scripts are run in a clean build environment that
is built from the sstate (populate_sysroot_setscene run for
postins
26 matches
Mail list logo
