On 2020-03-27 18:25, Alex Kiernan wrote:
> udev is packaged before systemd so any wildcard inclusions in FILES will
> override later specifics. List all udev rules explicitly so that the
> systemd specific rules, packaged alongside systemd, appear in the
> correct package.
>
> Signed-off-by: Alex
I guess I should have prefixed that one with [pseudo].
--
Stefan
On 2020-07-20 11:02, Patchwork wrote:
> == Series Details ==
>
> Series: Handle OFD lock flags (rev2)
> Revision: 2
> URL : https://patchwork.openembedded.org/series/15665/
> State : failure
>
> == Summary ==
>
>
> Thank you f
F_GETLK (and friends).
This issue has been observed with ostree. Comparing strace output
between two runs with/without this patch shows the same fcntl calls,
hence it seems not to matter in practice.
Signed-off-by: Stefan Agner
---
ports/linux/guts/fcntl.c | 5 +
1 file changed, 5 insertions
On 2020-06-16 11:50, Quentin Schulz wrote:
> Hi all,
>
> On Wed, Jan 22, 2020 at 11:06:55AM +0100, Quentin Schulz wrote:
>> > > The reason why I didn't bother to send a patch to busybox before pinging
>> > > on this patch was that we're already different from the upstream
>> > > simple.script
>>
From: Stefan Agner
Instead of checking for existence of /dev in the mounted file system use
mountpoint to check if a root file system has been mounted. This allows
to use the rootfs module for OSTree based rootfs as well, where the file
system rootfs does not have any of the regular directories
From: Ming Liu
do_kernel_checkout and do_symlink_kernsrc are both modifying ${S}, they
could conflict with eacher other, move do_kernel_checkout after
do_symlink_kernsrc does fix that.
Signed-off-by: Ming Liu
Signed-off-by: Stefan Agner
---
meta/classes/kernel-yocto.bbclass | 2 +-
1 file
From: Stefan Agner
Make use of the recently added systemd support in psplash. The utility
psplash-systemd communicates boot progress to the splash screen. The
splash is disabled once systemd consideres the system fully booted
(progress is at 1.0). Note that this can take a while if systemd is
On 2020-01-20 13:32, Quentin Schulz wrote:
> Hi all,
>
> On Mon, Jan 13, 2020 at 03:57:31PM +0100, Quentin Schulz wrote:
>> Hi all,
>>
>> On Mon, May 14, 2018 at 04:44:15PM +0200, Stefan Agner wrote:
>> > From: Stefan Agner
>> >
>> >
accidentally).
--
Stefan
On 2019-11-20 13:41, Stefan Agner wrote:
> From: Stefan Agner
>
> Add Zstandard (or just Zstd) compression support. This allows to
> create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
>
> Signed-off-by: Stefan Agner
> ---
> meta/cla
Hi,
tl;dr: Afaict, using DATETIME in PV is currently impossible due to
commit 9ca2fad2 ("image: Expand PV to avoid AUTOREV parsing failures").
Do not use DATETIME in PV.
In an effort to use timestamps for development builds we tried to use
DATETIME in the PV variable of an image recipe (basicall
Hi,
On 2019-11-15 17:09, Stefan Agner wrote:
> From: Stefan Agner
>
> Make sure that the (newer) /dev/pts/ptmx is accessible by users. This
> is useful e.g. when running containers which symlink /dev/ptmx to
> /dev/pts/ptmx on start. The default mode (000) does not allow to
>
From: Stefan Agner
Use upstream systemd service files instead of our own service files.
This also makes sure that /run/rpcbind.sock is used which fixes the
following systemd warning:
/usr/lib/systemd/system/rpcbind.socket:5: ListenStream= references a
path below legacy directory /var/run
From: Stefan Agner
Add Zstandard (or just Zstd) compression support. This allows to
create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
Signed-off-by: Stefan Agner
---
meta/classes/image_types.bbclass | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a
From: Stefan Agner
Zstd is a very fast compression algorithm and has gained quite some
popularity recently. An upcoming patch allows to compress rootfs
using Zstd. Moving Zstd to oe-core allows this new conversion formats
to be automatically tested by the oe-selftest
On 2019-11-20 11:49, Alex Kiernan wrote:
> On Wed, Nov 20, 2019 at 9:13 AM Stefan Agner wrote:
>>
>> From: Stefan Agner
>>
>> Add Zstandard (or just Zstd) compression support. This allows to
>> create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
From: Stefan Agner
Zstd is a very fast compression algorithm and has gained quite some
popularity recently. An upcoming patch allows to compress rootfs
using Zstd. Moving Zstd to oe-core allows this new conversion formats
to be automatically tested by the oe-selftest
From: Stefan Agner
Add Zstandard (or just Zstd) compression support. This allows to
create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
Signed-off-by: Stefan Agner
---
meta/classes/image_types.bbclass | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a
On 2019-11-19 17:18, Alex Kiernan wrote:
> On Mon, Nov 18, 2019 at 6:39 PM Stefan Agner wrote:
>>
>> [adding Alex, he maintained the recipe in meta-oe so far]
>>
>> On 2019-11-18 13:19, Richard Purdie wrote:
>> > On Thu, 2019-11-14 at 15:47 +0100, Stefan Ag
[adding Alex, he maintained the recipe in meta-oe so far]
On 2019-11-18 13:19, Richard Purdie wrote:
> On Thu, 2019-11-14 at 15:47 +0100, Stefan Agner wrote:
>> On 2019-11-08 10:14, Stefan Agner wrote:
>> > From: Stefan Agner
>> >
>> > Zstd is a very fast
On 2019-11-18 17:53, Ross Burton wrote:
> On 18/11/2019 16:47, akuster808 wrote:
>> Does a possible Poky LTS have any factor in deciding to add more
>> packages to core?
>
> Even without the LTS there's a (relatively) long-term commitment to
> maintain recipes.
>
> Personally, I'm happy with Zstd
From: Stefan Agner
Make sure that the (newer) /dev/pts/ptmx is accessible by users. This
is useful e.g. when running containers which symlink /dev/ptmx to
/dev/pts/ptmx on start. The default mode (000) does not allow to
create ptys inside the container.
Using 666 when symlinking /dev/ptmx is
On 2019-11-08 10:14, Stefan Agner wrote:
> From: Stefan Agner
>
> Zstd is a very fast compression algorithm and has gained quite some
> popularity recently. An upcoming patch allows to compress rootfs
> using Zstd. Moving Zstd to oe-core allows this new conversion formats
> t
From: Stefan Agner
The whole D-Bus source has no reference to the netdev group. It
seems that the netdev group is nowhere used. Early avahi package
versions used this group for the D-Bus specific rules. However,
today avahi uses --with-avahi-priv-access-group=adm and hence
uses the adm group for
From: Stefan Agner
Add Zstandard (or just Zstd) compression support. This allows to
create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
Signed-off-by: Stefan Agner
---
meta/classes/image_types.bbclass | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a
From: Stefan Agner
Zstd is a very fast compression algorithm and has gained quite some
popularity recently. An upcoming patch allows to compress rootfs
using Zstd. Moving Zstd to oe-core allows this new conversion formats
to be automatically tested by the oe-selftest
On 2019-11-07 09:01, Richard Purdie wrote:
> On Wed, 2019-11-06 at 13:43 +0000, Stefan Agner wrote:
>> From: Stefan Agner
>>
>> Add Zstandard (or just Zstd) compression support. This allows to
>> create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
>&g
From: Stefan Agner
Add Zstandard (or just Zstd) compression support. This allows to
create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
Signed-off-by: Stefan Agner
---
meta/classes/image_types.bbclass | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a
Hi Andre,
On 2019-11-06 02:25, Andre McCurdy wrote:
> On Tue, Nov 5, 2019 at 3:13 PM Stefan Agner wrote:
>>
>> From: Stefan Agner
>>
>> Add Zstandard (or just Zstd) compression support. This allows to
>> create Zstd compressed tarballs by using tar.zst as I
From: Stefan Agner
Add Zstandard (or just Zstd) compression support. This allows to
create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
Signed-off-by: Stefan Agner
---
meta/classes/image_types.bbclass | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a
Also add Richard.
On 2019-10-11 11:06, Stefan Agner wrote:
> From: Stefan Agner
>
> In case multiple builds share UNINATIVE_DLDIR's location, one build
> might be in the process of downloading the tarball while another is
> just checking whether the tarball exists. Che
From: Stefan Agner
In case multiple builds share UNINATIVE_DLDIR's location, one build
might be in the process of downloading the tarball while another is
just checking whether the tarball exists. Check for the done file
instead and rely on the fetchers lockfile mechanism in case two
build
On 2019-10-11 10:26, Stefan Agner wrote:
> On 2019-10-07 18:47, Michael Halstead wrote:
>> The 2.7 release updates glibc to version 2.30. Recently added to openSUSE
>> Tumbleweed and needed for Fedora Core 31.
>
> Since we updated master to include this commit we see re
On 2019-10-07 18:47, Michael Halstead wrote:
> The 2.7 release updates glibc to version 2.30. Recently added to openSUSE
> Tumbleweed and needed for Fedora Core 31.
Since we updated master to include this commit we see regularly the following
issues:
WARNING: Disabling uninative as unable to ins
Hi all,
As an on and off contributor I rely on the instructions in the OE wiki.
Unfortunately the example for meta-oe is just next of an example using
the openembedded-core@lists.openembedded.org. Maybe the second example
should contain the correct address for meta-oe as well?
http://www.openembed
From: Stefan Agner
The systemd service points ot a script which is not installed by
zram or any of its dependencies. It seems that the service got
migrated without the necessary script.
The sysvinit script seems rather dated and initializes multiple
zram instances to support multiprocessor
On 2019-09-17 15:10, Andrew F. Davis via Openembedded-core wrote:
> The dependency is for EGL and GLES2 libraries. On some systems these
> are not provided by Mesa, list what is actually needed so the system
> can choose the correct provider.
Unfortunately I saw that a bit late, but this is breaki
d to me. I like the fact that this patch
mostly migrates 1:1 to Meson without changing anything else.
--
Stefan
> - Introduce remoting package config, without it meson would run into a
> build error.
>
> Signed-off-by: Stefan Agner
> Signed-off-by: Ming Liu
> ---
>
On 2019-07-25 14:21, Burton, Ross wrote:
> On Thu, 25 Jul 2019 at 12:42, wrote:
>> - Introduce remoting package config, without it meson would run into a
>> build error.
What do you mean by that exactly, I guess it does build at all with
remoting, and by introducing a packaging config you disab
From: Stefan Agner
The psplash binary uses TMPDIR as directory to store the FIFO to
communicate with the psplash tools. This directory can be in any
location an init system determines to be suitable, psplash-init
uses /mnt/ for it. Rather than creating the mount directory in
the recipe, just
From: Stefan Agner
The psplash binary uses TMPDIR as directory to store the FIFO to
communicate with the psplash tools. This directory can be in any
location an init system determines to be suitable, psplash-init
uses /mnt/ for it. Rather than creating the mount directory in
the recipe, just
Hi,
Any comment on this patch? Just stumbled upon that problem today again
:-)
--
Stefan
On 14.05.2018 16:44, Stefan Agner wrote:
> From: Stefan Agner
>
> The udhcpc script calls ip addr flush .. which flushes addresses
> of any address family, including IPv6. However, busyb
mtime to prevent failures like this.
FWIW,
Acked-by Stefan Agner
I fixed this in master, and it actually helps us resolving issues we see
on CI on thud branch.
--
Stefan
>
> Signed-off-by: Ming Liu
> ---
> ...pkg-make-index-use-ctime-instead-of-mtime.patch | 59
> +
-gnueabi/psplash/0.1+gitAUTOINC+2015f7073e-r15/torizon-blue-img.h'
Note that the error is somewhat misleading since the real problem
happened in the convert script, where the header did not get created due
to gdk-pixbuf-csource not recognizing the png file (Couldn't recognize
the image file f
On 01.03.2019 20:15, Stefan Agner wrote:
> On 23.02.2019 13:29, Richard Purdie wrote:
>> On Wed, 2019-02-20 at 21:10 +0100, Alexander Kanavin wrote:
>>> Drop autotools-specific patches.
>>>
>>> Rework jku's thumbnailer patch into meson configuration.
From: Stefan Agner
With 2.38.0 gdk-pixbuf dopped the enable_ prefix from the Meson
build options.
Signed-off-by: Stefan Agner
---
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.38.0.bb | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/recipes-gnome/gdk-pixbuf/gdk
From: Stefan Agner
Simplify make-image-header.sh call and make sure it gets called in
the current working directory. Also check the return value of the
function call.
Signed-off-by: Stefan Agner
---
meta/recipes-core/psplash/psplash_git.bb | 6 +++---
1 file changed, 3 insertions(+), 3
On 23.02.2019 13:29, Richard Purdie wrote:
> On Wed, 2019-02-20 at 21:10 +0100, Alexander Kanavin wrote:
>> Drop autotools-specific patches.
>>
>> Rework jku's thumbnailer patch into meson configuration.
>>
>> Signed-off-by: Alexander Kanavin
>
> We've seen it before but its happened again:
>
>
From: Stefan Agner
Enable polkit depending on whether polkit distro feature is set.
Signed-off-by: Stefan Agner
---
meta/recipes-support/consolekit/consolekit_0.4.6.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/consolekit/consolekit_0.4.6.bb
b
From: Stefan Agner
PolicyKit has been renamed to Polkit since quite a while. Rename
the PACKAGECONFIG accordingly.
Signed-off-by: Stefan Agner
---
meta/recipes-gnome/gnome/gconf_3.2.6.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-gnome/gnome
From: Stefan Agner
Enable polkit depending on whether polkit distro feature is set.
Signed-off-by: Stefan Agner
---
meta/recipes-gnome/gnome/gconf_3.2.6.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-gnome/gnome/gconf_3.2.6.bb
b/meta/recipes-gnome/gnome
From: Stefan Agner
This patchset adds Polkit (formerly known as PolicyKit) as a distro feature.
Polkit is used to centrally manage system policies and allows non-privileged
processes access privileged operations.
Since various packages such as systemd, ConnMan or NetworkManager allow building
From: Stefan Agner
PolicyKit has been renamed to Polkit since quite a while. Rename
the PACKAGECONFIG accordingly.
Signed-off-by: Stefan Agner
---
meta/recipes-support/consolekit/consolekit_0.4.6.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support
From: Stefan Agner
Only add polkit to PACKAGECONFIG if polkit is in DISTRO_FEATURES.
Signed-off-by: Stefan Agner
---
meta/recipes-core/systemd/systemd_239.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd_239.bb
b/meta/recipes-core
F_GETLK (and friends).
This issue has been observed with ostree. Comparing strace output
between two runs with/without this patch shows the same fcntl calls,
hence it seems not to matter in practice.
Signed-off-by: Stefan Agner
---
Hi,
I noticed this when using meta-updater which uses ostree to
question: Is there a new release of opkg-utils planned
anytime soon? Or should that be added as a patch in the OE recipe for
now?
--
Stefan
>
> On 10/19/18 10:38 AM, Stefan Agner wrote:
>> From: Stefan Agner
>>
>> When using sstate, two parallel builds can produce two
On 01.11.2018 23:27, Stefan Agner wrote:
> On 29.10.2018 14:01, Khem Raj wrote:
>> On Mon, Oct 29, 2018 at 5:31 AM Stefan Agner wrote:
>>>
>>> Hi,
>>>
>>> We use meta-updater, which has a custom FSTYPE to build a OSTree
>>> repository. We sh
On 29.10.2018 14:01, Khem Raj wrote:
> On Mon, Oct 29, 2018 at 5:31 AM Stefan Agner wrote:
>>
>> Hi,
>>
>> We use meta-updater, which has a custom FSTYPE to build a OSTree
>> repository. We share that repository across multiple bitbake executions.
>> The
Hi,
We use meta-updater, which has a custom FSTYPE to build a OSTree
repository. We share that repository across multiple bitbake executions.
The underlying OSTree tools lock the OSTree repository before trying to
interact, and if it fails ("error: Locking repo exclusive failed:
Resource temporari
From: Stefan Agner
When using sstate, two parallel builds can produce two packages
with the same mtime but different checksums. When later one of
those two builds fetches the others ipk, the package index does
not get udpated properly (since mtime matches). This ends up with
messages such as
On 02.10.2018 15:12, Stefan Agner wrote:
> On 02.10.2018 10:46, Stefan Agner wrote:
>> On 26.09.2018 11:34, Stefan Agner wrote:
>>> Hi,
>>>
>>> On 12.09.2018 00:49, Stefan Agner wrote:
>>
>>> We discussed the issue at Linaro Connect a bit.
&g
From: Stefan Agner
Replace the remaining hardcoded '/lib' in kernel firmware installation
path with ${nonarch_base_libdir}.
Signed-off-by: Stefan Agner
---
meta/recipes-kernel/linux-firmware/linux-firmware_git.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --
On 02.10.2018 10:46, Stefan Agner wrote:
> On 26.09.2018 11:34, Stefan Agner wrote:
>> Hi,
>>
>> On 12.09.2018 00:49, Stefan Agner wrote:
>
>> We discussed the issue at Linaro Connect a bit.
>>
>> To recap, we do build in two steps:
>>
>
On 26.09.2018 11:34, Stefan Agner wrote:
> Hi,
>
> On 12.09.2018 00:49, Stefan Agner wrote:
> We discussed the issue at Linaro Connect a bit.
>
> To recap, we do build in two steps:
>
> 1. bitbake full-container-image
> 2. bitbake -c populate_sdk full-container-
Hi,
On 12.09.2018 00:49, Stefan Agner wrote:
> Hi,
>
> We experience build errors as follows every now and then:
>
> ...
> ERROR: full-container-image-0.1-r0 do_populate_sdk: Unable to install
> packages. Command
> '/workdir/oe/tmp/work/colibri_imx7-lmp-linux-gnueab
I think weston is using KMS connector names.
Try HDMI-A-1.
Otherwise, running weston with --log=weston.log will produce a helpful
logfile.
--
Stefan
On 11.09.2018 02:02, Mohamed Dawod wrote:
> -- Forwarded message -
> From: Mohamed Dawod
> Date: Mon, Sep 10, 2018 at 1:15 PM
> S
Hi,
We experience build errors as follows every now and then:
...
ERROR: full-container-image-0.1-r0 do_populate_sdk: Unable to install
packages. Command
'/workdir/oe/tmp/work/colibri_imx7-lmp-linux-gnueabi/full-container-image/0.1-r0/recipe-sysroot-native/usr/bin/opkg
--volatile-cache -f
/workdi
On 04.06.2018 18:18, Alexander Kanavin wrote:
> On 06/04/2018 07:06 PM, Stefan Agner wrote:
>
>> Anything holding us back merging this changes?
>
> Please read the Yocto project status mail:
>
> " · Patch review/merging was slow over the past week due to
On 16.05.2018 11:13, Stefan Agner wrote:
> From: Stefan Agner
>
> Hi,
>
> This follows up on the discussion a while ago:
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg104996.html
>
> Patch 1 is rather simple and really fixes the main issu
From: Stefan Agner
OpenEmbedded has a built-in mechanism to run postinst scripts offline
at build time or, if necessary, on first boot (delayed execution). If
the latter is the case and systemd is in use, two services end up
doing the same thing:
- opkg-configure.service starts "opkg conf
From: Stefan Agner
Start opkg/dpkg as soon as the respective package managers status
file is present, no matter whether /etc/$pm-postinsts exists. This
decouples the implicit link between postinsts scripts in /etc and
the package manager: Currently the package manager is only started
if those
From: Stefan Agner
If package management is present opkg/dpkg will bring the original
copy of the postinsts scripts with the metadata and will be able to
handle postinsts just fine. In fact, it is preferred to let package
management handle the postinsts scripts in this case since it will
keep
From: Stefan Agner
Hi,
This follows up on the discussion a while ago:
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg104996.html
Patch 1 is rather simple and really fixes the main issue. The patch
by itself has been tested with the relevant self test and passes
On 15.05.2018 17:03, Alexander Kanavin wrote:
> On 05/15/2018 05:04 PM, Stefan Agner wrote:
>> This follows up on the discussion a while ago:
>> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg104996.html
>
> Took me a moment to realize all three pa
From: Stefan Agner
OpenEmbedded has a built-in mechanism to run postinst scripts offline
at build time or, if necessary, on first boot (delayed execution). If
the latter is the case and systemd is in use, two services end up
doing the same thing:
- opkg-configure.service starts "opkg conf
From: Stefan Agner
If package management is present opkg/dpkg will bring the original
copy of the postinsts scripts with the metadata and will be able to
handle postinsts just fine. In fact, it is preferred to let package
management handle the postinsts scripts in this case since it will
keep
From: Stefan Agner
Start opkg/dpkg as soon as the respective package managers status
file is present, no matter whether /etc/$pm-postinsts exists. This
decouples the implicit link between postinsts scripts in /etc and
the package manager: Currently the package manager is only started
if those
From: Stefan Agner
Hi,
This follows up on the discussion a while ago:
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg104996.html
Patch 1 is rather simple and really fixes the main issue. The patch
by itself has been tested with the relevant self test and passes
From: Stefan Agner
The udhcpc script calls ip addr flush .. which flushes addresses
of any address family, including IPv6. However, busybox udhcpc is
IPv4 only and should not influence IPv6 addressing. Hence use ip
addr flush with family constrait.
The script particularly broke IPv6 SLAAC
From: Stefan Agner
When compiling OpenSSL with binutils 2.29 for ARM with Thumb2 enabled
crashes and unexpected behavior occurs. E.g. connecting to a OpenSSH
server using the affected binary fails with:
ssh_dispatch_run_fatal: Connection to 192.168.10.171 port 22: incorrect
signature
From: Stefan Agner
Deals with two CVEs:
* bn_sqrx8x_internal carry bug on x86_64 (CVE-2017-3736)
* Malformed X.509 IPAddressFamily could cause OOB read (CVE-2017-3735)
Signed-off-by: Stefan Agner
Acked-by: Otavio Salvador
---
.../openssl/{openssl_1.1.0f.bb => openssl_1.1.0g
From: Stefan Agner
Deals with two CVEs:
* bn_sqrx8x_internal carry bug on x86_64 (CVE-2017-3736)
* Malformed X.509 IPAddressFamily could cause OOB read (CVE-2017-3735)
Signed-off-by: Stefan Agner
Acked-by: Otavio Salvador
---
Changes since v2:
- Rebased to rocko-next
.../0001-Fix-build-with
From: Stefan Agner
When compiling OpenSSL with binutils 2.29 for ARM with Thumb2 enabled
crashes and unexpected behavior occurs. E.g. connecting to a OpenSSH
server using the affected binary fails with:
ssh_dispatch_run_fatal: Connection to 192.168.10.171 port 22: incorrect
signature
From: Stefan Agner
The udhcpc script calls ip addr flush .. which flushes addresses
of any address family, including IPv6. However, busybox udhcpc is
IPv4 only and should not influence IPv6 addressing. Hence use ip
addr flush with family constrait.
The script particularly broke IPv6 SLAAC
On 2017-12-14 19:04, Alexander Kanavin wrote:
> On 12/14/2017 07:49 PM, Alexander Kanavin wrote:
>> On 12/14/2017 07:40 PM, Stefan Agner wrote:
>>
>>> Oh, I see, well that simplifies it, doesn't it? E.g.
>>>
>>> # If package managers support post
On 2017-12-14 18:28, Alexander Kanavin wrote:
> On 12/14/2017 07:16 PM, Stefan Agner wrote:
>
>> Are you sure that rpm has no such facility? Maybe there is some other
>> mechanism around...
>
> You are welcome to find it. rpm does not distinguish between unpacking
>
On 2017-12-14 17:59, Alexander Kanavin wrote:
> On 12/14/2017 06:46 PM, Stefan Agner wrote:
>
>> Suggestion:
>> - Still remove systemd opkg service as proposed, since run-postinsts
>> gets run with systemd and should/will handle package manager just fine
>
> Yes.
&
On 2017-12-14 16:14, Alexander Kanavin wrote:
> On 12/14/2017 04:57 PM, Stefan Agner wrote:
>> On 2017-12-14 15:55, Alexander Kanavin wrote:
>>> On 12/14/2017 04:41 PM, Stefan Agner wrote:
>>>
>>>> I think removing the Opkg first boot systemd service (as the
On 2017-12-14 15:55, Alexander Kanavin wrote:
> On 12/14/2017 04:41 PM, Stefan Agner wrote:
>
>> I think removing the Opkg first boot systemd service (as the initial
>> patch does) is the correct first step.
>>
>> However, it currently still leads to a second copy
On 2017-12-14 15:24, Alexander Kanavin wrote:
> On 12/14/2017 03:59 PM, Stefan Agner wrote:
>
>> That at least contradicts my testing with opkg/ipk.
>>
>> If /etc/ipk-postinsts is not there and /var/lib/opkg/status is there
>> (package management installed), then run
On 2017-12-14 14:52, Alexander Kanavin wrote:
> On 12/14/2017 03:11 PM, Stefan Agner wrote:
>>
>>> I don't think this is correct. Some postinsts are intentionally
>>> deferred to first boot, and they need to be run regardless of whether
>>> the image s
On 2017-12-14 14:10, Alexander Kanavin wrote:
> On 12/13/2017 08:29 PM, Stefan Agner wrote:
>
>> Maybe it needs something like this?
>>
>>
>> runtime_pkgmanage = bb.utils.contains("IMAGE_FEATURES",
>> "package-management",
>&
On 2017-12-13 19:06, Stefan Agner wrote:
> From: Stefan Agner
>
> OpenEmbedded has a built-in mechanism to run postinst scripts offline
> at build time or, if necessary, on first boot (delayed execution). If
> the latter is the case and systemd is in use, two services end up
&
From: Stefan Agner
OpenEmbedded has a built-in mechanism to run postinst scripts offline
at build time or, if necessary, on first boot (delayed execution). If
the latter is the case and systemd is in use, two services end up
doing the same thing:
- opkg-configure.service starts "opkg conf
From: Stefan Agner
On some build hosts distros (e.g. Fedora 26) waf tries to be
smart about libdir detection and defaults to [EXEC_PREFIX/lib64].
This obviously is not what we want for 32-bit targets and usually
fails in the do_package phase:
WARNING: gstreamer1.0-plugins-imx-0.13.0-r0
ort it to rocko).
--
Stefan
>
> 2017-12-12 16:56 GMT+01:00 Stefan Agner :
>
>> On 2017-12-12 16:47, Otavio Salvador wrote:
>>> On Tue, Dec 12, 2017 at 12:38 PM, Stefan Agner wrote:
>>>> On 2017-12-12 15:13, Burton, Ross wrote:
>>>>
>>>>>
On 2017-12-12 16:47, Otavio Salvador wrote:
> On Tue, Dec 12, 2017 at 12:38 PM, Stefan Agner wrote:
>> On 2017-12-12 15:13, Burton, Ross wrote:
>>
>>> On 12 December 2017 at 14:03, Stefan Agner wrote:
>>>
>>>> On 2017-12-12 15:00, Burton, Ross w
On 2017-12-12 15:13, Burton, Ross wrote:
> On 12 December 2017 at 14:03, Stefan Agner wrote:
>
>> On 2017-12-12 15:00, Burton, Ross wrote:
>>
>>> On 12 December 2017 at 13:27, Stefan Agner wrote:
>>>
>>>> On some build hosts distros (e.g. Fe
ix=PREFIX installation prefix [default: '/usr/local/']
--download try to download the tools if missing
..
No libdir to be seen.
--
Stefan
> Best regards,
> Vincent
>
> 2017-12-12 15:00 GMT+01:00 Burton, Ross :
>
> On 12 December 2017 at 13:27, Stefan A
On 2017-12-12 15:00, Burton, Ross wrote:
> On 12 December 2017 at 13:27, Stefan Agner wrote:
>
>> On some build hosts distros (e.g. Fedora 26) waf tries to be
>> smart about libdir detection and defaults to [EXEC_PREFIX/lib64].
>> This obviously is not what we wan
From: Stefan Agner
On some build hosts distros (e.g. Fedora 26) waf tries to be
smart about libdir detection and defaults to [EXEC_PREFIX/lib64].
This obviously is not what we want for 32-bit targets and usually
fails in the do_package phase:
WARNING: gstreamer1.0-plugins-imx-0.13.0-r0
1 - 100 of 156 matches
Mail list logo
