From: Johannes Pointner
If DISTRO_FEATURE usrmerge is enabled, SLIBDIR is just a symlink to LIBDIR.
ldconfig-native uses hardcoded paths for SLIBDIR and LIBDIR that are fine for
the not usrmerge case. But if usrmerge is enabled ldconfig-native generates a
ld.so.cache, which is done in rootfs.py,
From: Mingli Yu
Add systemd-sshd-socket-mode PACKAGECONFIG option to choose sshd.socket
and systemd-sshd-service-mode PACKAGECONFIG option to choose installing
sshd.service.
The systemd-sshd-socket-mode PACKAGECONFIG option is enabled by default
and user can customize the above two PACKAGECONFIG
From: Changqing Li
To fix:
Error: Transaction test error:
file /usr/share/man/man3/crypt.3 from install of
libcrypt-doc-4.4.33-r0.x86_64 conflicts with file from package
man-pages-6.04-r0.x86_64
Signed-off-by: Changqing Li
---
meta/recipes-core/libxcrypt/libxcrypt.inc | 7 ++-
1 fil
On 12/6/23 02:27, Khem Raj wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Tue, Dec 5, 2023 at 3:48 AM Ross Burton wrote:
On 5 Dec 2023, at 01:41, Changqing Li via
l
On 12/5/23 17:55, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Tue, 5 Dec 2023 at 06:46, Changqing Li
wrote:
So I add this patch
https://git.o
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/V3-cairo-upgrade-1.16.0---1.18.0.patch
FAIL: test CVE tag format: Missing or incorrectly formatted CVE tag in patch
From: qiutt
Changelog for 1.18.0 [1]:
The cairo-sphinx tool has been removed
Cairo now implements Type 3 color fonts for PDF
The XML surface has been removed
The Tee surface is now automatically enabled
The Quartz surface is improved
Cairo now hides all private symbols by default on e
On Tue, Dec 5, 2023 at 8:02 AM Bruce Ashfield wrote:
>
> In message: Re: [OE-core][kirkstone 0/4] linux-yocto: -stable updates
> on 05/12/2023 Steve Sakoman wrote:
>
> > On Mon, Dec 4, 2023 at 6:40 PM wrote:
> > >
> > > From: Bruce Ashfield
> > >
> > > Steve,
> > >
> > > Much like my last pull r
bnx2x is another broadcom ethernet adapter with its own firmware. Place
it into its own subpackage.
Signed-off-by: Jason Andryuk
---
.../linux-firmware/linux-firmware_20231030.bb | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/recipes-kernel/linux-firmware/linux-fir
The bnx2 module uses both the mips and rv2p files, so package them all
together. Remove -mips from the package name, but add an RPROVIDES for
compatibility.
Signed-off-by: Jason Andryuk
---
.../linux-firmware/linux-firmware_20231030.bb | 14 +-
1 file changed, 9 insertions(+),
The iwlwifi uses the .pnvm files for newer AX210+ cards, so package them
into the iwlwifi-misc subpackage.
Signed-off-by: Jason Andryuk
---
.../recipes-kernel/linux-firmware/linux-firmware_20231030.bb | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/lin
This is a small series to fixup up linux-firmware packaging:
The first adds some .pnvm files needed along with the .ucode by newer
iwlwifi cards to the linux-firmware-iwlwifi-misc package.
The second renames s/bnx2-mips/bnx2/ and includes more files needed by
the driver.
The third creates a new b
On Tue, Dec 5, 2023 at 3:48 AM Ross Burton wrote:
>
> On 5 Dec 2023, at 01:41, Changqing Li via lists.openembedded.org
> wrote:
> >
> > From: Changqing Li
> >
> > To fix:
> >
> > Error: Transaction test error:
> > file /usr/share/man/man3/crypt.3 from install of
> > libcrypt-doc-4.4.33-r0.x86
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
8e221b47173d Linux 5.4.262
b053223b7cf4 netfilter: nf_tables: bogus EBUSY when deleting flowtable
after flush (for 5.4)
c35df8b8c572 netfilter: nf_tables: disable toggling dormant
In message: Re: [OE-core][dunfell 3/3] linux-yocto/5.4: update to v5.4.262
on 05/12/2023 Steve Sakoman wrote:
> Hi Bruce,
>
> I'm getting a failure on the autobuilder for this version bump:
>
> https://errors.yoctoproject.org/Errors/Details/745216/
>
> ERROR: Package Version (5.4.262+gitAUTOINC
On Tue, Dec 5, 2023 at 12:55 PM Alexandre Belloni
wrote:
>
> Hello Bruce,
>
> I got this: Unable to find revision 867a6bdef9701f378f5a9ce66a713daa22598649
> in branch yocto-6.5
> This seems correct, did you forget to push anything?
I just replied to Steve.
It's my new machine having different d
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/v2-tiff-Backport-fixes-for-CVE-2023-6277.patch
FAIL: test commit message presence: Please include a commit message
In message: Re: [OE-core][kirkstone 0/4] linux-yocto: -stable updates
on 05/12/2023 Steve Sakoman wrote:
> On Mon, Dec 4, 2023 at 6:40 PM wrote:
> >
> > From: Bruce Ashfield
> >
> > Steve,
> >
> > Much like my last pull request to Richard, this has been
> > generated from a newly provisioned mac
Hello Bruce,
I got this: Unable to find revision 867a6bdef9701f378f5a9ce66a713daa22598649 in
branch yocto-6.5
This seems correct, did you forget to push anything?
On 04/12/2023 23:26:55-0500, Bruce Ashfield wrote:
> From: Bruce Ashfield
>
> Richard,
>
> Here's my latest -stable updates for 6.
Signed-off-by: Khem Raj
---
v2: Drop ununsed patch
...277-Apply-1-suggestion-s-to-1-file-s.patch | 27 +++
...ompare-data-size-of-some-tags-data-2.patch | 36
...-compare-data-size-of-some-tags-data.patch | 162 ++
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 3 +
4 f
On 5 Dec 2023, at 16:34, Alexandre Belloni via lists.openembedded.org
wrote:
>
> Hello,
>
> Running cve-check against oe-core now generates a few warnings:
>
> WARNING: automake-native-1.16.5-r0 do_cve_check: automake: Failed to compare
> 1.16.5 = branch_1-9 for CVE-2009-4029
> WARNING: subve
From: Ross Burton
This change introduced a warning if version comparisons failed, but
this is far too common an issue in data that we don't control, so this
shouldn't cause a warning:
WARNING: automake-native-1.16.5-r0 do_cve_check: automake: Failed to compare
1.16.5 = branch_1-9 for CVE-2009-4
Hello,
Running cve-check against oe-core now generates a few warnings:
WARNING: automake-native-1.16.5-r0 do_cve_check: automake: Failed to compare
1.16.5 = branch_1-9 for CVE-2009-4029
WARNING: subversion-1.14.2-r0 do_cve_check: subversion: Failed to compare
1.14.2 = m1 for CVE-2010-4539
WARNI
Le mar. 5 déc. 2023 à 16:45, Alexandre Belloni
a écrit :
>
> On 05/12/2023 15:57:58+0100, Julien Stephan wrote:
> > Le mar. 5 déc. 2023 à 08:50, Alexandre Belloni
> > a écrit :
> > >
> > > Please do not send bitbake patches in the same series as oe-core patches
> > > if there is no dependency. Th
Hello,
This fail for musl:
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/8237/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/8267/steps/12/logs/stdio
On 04/12/2023 22:44:10-0800, Robert Yang via lists.openembedded.org wrote:
> From: Robe
On Mon, Dec 4, 2023 at 6:40 PM wrote:
>
> From: Bruce Ashfield
>
> Steve,
>
> Much like my last pull request to Richard, this has been
> generated from a newly provisioned machine after my old machine
> of 10 years had a disk failure.
>
> Let me know if you have any issues with this, and I'll deb
Hi Bruce,
I'm getting a failure on the autobuilder for this version bump:
https://errors.yoctoproject.org/Errors/Details/745216/
ERROR: Package Version (5.4.262+gitAUTOINC+9f1a56eeea_102ea8999f) does
not match of kernel being built (5.4.260). Please update the PV
variable to match the kernel sou
Current Dev Position: YP 5.0 M1
Next Deadline: 4th December 2023 YP 5.0 M1 build
Next Team Meetings:
-
Bug Triage meeting Thursday December 7th at 7:30 am PST (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync Tuesday December 5
On 05/12/2023 15:57:58+0100, Julien Stephan wrote:
> Le mar. 5 déc. 2023 à 08:50, Alexandre Belloni
> a écrit :
> >
> > Please do not send bitbake patches in the same series as oe-core patches
> > if there is no dependency. Those patches are applied on different
> > repositories.
>
> Hi Alexandre
On 2023-12-04 04:57, Alexander Kanavin wrote:
Is this a different patchtest issue to the one that was fixed?
Looks like there are still excessive line length issues with the
patchtest report that I need to fix.
This is what it reported:
FAIL: test Signed-off-by presence: A patch file has b
Le mar. 5 déc. 2023 à 08:50, Alexandre Belloni
a écrit :
>
> Please do not send bitbake patches in the same series as oe-core patches
> if there is no dependency. Those patches are applied on different
> repositories.
Hi Alexandre,
Noted! Do you want me to resend the series without the bitbake p
Add a new parameter update_original_recipe to allow to patch a recipe
instead of creating/updating a bbappend
Signed-off-by: Julien Stephan
---
meta/lib/oe/recipeutils.py | 35 +--
1 file changed, 25 insertions(+), 10 deletions(-)
diff --git a/meta/lib/oe/recipeu
appendsrc function relies on oe.recipeutils.bbappend_recipe to
copy files and add the corresponding entries in SRC_URI.
Currently, appendsrc function build itself the new SRC_URI entry to add the
correct subdir param, and gives it using the extralines parameter.
This has 2 drawbacks:
- oe.recipeut
add a basic test for testing the update mode of recipetool
appendsrcfile(s)
Signed-off-by: Julien Stephan
---
meta/lib/oeqa/selftest/cases/recipetool.py | 28 ++
1 file changed, 28 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/recipetool.py
b/meta/lib/oeqa/selftes
Add a new test for machine specific bbappend override
Signed-off-by: Julien Stephan
---
meta/lib/oeqa/selftest/cases/recipetool.py | 44 +++---
1 file changed, 38 insertions(+), 6 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/recipetool.py
b/meta/lib/oeqa/selftest/case
Add a new option -u/--update-recipe to update the recipe itself instead
of creating/updating a bbappend file
Signed-off-by: Julien Stephan
---
scripts/lib/recipetool/append.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/recipetool/append.py b/scripts/lib/
Currently we do not add a new src_ury entry if the entry already exists
AND the parameters are the same.
I believe that when an entry already exist with different parameters,
we should remove it and add the new entry otherwise we end up with two
entries with different parameters
Signed-off-by: Ju
Add missing patchdir key in docstring description for srcfiles
parameters.
Also fix typo: value --> key in srcfile docstring description
Signed-off-by: Julien Stephan
---
meta/lib/oe/recipeutils.py | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oe/recipeuti
bbappend_recipe can take a dict of source files to add to SRC_URI where
the key is the full path to the file to be added and the value is a dict
Add a new optionnal entry "newname" to specify the name of the newly added file
Signed-off-by: Julien Stephan
---
meta/lib/oe/recipeutils.py | 7 +
In the case get_bbappend_path returns None (could not find the layer
containing the recipe) the error message tries to print the recipefile,
but it is not defined. Fix it.
Signed-off-by: Julien Stephan
---
meta/lib/oe/recipeutils.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/lib/oe
Hi all,
I was trying to use recipetool appendsrcfile to add a file to a recipe and I
noticed several issues:
* -m is not correctly supported
* recipetool appendsrfile(s) are missing a usefull dry-run mode
* appendsrc function relies on oe.recipeutils.bbappend_recipe but
duplicates some code: it
Add dry-run mode for recipetool appendsrcfile and appendsrcfiles, with
if necessary, a diff of changes
Signed-off-by: Julien Stephan
---
scripts/lib/recipetool/append.py | 33 +++-
1 file changed, 32 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/recipetool/ap
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/kirkstone-v2-3-5-rust-cross-rust-common-Merge-arm-target-handling-code-to-fix-cross-canadian.patch
FAIL: test short
From: Richard Purdie
Some recipes reference these. Rather than continually trying to chase down the
references
and taskhash issues, clear the variables for an easier life and simpler code.
These
wouldn't convey anything useful in a native build.
Signed-off-by: Richard Purdie
(cherry picked fr
From: Richard Purdie
Match the code in rust-cross-canadian so that further simplifications
can be considered in future.
Signed-off-by: Richard Purdie
(cherry picked from commit 5cb62d0a33777cb9afb1eea5f736a2580ce50dc7)
Signed-off-by: Jermain Horsman
---
meta/recipes-devtools/rust/rust-common.
From: Richard Purdie
rust-cross had special handling for armv7 targets but we also need this
for cross-canadian. Merge the code into the main function so everything is
consistent.
Also then fix the arm definition to be arm-eabi since ABI is correctly
being looked up.
Signed-off-by: Richard Purd
From: Richard Purdie
Based upon a patch from Otavio Salvador ,
ensure the target json files are written in the correct order with
the most specific last incase it overwrites earlier files if the prefixes
match.
Signed-off-by: Richard Purdie
(cherry picked from commit 1912c4e9e0ecf9655f3b3a41588
From: Richard Purdie
When a 'BUILD' target is requested we shouldn't be looking at TARGET_SYS but
at BUILD_SYS. Due to the way rust mangles triplets, we need the HOST_SYS triplet
to work with existing code - fixing that issue is a separate patch.
Also drop the arch_abi argument, it doens't make
From: Jermain Horsman
I ran into the following when trying to compile rust for arm (on kirkstone):
Exception: TypeError: int() argument must be a string, a bytes-like object or a
number, not 'NoneType'
After some investigation I notices some patches on master which were not
available on kirkst
Version 2 of the patch: I implemented the feedback of Richard (convert
PACKAGE_MINIDEBUGINFO to a DISTRO_FEATURES), and added a runtime test.
This was my local.conf used for testing (with "bitbake -v -c testimage
core-image-sato"):
DISTRO_FEATURES:append = " minidebuginfo"
IMAGE_CLASSES += "testim
From: Etienne Cordonnier
Enabling minidebuginfo is not useful if gdb and systemd-coredump
are unable to parse it.
In order to parse it, gdb needs xz support. Systemd needs coredump enabled, as
well as elfutil enabled as well (systemd-coredump loads libdw which is part of
elfutils using dlopen).
Note that this depends on Bruce’s latest kernel patches.
Ross
> On 5 Dec 2023, at 13:23, Ross Burton via lists.openembedded.org
> wrote:
>
> From: Ross Burton
>
> Signed-off-by: Ross Burton
> ---
> .../linux/cve-exclusion_6.1.inc | 26 +++
> .../linux/cve-exclus
From: Ross Burton
Signed-off-by: Ross Burton
---
.../linux/cve-exclusion_6.1.inc | 26 +++
.../linux/cve-exclusion_6.5.inc | 22 +---
2 files changed, 40 insertions(+), 8 deletions(-)
diff --git a/meta/recipes-kernel/linux/cve-exclusion_6
> On 3 Dec 2023, at 16:20, Khem Raj via lists.openembedded.org
> wrote:
>
> create mode 100644 meta/recipes-multimedia/libtiff/tiff/545.patch
This file is created but not used.
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191817):
http
On 5 Dec 2023, at 01:41, Changqing Li via lists.openembedded.org
wrote:
>
> From: Changqing Li
>
> To fix:
>
> Error: Transaction test error:
> file /usr/share/man/man3/crypt.3 from install of
> libcrypt-doc-4.4.33-r0.x86_64 conflicts with file from package
> man-pages-6.04-r0.x86_64
This
This causes:
stdio: WARNING: libxcrypt-4.4.36-r0 do_package: libxcrypt: alternative target
(/usr/bin/crypt_r.3 or /usr/bin/crypt_r.3.libxcrypt) does not exist, skipping...
stdio: WARNING: libxcrypt-4.4.36-r0 do_package: libxcrypt: NOT adding
alternative provide /usr/bin/crypt_r.3: /usr/bin/crypt
On Tue, 5 Dec 2023 at 10:44, Johannes Pointner wrote:
> Thanks, I understand that, but ldconfig-native seemed very special to me, so
> I tried to take an example from the existing patches.
>
> So the next step would be a v2 with a better explanation and obviously a
> fixed sendemail.from?
> Or are
mickledore is already end of life I think?
Alex
On Mon, 4 Dec 2023 at 20:36, Joe Slater via lists.openembedded.org
wrote:
>
> From: Joe Slater
>
> De-fuzz existing patches.
> Do not update PACKAGECONFIG to match master.
>
> Signed-off-by: Joe Slater
> ---
> ...ile-should-be-excuted-in-target-
On Tue, 5 Dec 2023 at 06:46, Changqing Li
wrote:
> So I add this patch
> https://git.openembedded.org/openembedded-core/commit/?id=406a72a9a47c2735b7e18cefc682b1df00d5a9aa
> to remove the lock file in rootfs.
>
> Since for dnf-native, it will not have reboot process, so it is better
> to remov
On Mon, Dec 4, 2023 at 11:00 AM Alexander Kanavin
wrote:
>
> Generally if you mark something as inappropriate, it's best to write
> an extended description of why in the patch. The barrier to adding
> patches that we can never upstream is high.
>
Thanks, I understand that, but ldconfig-native seem
Then it's probably best to write a recipe, so that the code can be
hosted externally and maintained independently of oe-core?
Alex
On Mon, 4 Dec 2023 at 15:46, Andrey Popov wrote:
>
> Hello, Alex!
>
> I have doubts that the entire isoparser class set could be inlined, that
> would occupy around
UEFI bootloader specification says the primary place for UKI images
is the /EFI/Linux/ directory under $boot. Defining a varaible for
the same to reuse in all UEFI-related packages.
Signed-off-by: Viswanath Kraleti
---
meta/conf/image-uefi.conf | 4
1 file changed, 4 insertions(+)
diff --g
Using devtool to patch CRLF based sources creates patch files which have
mixed end of lines : LF for headers and CRLF for source context and
modified lines.
Python open(..., newline=None) (default for newline arg)does detect
end-of-line in this mixed file but only outputs LF EOL data. This
result
Le mar. 5 déc. 2023 à 08:48, Alexandre Belloni <
alexandre.bell...@bootlin.com> a écrit :
> Hello,
>
> This doesn't apply on master, can you rebase?
>
Yes! I will send a v2 today
On 27/11/2023 14:49:03+0100, Yoann Congal wrote:
> > Using devtool to patch CRLF based sources creates patch files wh
64 matches
Mail list logo
