Hi,
Op 19-04-2022 om 15:21 schreef Richard Purdie:
On Wed, 2022-04-13 at 22:37 +0200, Ferry Toth wrote:
[PATCH v4 1/2] apt: add apt selftest to test signed package feeds
[PATCH v4 2/2] package_manager: fix missing dependency on gnupg when
Since Gatesgarth apt (1.8.2) has become more strict
From: Ferry Toth
When signing the deb package feed gpg tools are a soft requirement. If
gnupg-native
is not declared a dependancy the version from hosttools is used. Unfortunately
the
gpg-agent version from Ubuntu 16.04 on the autobuilders is incompatible with
the package_index task
and fails
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when performing selftest.
Patches "gpg-sign: Add param
[PATCH v4 1/2] apt: add apt selftest to test signed package feeds
[PATCH v4 2/2] package_manager: fix missing dependency on gnupg when
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked
Hi,
Op 13-04-2022 om 09:00 schreef Richard Purdie:
On Wed, 2022-04-13 at 00:34 +0200, Alexandre Belloni wrote:
On 13/04/2022 00:20:40+0200, Ferry Toth wrote:
Hi,
Op 12-04-2022 om 23:51 schreef Richard Purdie:
On Tue, 2022-04-12 at 23:48 +0200, Alexandre Belloni wrote:
On 12/04/2022 23:32
Hi,
Op 12-04-2022 om 23:51 schreef Richard Purdie:
On Tue, 2022-04-12 at 23:48 +0200, Alexandre Belloni wrote:
On 12/04/2022 23:32:49+0200, Ferry Toth wrote:
Hi
Op 12-04-2022 om 16:16 schreef Alexandre Belloni:
Hello,
On 11/04/2022 22:50:36+0200, Ferry Toth wrote:
From: Ferry Toth
Since
Hi
Op 12-04-2022 om 16:16 schreef Alexandre Belloni:
Hello,
On 11/04/2022 22:50:36+0200, Ferry Toth wrote:
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked
[PATCH v3 1/1] apt: add apt selftest to test signed package feeds
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when performin
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when performing selftest.
Patches "gpg-sign: Add param
[PATCH v3 1/1] apt: add apt selftest to test signed package feeds
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when performin
Op 06-04-2022 om 23:05 schreef Richard Purdie:
On Wed, 2022-04-06 at 21:44 +0200, Ferry Toth wrote:
Hi
Op 06-04-2022 om 17:23 schreef Richard Purdie:
On Wed, 2022-04-06 at 16:43 +0200, Ferry Toth wrote:
Op 06-04-2022 om 13:40 schreef Richard Purdie:
On Tue, 2022-04-05 at 17:23 +0200, Ferry
Hi
Op 06-04-2022 om 17:23 schreef Richard Purdie:
On Wed, 2022-04-06 at 16:43 +0200, Ferry Toth wrote:
Op 06-04-2022 om 13:40 schreef Richard Purdie:
On Tue, 2022-04-05 at 17:23 +0200, Ferry Toth wrote:
Op 04-04-2022 om 22:39 schreef Richard Purdie:
On Mon, 2022-04-04 at 19:35 +0200, Ferry
Hi
Op 06-04-2022 om 12:10 schreef Alexandre Belloni:
Hello,
On 04/04/2022 14:58:07+0100, Richard Purdie wrote:
On Sun, 2022-04-03 at 21:50 +0200, Ferry Toth wrote:
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default
Hi,
Op 06-04-2022 om 13:40 schreef Richard Purdie:
On Tue, 2022-04-05 at 17:23 +0200, Ferry Toth wrote:
Op 04-04-2022 om 22:39 schreef Richard Purdie:
On Mon, 2022-04-04 at 19:35 +0200, Ferry Toth wrote:
Op 04-04-2022 om 15:58 schreef Richard Purdie:
On Sun, 2022-04-03 at 21:50 +0200
Hi,
Op 04-04-2022 om 22:39 schreef Richard Purdie:
On Mon, 2022-04-04 at 19:35 +0200, Ferry Toth wrote:
Hi,
Op 04-04-2022 om 15:58 schreef Richard Purdie:
On Sun, 2022-04-03 at 21:50 +0200, Ferry Toth wrote:
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t
Hi,
Op 04-04-2022 om 15:58 schreef Richard Purdie:
On Sun, 2022-04-03 at 21:50 +0200, Ferry Toth wrote:
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when performing selftest.
Patches "gpg-sign: Add param
From: Ferry Toth
Implement debian package repository signature.
For each Release file created in repository subdirectory, a signature
Release.gpg is created.
Signature is performed using gpg backend when the following variables
are set in local.conf:
PACKAGE_CLASSES += "sign_package
From: Xavier Berger
output_suffix: If defined, add output_suffix as file name extension.
use_sha256: If True, use sha256 for gpg as digest algorithm
Signed-off-by: Xavier Berger
Signed-off-by: Ferry Toth
---
meta/lib/oe/gpg_sign.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion
[PATCH v2 0/3] package_manager: support for signed DEB package feeds
[PATCH v2 1/3] gpg-sign: Add parameters to gpg signature function
[PATCH v2 2/3] package_manager: sign DEB package feeds
[PATCH v2 3/3] apt: add apt selftest to test signed package feeds
Since Gatesgarth apt (1.8.2) has become mo
From: Ferry Toth
*** BLURB HERE ***
Ferry Toth (2):
package_manager: sign DEB package feeds
apt: add apt selftest to test signed package feeds
Xavier Berger (1):
gpg-sign: Add parameters to gpg signature function
meta/lib/oe/gpg_sign.py | 6 +++-
meta/lib/oe
Hi,
Op 24-03-2022 om 23:20 schreef Richard Purdie:
On Thu, 2022-03-24 at 23:11 +0100, Ferry Toth wrote:
Op 24-03-2022 om 16:36 schreef Ferry Toth:
Op 24-03-2022 om 13:03 schreef Richard Purdie:
On Thu, 2022-03-24 at 12:23 +0100, Ferry Toth wrote:
On Wed, 2022-03-23 at 19:34 +0100, Ferry
Hi Alexander,
I see your answer on gmane, but not by e-mail, strange.
But thanks for the tip, it worked and I got oe-selftest -r
runtime_test.TestImage.test_testimage_dnf to run successfully.
(for future readers: by following "Yocto Project Development Tasks" manual
section "Performing Automat
Hi,
Op 24-03-2022 om 23:11 schreef Ferry Toth:
It doesn't seem to be a particularly volatile area in the code. I
refreshed
Xavier's patches for Gatesgarth, and am actively using unchanged
patch on
Honisiter.
I don't know how the automated testing is working but I guess
Hi
Op 24-03-2022 om 16:36 schreef Ferry Toth:
Hi
Op 24-03-2022 om 13:03 schreef Richard Purdie:
On Thu, 2022-03-24 at 12:23 +0100, Ferry Toth wrote:
On Wed, 2022-03-23 at 19:34 +0100, Ferry Toth wrote:
I forgot to add a cover letter, sorry for that. The 2 patches together
implement DEB
Hi
Op 24-03-2022 om 13:03 schreef Richard Purdie:
On Thu, 2022-03-24 at 12:23 +0100, Ferry Toth wrote:
On Wed, 2022-03-23 at 19:34 +0100, Ferry Toth wrote:
I forgot to add a cover letter, sorry for that. The 2 patches together
implement DEB repository signing.
This is necessary since
Hi,
Op 24-03-2022 om 09:12 schreef Richard Purdie:
On Wed, 2022-03-23 at 19:34 +0100, Ferry Toth wrote:
Hi Richard,
I forgot to add a cover letter, sorry for that. The 2 patches together
implement DEB repository signing.
This is necessary since Gatesgarth |apt| (1.8.2) has become more
:19 schreef Ferry Toth:
From: Xavier Berger
output_suffix: If defined, add output_suffix as file name extension.
use_sha256: If True, use sha256 for gpg as digest algorithm
Signed-off-by: Xavier Berger
Signed-off-by: Ferry Toth
---
meta/lib/oe/gpg_sign.py | 6 +-
1 file changed, 5
From: Ferry Toth
Implement debian package repository signature.
For each Release file created in repository subdirectory, a signature
Release.gpg is created.
Signature is performed using gpg backend when the following variables
are set in local.conf:
PACKAGE_CLASSES += "sign_package
From: Xavier Berger
output_suffix: If defined, add output_suffix as file name extension.
use_sha256: If True, use sha256 for gpg as digest algorithm
Signed-off-by: Xavier Berger
Signed-off-by: Ferry Toth
---
meta/lib/oe/gpg_sign.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion
Hi,
Op 01-06-2021 om 22:12 schreef Ferry Toth via lists.openembedded.org:
Hi
Op 26-05-2021 om 20:32 schreef Guillaume Champagne:
do_bootimg expects IMGDEPLOYDIR to exist, since it stores its artifacts
there. Therefore, do_bootimg should run after do_rootfs because
IMGDEPLOYDIR is created
Hi
Op 26-05-2021 om 20:32 schreef Guillaume Champagne:
do_bootimg expects IMGDEPLOYDIR to exist, since it stores its artifacts
there. Therefore, do_bootimg should run after do_rootfs because
IMGDEPLOYDIR is created before do_rootfs runs since IMGDEPLOYDIR is
contained in do_rootfs' [cleandirs] v
Op 29-10-2019 om 11:25 schreef JH:
Hi Ferry,
On 10/29/19, Ferry Toth wrote:
https://github.com/edison-fw/meta-intel-edison/blob/master/meta-intel-edison-bsp/conf/machine/edison.conf
And there is the max size!
Are you able to run u-boot to start kernel in the large size 64 MB?
No, the
Op 28-10-2019 om 22:36 schreef Ross Burton:
On 25/10/2019 21:39, Ferry Toth wrote:
Op 25-10-2019 om 21:32 schreef Patchwork:
== Series Details ==
Series: sudo: Fix fetching sources
Revision: 1
URL : https://patchwork.openembedded.org/series/20684/
State : failure
== Summary ==
Thank you
Op 28-10-2019 om 03:02 schreef JH:
On 10/28/19, Ferry Toth wrote:
No, there is no limitation in kernel, BTW, the zImage-initramfs is not
just kernel space, the zImage-initramfs = kernel + rootfs which cannot
be limited to 10 MB. I have a zImage-initramfs created by openwrt, the
size is 28 MB
Op 27-10-2019 om 22:52 schreef JH:
Hi Ferry,
On 10/27/19, Ferry Toth wrote:
Op 27-10-2019 om 02:27 schreef JH:
Hi Ferry,
On 10/27/19, Ferry Toth wrote:
As an example you might want to look at my repo, I have 2 images minimal
and initramfs:
https://github.com/edison-fw/meta-intel-edison
Op 27-10-2019 om 02:27 schreef JH:
Hi Ferry,
On 10/27/19, Ferry Toth wrote:
As an example you might want to look at my repo, I have 2 images minimal
and initramfs:
https://github.com/edison-fw/meta-intel-edison/tree/master/meta-intel-edison-distro/recipes-core/images
I don't exactly
Op 26-10-2019 om 11:46 schreef JH:
Hi,
I finally built the
zImage->zImage--4.19.75+git0+d573e8a79f-r0-20191026074920.bin and
zImage-initramfs ->
zImage-initramfs--4.19.75+git0+d573e8a79f-r0-20191026074920.bin based
on oe-core kernel.bbclass.
The zImage could be loaded by u-boot on RAM booting b
It looks like https://www.sudo.ws/download.html changed certificate
and directory structure. This breaks fetching sources.
Signed-off-by: Ferry Toth
---
meta/recipes-extended/sudo/sudo_1.8.23.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/sudo
Op 25-10-2019 om 21:32 schreef Patchwork:
== Series Details ==
Series: sudo: Fix fetching sources
Revision: 1
URL : https://patchwork.openembedded.org/series/20684/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response.
It looks like https://www.sudo.ws/download.html changed certificate and
directory structure. So that breaks not only thud, but also warrior and
zeus. It can be fixed by changing the path in the recipe to
https://www.sudo.ws/dist/sudo-${PV}.tar.gz or
ftp://ftp.sudo.ws/pub/sudo/sudo-${PV}.tar.gz.
Hi
Op 13-10-19 om 11:10 schreef JH:
On 10/13/19, Khem Raj wrote:
$ vi local.conf
IMAGE_ROOTFS += " core-image-minimal-initramfs"
INITRAMFS_IMAGE should be an image name. Like core-image-minimal or
somesuch
Hmm, change it to my image, the name is solar-image.bb (bitbake
solar-image), is i
Op 10-01-19 om 21:52 schreef Marek Vasut:
On 1/10/19 9:49 PM, Marek Vasut wrote:
On 1/10/19 9:48 PM, akuster808 wrote:
On 1/10/19 8:23 AM, Ferry Toth wrote:
After a new checkout I am experiencing multiple errors building Sumo
that might be related:
bison-3.0.4
cross-localedef-native_2.27
Op 10-01-19 om 21:48 schreef akuster808:
On 1/10/19 8:23 AM, Ferry Toth wrote:
After a new checkout I am experiencing multiple errors building Sumo
that might be related:
bison-3.0.4
cross-localedef-native_2.27
coreutils-8.29
On another machine with slightly out-of-date Sumo these
After a new checkout I am experiencing multiple errors building Sumo
that might be related:
bison-3.0.4
cross-localedef-native_2.27
coreutils-8.29
On another machine with slightly out-of-date Sumo these problems do not
occur.
Detail below.
Any ideas how to fix?
Ferry
virtual:native:/h
Commit ab54dd75 "libgpiod: Rrecommend python3 only for PN-python
package" also removes the build dependency
on python3 however this results in fatal error: Python.h: No such file
or directory #include
Signed-off-by: Ferry Toth
---
meta-oe/recipes-support/libgpiod/libgpiod_1.2.b
Commit ab54dd75 "libgpiod: Rrecommend python3 only for PN-python
package" also removes the build dependency on python3 however this
results in fatal error: Python.h: No such file or directory #include
Signed-off-by: Ferry Toth
---
meta-oe/recipes-support/libgpiod/libgpiod_1.2.b
47 matches
Mail list logo
