On Mon, 2024-02-19 at 16:19 +, Jonathan GUILLOT wrote:
> split_locales() must only check subdirectories in paths added to
> LOCALE_PATHS to avoid creating weird packages based on filenames also
> present in paths.
>
> Without such a filter, cups recipe adding ${datadir}/cups/templates
> to
>
Hoi Richard,
and thanks for the feedback!
>> archive the package database after the rootfs has been put together as
>> *rootfs-pkdbfs.tar.gz, and put it into the deploy folder.
>>
>> This creates a snapshot of the package mangers state at the point in time
>> when
>> all dependencies have been
Hoi Richard,
and thanks for the feedback!
your other mail is still being processed, but to get already back to you on
this one:
>> set the package-database of a "lower image" to unpack and build upon when
>> installing packages for the current image. This way a lean image will be
>> created,
Judgment processing of vulnerable using "=" compares characters as strings
rather than numbers,
and misjudges "cases that do not match in strings but do match in numbers" as
"Patched".
(e.g. PV = "1.2.0" and Vulnerabilities Affected Versions (registered with NVD)
= "1.2")
Therefore, if the
License-Update: Copyright year updated to 2024.
ChangeLog (https://github.com/libsdl-org/SDL/releases/tag/release-2.30.0):
* Added support for 2 bits-per-pixel indexed surface formats
* Added the function SDL_GameControllerGetSteamHandle() to get the Steam
API handle for a controller, if
From: Xiangyu Chen
This fix commit oe-core: 1b69769b -- bash: changes to SIGINT handler while
waiting for a child
Due to the patch adjust and drop some codes to be applicable the tree,
the line number has been changed, that cause test case "run-type" fail.
Signed-off-by: Xiangyu Chen
---
Add HOMEPAGE and DESCRIPTION that were missing in
the original recipe in meta-python
Signed-off-by: Tim Orling
---
.../python/python3-pyproject-metadata_0.7.1.bb| 11 +++
1 file changed, 11 insertions(+)
diff --git
This is a dependency for python3-meson-python.
Signed-off-by: Tim Orling
---
meta/conf/distro/include/maintainers.inc | 1 +
.../python/python3-pyproject-metadata_0.7.1.bb | 16
2 files changed, 17 insertions(+)
create mode 100644
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/4-4-recipetool-add-support-for-python_mesonpy-class.patch
FAIL: test shortlog format: Commit shortlog (first line
From: Fabien Mahot
When ldconfig-native reads an ELF file, it computes an offset from a LOAD
segment, to point on DT NEEDED entries of dynstr section.
Without this patch, ldconfig-native uses only the first LOAD segment, even if
the offset is incorrect.
This patch adds conditions to compute the
* Add support to detect the "mesonpy" build-backend for recipetool create.
* Add oe-selftest case for creating a recipe for "siphash24" from pypi.
https://pypi.org/project/siphash24/
This is by far the simplest recipe using the mesonpy build backend.
Upstream does not provide LICENSE file(s)
Replace the deprecated setuptools3 bbclass with python_mesonpy.
The build-backend has been defined as "mesonpy" since:
https://github.com/numpy/numpy/commit/942fb8caf33a65e449fbf198ecf1cd39be953248
The vendored meson-python was dropped in:
Move the PEP-517 back-end bbclass from meta-python to support:
[build-system]
build-backend = "mesonpy"
This is the declared backend in python3-numpy since:
https://github.com/numpy/numpy/commit/942fb8caf33a65e449fbf198ecf1cd39be953248
Signed-off-by: Tim Orling
---
meson-python is a Python build backend built on top of the Meson
build-system. It enables you to use Meson for your Python packages.
https://meson-python.readthedocs.io/en/latest/
It is used as the PEP-517 build-backend for python3-numpy and python3-scipy.
For other projects using the backend,
Move the python_mesonpy bbclass and python3-meson-python recipe from
meta-python.
https://meson-python.readthedocs.io/en/latest/
This is the declared backend for python-numpy, so it is time to move it to
oe-core.
The following changes since commit 4cfd0f7e4e2db19344677999572e5b71ae97dfc4:
By default, the cpptools VSCode extension will use the host's headers
and flags for linting. This results in a lot of include errors and
misleading definitions. Even though this generic configuration doesn't
include all the depenendencies, it is a proper fallback for recipe
classes we do not
When debugging or browsing files, the user may fall into external
sources from other packages in the sysroot or dbg-rootfs. Modifying them
will only lead to confusion since they will be overwritten by Yocto. The
user should open them in a separate devtool modify session if they want
to make
The generated scripts use the sys.path configuration found inside
bitbake. It can be a different python version than the one used on the
host through the IDE.
For instance, when running the generated script
deploy_target_cmake-example-core2-64 from an eSDK generated on another
machine, I got the
Among the files generated by meson is compile_commands.json. It is not
used by bitbake during the build. However, if the devtool workspace is
opened inside an IDE, that IDE can use compile_commands.json to
configure linting and code completion. This is notably relied on by the
new devtool ide-sdk
When launching the debug configuration, the source files from the debug
rootfs were openened in the editor instead of the local workspace files.
We add an exception to properly map them to the file being developed and
compiled by the IDE integration. This also more closely matches what the
user
These patches improve the VSCode support in devtool ide-sdk from Adrian
Freihofer.
I added a generic C++ configuration for the VScode extension while
awaiting for autotools support.
A refactoring is proposed for the meson class. Without absolute compiler
paths, the linter inside VSCode will not
split_locales() must only check subdirectories in paths added to
LOCALE_PATHS to avoid creating weird packages based on filenames also
present in paths.
Without such a filter, cups recipe adding ${datadir}/cups/templates to
LOCALE_PATHS creates the following incorrect packages:
-
python 2 is gone and we don't need the abstraction now, drop the remaining usage
of this variable.
The definition in python3-dir.bbclass is left for now for other layers.
Signed-off-by: Richard Purdie
---
.../python/python-async-test.inc | 2 +-
On 19 Feb 2024, at 15:03, Peter Kjellerstedt
wrote:
>> This is all that is needed for the new code to work correctly with an old
>> worktree, right?
>
> Well, it relies on the fallback (i.e., the exception clause) in
> GitApplyTree.getNotes()
> that reads from the commit message in case a Git
On Mon, 2024-02-19 at 11:00 +0100, Jonathan GUILLOT wrote:
> Thanks Ross,
>
> I was too focus on English and French packages and missed this point.
> Listing all items in CUPS added locale path is not OK. I should at
> least only get directories (not files) in this path to create the
> locale
> -Original Message-
> From: Ross Burton
> Sent: den 19 februari 2024 13:56
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCHv2 5/5] lib/oe/patch: Use git notes to store
> the filenames for the patches
>
> On 19 Feb 2024, at 01:28,
> -Original Message-
> From: Ross Burton
> Sent: den 19 februari 2024 13:54
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCHv2 3/5] devtool: Make use of
> oe.patch.GitApplyTree.commitIgnored()
>
> On 19 Feb 2024, at 01:28, Peter
On Tue, 2024-02-13 at 11:00 +0100, Johannes Schneider via
lists.openembedded.org wrote:
> set the package-database of a "lower image" to unpack and build upon when
> installing packages for the current image. This way a lean image will be
> created, which only holds the packages that are not
On Tue, 2024-02-13 at 11:00 +0100, Johannes Schneider via
lists.openembedded.org wrote:
> archive the package database after the rootfs has been put together as
> *rootfs-pkdbfs.tar.gz, and put it into the deploy folder.
>
> This creates a snapshot of the package mangers state at the point in
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-libuv-fix-CVE-2024-24806.patch
FAIL: test Signed-off-by presence: A patch file has been added without
On 19 Feb 2024, at 01:28, Peter Kjellerstedt via lists.openembedded.org
wrote:
> +@staticmethod
> +def addNote(repo, ref, key, value=None):
> +note = key + (": %s" % value if value else "")
> +notes_ref = GitApplyTree.notes_ref
> +runcmd(["git", "config",
On 19 Feb 2024, at 01:28, Peter Kjellerstedt via lists.openembedded.org
wrote:
>
> This makes use of the oe.patch.GitApplyTree.commitIgnored() function to
> create commits that shall be ignored by `devtool finish`.
If we’re using notes to store the filename info, couldn’t the ignores state
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-libuv-fix-CVE-2024-24806.patch
FAIL: test Signed-off-by presence: A patch file has been added without a
On Fri, 16 Feb 2024 at 12:34, Richard Purdie
wrote:
> I'm sure there are some things I'm forgetting too.
>
> Please let me know ASAP if there is anything else pending.
>
> The good news is that several problematic issues do seem to be finding
> resolutions in the last 48h.
Last week I got the
Thanks Ross,
I was too focus on English and French packages and missed this point.
Listing all items in CUPS added locale path is not OK. I should at least
only get directories (not files) in this path to create the locale list.
However, it remains an issue if some directories in the path would
From: Michael Haener
Add package for using the bridge tool.
Signed-off-by: Michael Haener
---
meta/recipes-connectivity/iproute2/iproute2_6.7.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-connectivity/iproute2/iproute2_6.7.0.bb
> Was there a reason why this wasn't merged in the end (other than being sent
> as RFC)?
I'm assuming you meant to reply to this one instead:
https://lists.openembedded.org/g/openembedded-core/message/190292
I did not include this in the final version as we ended up going in a bit of a
On Sat, 2024-02-17 at 12:38 +, Richard Purdie wrote:
> On Fri, 2024-02-16 at 19:40 +0800, Anuj Mittal wrote:
> > Drop patches that have been merged upstream and available in this
> > version.
> >
> > Signed-off-by: Anuj Mittal
> > ---
> > ...ix-minicom-h-v-return-value-is-not-0.patch | 33
38 matches
Mail list logo
