Avoid overwriting the dropbear configuration when the package gets
updated by adding it to the CONFFILES list.
Before:
root@qt5222:~# dpkg -i dropbear_2022.82-r0.26_amd64.deb
(Reading database ... 32509 files and directories currently installed.)
Preparing to unpack dropbear_2022.82-r0.26_amd64.de
Thanks Bruce!
Steve
On Mon, Jul 18, 2022, 5:46 PM Bruce Ashfield
wrote:
> We fixed this for 5.10/5.15, but missed 5.4.
>
> I ported the fix from those kernels to 5.4, and it now builds fine here.
>
> patch has been sent to the list.
>
> Bruce
>
> On Mon, Jul 18, 2022 at 2:19 PM Denys Dmytriyenk
On Tue, Jul 19, 2022 at 12:01 AM Denys Dmytriyenko wrote:
>
> On Mon, Jul 18, 2022 at 11:44:56PM -0400, Bruce Ashfield wrote:
> > From: Bruce Ashfield
> >
> > Integrating the following commit(s) to linux-yocto/5.4:
> >
> > cc478e363cc3 rt: fixup random and irq/manage merge issues
> >
> > Sign
On Mon, Jul 18, 2022 at 11:44:56PM -0400, Bruce Ashfield wrote:
> From: Bruce Ashfield
>
> Integrating the following commit(s) to linux-yocto/5.4:
>
> cc478e363cc3 rt: fixup random and irq/manage merge issues
>
> Signed-off-by: Bruce Ashfield
> ---
> meta/recipes-kernel/linux/linux-yocto-
We fixed this for 5.10/5.15, but missed 5.4.
I ported the fix from those kernels to 5.4, and it now builds fine here.
patch has been sent to the list.
Bruce
On Mon, Jul 18, 2022 at 2:19 PM Denys Dmytriyenko wrote:
>
> Oops, Richard's alias didn't get resolved properly the first time, sorry
>
>
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/5.4:
cc478e363cc3 rt: fixup random and irq/manage merge issues
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta
This is a dummy shared object therefore reduce dependencies further by
not requiring the C startup files, we wont use this shared library for
anything useful anyway
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/gcc-runtime.inc | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
On 7/18/22 23:09, Ross Burton wrote:
This patch has been rejected upstream, please switch for
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17439 instead.
OK.
Kai
Ross
On 18 Jul 2022, at 03:21, kai via lists.openembedded.org
wrote:
From: Kai Kang
It fails to compile mesa
Em seg., 18 de jul. de 2022 às 19:54, Richard Purdie <
richard.pur...@linuxfoundation.org> escreveu:
> On Mon, 2022-07-18 at 18:41 -0300, Otavio Salvador wrote:
> > Em seg., 18 de jul. de 2022 às 18:18, Richard Purdie
> > escreveu:
> > > > It does, indeed, but it doesn't seem related to this PR.
License-Update:
year updated to 2022
url of some reposity and license changed
file lists changed
Changelog:
===
- Drop support for Python 2.7, 3.5, and 3.6.
- Output changes:
HTML5:
Wrap groups of footnotes in an for easier styling.
The CSS rule .footnote-list { display: c
I have seen the results of devtool, and also diff two versions of COPYING.txt.
Sometimes, when the file differs greatly, I may not summarize them well
--
Best Regards
---
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd
On Mon, 2022-07-18 at 18:41 -0300, Otavio Salvador wrote:
> Em seg., 18 de jul. de 2022 às 18:18, Richard Purdie
> escreveu:
> > > It does, indeed, but it doesn't seem related to this PR.
> > >
> > > Do you know if this has worked?
> > >
> > > I am asking as I did all development and testing us
On Mon, Jul 18, 2022 at 4:06 PM Khem Raj wrote:
>
> Can you try something like this
>
> diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
> b/meta/recipes-devtools/gcc/gcc-runtime.inc
> index 5d74e4494d..61d5bf6058 100644
> --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> +++ b/meta/recipes-
In Yocto Honister if i use sha256crypt for my password hash my finished Linux
image can not like it, and at first boot it forces to me to change it. If i use
sha512crypt for my hash everything is ok at Linux first boot.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Em seg., 18 de jul. de 2022 às 18:18, Richard Purdie <
richard.pur...@linuxfoundation.org> escreveu:
> > It does, indeed, but it doesn't seem related to this PR.
> >
> > Do you know if this has worked?
> >
> > I am asking as I did all development and testing using SDKMACHINE ?=
> > 'x86_64' and ev
On Mon, 2022-07-18 at 16:25 -0300, Otavio Salvador wrote:
> Hello Richard and Khem
>
> Em seg., 18 de jul. de 2022 às 12:59, Richard Purdie
> escreveu:
> > On Mon, 2022-07-18 at 12:49 -0300, Otavio Salvador wrote:
> > > Em seg., 18 de jul. de 2022 às 09:45, Richard Purdie
> > > escreveu:
> > > >
Hi Livius,
On 6/3/22 23:45, Livius wrote:
Finaly, i found the problem and i could solve it. SHA-256 is too weak to make a
password hash, this is why on first login we need to change password always.
Please fix it in Yocto manual (
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoct
Can you try something like this
diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
b/meta/recipes-devtools/gcc/gcc-runtime.inc
index 5d74e4494d..61d5bf6058 100644
--- a/meta/recipes-devtools/gcc/gcc-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
@@ -68,8 +68,7 @@ do_configure () {
All,
Below is the list as of top 37 bug owners as of the end of WW29 of who have
open medium or higher bugs and enhancements against YP 4.1. There are 72
possible work days left until the final release candidates for YP 4.1 needs
to be released.
Who
Count
michael.opdenac...@bootlin.com
36
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc
Hello Richard and Khem
Em seg., 18 de jul. de 2022 às 12:59, Richard Purdie <
richard.pur...@linuxfoundation.org> escreveu:
> On Mon, 2022-07-18 at 12:49 -0300, Otavio Salvador wrote:
> > Em seg., 18 de jul. de 2022 às 09:45, Richard Purdie
> > escreveu:
> > > On Sun, 2022-07-10 at 13:43 -0300,
On Mon, Jul 18, 2022 at 08:31:39PM +0200, Bartosz Golaszewski wrote:
> Hi!
>
> It seems that the zephyr build is currently broken with master (and
> master-next) for meta-zephyr samples:
>
> Build Configuration:
> BB_VERSION = "2.0.1"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBS
I've contacted upstream. New release files (tarballs) are missing. The issue
may be fixed already.
--
Pavel
On Mon, Jul 18, 2022, at 20:02, Alexander Kanavin wrote:
> strace.io opens fine here. Can you check again please?
>
> Alex
>
> On Mon, 18 Jul 2022 at 16:09, Dragos-Marian Panait
> wro
Hi!
It seems that the zephyr build is currently broken with master (and
master-next) for meta-zephyr samples:
Build Configuration:
BB_VERSION = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-yocto-eabi"
MACHINE =
Oops, Richard's alias didn't get resolved properly the first time, sorry
On Mon, Jul 18, 2022 at 02:06:52PM -0400, Denys Dmytriyenko wrote:
> There's been some rework done around random subsystem lately. It now breaks
> RT
> kernel, at least on Aarch64, x86_64, maybe other platforms. Is there a
There's been some rework done around random subsystem lately. It now breaks RT
kernel, at least on Aarch64, x86_64, maybe other platforms. Is there a quick
fix, or should this update be reverted in Dunfell?
|
/OE/poky-dunfell/build/tmp/work-shared/qemuarm64/kernel-source/include/linux/random.h
strace.io opens fine here. Can you check again please?
Alex
On Mon, 18 Jul 2022 at 16:09, Dragos-Marian Panait
wrote:
>
> https://strace.io is down for some time now,
> so switching to https://github.com.
>
> Signed-off-by: Dragos-Marian Panait
> ---
> meta/recipes-devtools/strace/strace_5.18.
If you upgrade the package with 'devtool upgrade python3-docutils',
then devtool will write a diff of the license into the new recipe:
# --- COPYING.txt
# +++ COPYING.txt
# @@ -4,8 +4,8 @@
#
# :Author: David Goodger
# :Contact: good...@python.org
# -:Date: $Date: 2021-11-19 13:46:38 +0100 (Fr, 1
Am 18.07.22 um 19:08 schrieb Khem Raj:
On Mon, Jul 18, 2022 at 12:51 PM Martin Beeger wrote:
As discussied in [YOCTO #14717] cmake contains a OEToolchainConfig.cmake
file to configure the toolchain correctly in cross-compile build for recipes
using cmake. The CMAKE_ASM_FLAGS are the configurat
On Mon, Jul 18, 2022 at 12:51 PM Martin Beeger wrote:
>
> As discussied in [YOCTO #14717] cmake contains a OEToolchainConfig.cmake
> file to configure the toolchain correctly in cross-compile build for recipes
> using cmake. The CMAKE_ASM_FLAGS are the configuration are meant for
> assembly,
> b
As discussied in [YOCTO #14717] cmake contains a OEToolchainConfig.cmake
file to configure the toolchain correctly in cross-compile build for recipes
using cmake. The CMAKE_ASM_FLAGS are the configuration are meant for assembly,
but the spelling is incorrect and the Flag is ASFLAGS for gcc and oth
oh wait, I failed to send v2 of this patch. Will do so.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168242):
https://lists.openembedded.org/g/openembedded-core/message/168242
Mute This Topic: https://lists.openembedded.org/mt/89138781/21656
Grou
I looked further, and the variable is misspelt and should be CMAKE_AS_FLAGS to
have any effect. Furthermore, it is not recommended to set it explicitly, as
cmake will initialize it to the correct default. If the toolchain file from
open embedded in general contains ASFLGS, cmake wills et that as
This still seems overkill. You can build minizip from inside the zlib recipe
by fixing the minizip Makefile (fix posted to
https://github.com/madler/zlib/pull/681) and then adding one line to do_compile:
oe_runmake -C contrib/minizip CC="${CC}" CFLAGS="${CFLAGS}"
LDFLAGS="${LDFLAGS}"
A co
On Mon, 2022-07-18 at 12:49 -0300, Otavio Salvador wrote:
>
>
> Em seg., 18 de jul. de 2022 às 09:45, Richard Purdie
> escreveu:
> > On Sun, 2022-07-10 at 13:43 -0300, Otavio Salvador wrote:
> > > Signed-off-by: Otavio Salvador
> > > ---
> > >
> > > (no changes since v1)
> > >
> > > .../car
Em seg., 18 de jul. de 2022 às 09:45, Richard Purdie <
richard.pur...@linuxfoundation.org> escreveu:
> On Sun, 2022-07-10 at 13:43 -0300, Otavio Salvador wrote:
> > Signed-off-by: Otavio Salvador
> > ---
> >
> > (no changes since v1)
> >
> > .../cargo/cargo-cross-canadian.inc| 20 +++
On 12 Jul 2022, at 12:21, akash hadke via lists.openembedded.org
wrote:
> We can inherit cve-check by default in the configuration to export CVE
> information like CVE_PRODUCT, CVE_VERSION and the newly added variable
> CVE_PATCHED. And CVE_CHECK_WITH_DB variable will avoid scanning the CVEs fr
This patch has been rejected upstream, please switch for
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17439 instead.
Ross
> On 18 Jul 2022, at 03:21, kai via lists.openembedded.org
> wrote:
>
> From: Kai Kang
>
> It fails to compile mesa-native when DEBUG_BUILD is enabled:
>
>
From: Ross Burton
Normally m4-native ends up in the sysroot via the toolchain, but if a
non-standard toolchain is used them m4-native may not be installed.
However Pulseaudio explicitly checks for m4 in the meson.build, so add
it to DEPENDS.
Signed-off-by: Ross Burton
Signed-off-by: Richard Pu
From: Chanho Park
To support crate:// fetcher on externalsrc, we need to make pass-through
the URIs in SRC_URI.
Signed-off-by: Chanho Park
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard Purdie
Signed-off-by: Richard Pastrick
Signed-off-by: Steve Sakoman
---
meta/classes/externalsrc.bb
From: Chanho Park
To support crate:// fetcher on externalsrc, we need to remove "-z
${EXTERNALSRC} check of bitbake vendoring. It is possible to disable
vendoring by CARGO_DISABLE_BITBAKE_VENDORING = "1" if externalsrc-ed
project does not want to enablt it.
Signed-off-by: Chanho Park
Signed-off
From: Richard Purdie
We can't support vgem on RHEL derived distros so disable this test for
all almalinux hosts rather than specific versions.
Signed-off-by: Richard Purdie
(cherry picked from commit e921f3c1b917072e4c5a110c7dfeeadd2e571bde)
Signed-off-by: Steve Sakoman
---
meta/lib/oeqa/self
From: Richard Purdie
This fixes reproducibility issues with multilibs were a different recipe
specific sysroot is used which was leaking into debug symbols in libraries.
Signed-off-by: Richard Purdie
(cherry picked from commit f442edf51e256bd315bd8e4ac4d9fa12b8e9e092)
Signed-off-by: Steve Sakom
From: Richard Purdie
If gold is enabled as the default linker, it errors trying to link
to our dummy library empty file and this turns off things which should
be present in libstdc++.
For example, _GLIBCXX_HAVE_S_ISREG isn't defined and HAVE_S_ISREG in
libstdc++-v3/config.h isn't set properly.
From: Paul Eggleton
Add a test that verifies that devtool modify + devtool finish do the
right thing on a recipe that fetches from git and sets S to point to
a subdirectory of the source tree. We have a few examples among the core
recipes, dos2unix is a convenient one so let's use that. (The test
From: Paul Eggleton
If devtool finish needs to create a patch and have it applied to the
sources for a recipe where S points to a subdirectory of the sources,
then the patch needs to be applied at the root of the repo i.e. we need
to add a patchdir= parameter to the SRC_URI entry.
Signed-off-by:
From: Paul Eggleton
If PATCHTOOL = "git", SRC_URI fetches from a git repo and S points to
a subdirectory of the checked out sources, then we were erroneously
initialising the subdirectory as its own git repo. Check if the returned
top-level repo directory is a subdirectory of WORKDIR and do not
r
From: Pascal Bach
This makes the bin_package.bbclass work properly with the native class.
Signed-off-by: Pascal Bach
Signed-off-by: Richard Purdie
(cherry picked from commit ad330b6d4b6e2ba051b5c6c437e07a183831f757)
Signed-off-by: Steve Sakoman
---
meta/classes/bin_package.bbclass | 3 ++-
1
From: Paul Eggleton
If (perhaps foolishly) at your configuration level you have e.g.
SRC_URI_append_pn-recipename = " file://patchname.patch"
and then run devtool modify on a different recipe, an error occurs:
INFO: SRC_URI contains some conditional appends/prepends - will create
branches
From: Richard Purdie
Building external kernel modules like lttng-modules was showing build paths
inside the debug symbols for the modules and breaking build reproducibility.
Fix this by adding in the mapping needed to map the kernel build directory
to something more approriate on target.
Signed
From: Peter Marko
* add GPL license because of alsa-state-init file
* gpl link points to gpl3, but at time of adding this file was actually
pointing to gpl2, so should correspond to SPDX GPL-2.0-or-later
* remove date as the file was already changed several times since then
Signed-off-by: Rich
From: Ross Burton
We already exclude Makefile, makefile, and makefile.old from copy of the
perl source tree that is used by perl-ptest, but Makefile.old is not
being excluded. In a rebuild of perl with an existing source tree these
files now exist but have build paths in. As they're backup files
From: Richard Purdie
When api-documentation is enabled, we see a hardcoded build path to xsltproc in
the target python configuration file. We curate PATH carefully so we don't
need the path there, tweak configure to remove it and solve the issue.
Signed-off-by: Richard Purdie
(cherry picked fro
From: Khem Raj
Fixes
ERROR: QA Issue: :
/work/x86_64-linux/libmodule-build-perl-native/0.4231-r0/sysroot-destdir/work/x86_64-linux/libmodule-build-perl-native/0.4231-r0/recipe-sysroot-native/usr/bin/config_data
maximum shebang size exceeded, the maximum size is 128. [shebang-size]
Signed-off-b
From: Richard Purdie
The on target wrapper contains paths from the host build. Remove them.
Signed-off-by: Richard Purdie
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 10980ae59f18679413f2d3fd428a9386e4d6fc3a)
Signed-off-by: Steve Sakoman
---
meta
From: Richard Purdie
The .pc we install ourselves for lua has hardcoded /lib assumptions in it
which means in a multilib environment, full build paths end up in users
like rpm's configuration.
Fix the .pc file to use a correct includedir and libdir to resolve
those reproducibility issues.
Signe
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit cd05e2543bde4175da67781ec6f3eebc143d95d0)
Signed-off-by: Steve Sakoman
---
...build-request-native-wayland-scanner.patch | 27 +++
From: Richard Purdie
If enabled, the buildpaths test hangs in psplash as it tries to open
a fifo and read from it, hanging indefinitely.
Tweak the test to ignore fifo/socket/device files.
Signed-off-by: Richard Purdie
(cherry picked from commit 2567edb7e0a8c5ca9a88d6940491bf33bfe0eff9)
Signed-
From: Alejandro Hernandez Samaniego
Previous commit c725bdb29b266 broke kernel source handling, this was due
to the code expecting the sources to be in a different directory, this did
not happen when using externalsrc since sources were found in the expected
directories.
Pass work-shared to the
From: Christoph Lauer
Since commit d756b346f248df47b0540644adb1d0f17bcc4b6e kernel modules are
stripped by the functions 'runstrip' and 'splitdebuginfo'. Signed modules must
not be stripped. Function 'runstrip' avoids this by running
is_kernel_module_signed. Apply the same check to splitdebugi
From: Alejandro Hernandez Samaniego
While executing do_package, bitbake checks for a list of
debug source files and uses a pattern to match the ones
to be included in copydebugsources.
Previously when externalsrc was in use either directly or by
using devtool, the source location changed and thi
From: Markus Volk
This adds a backport patch that fixes a problem in subinterpreters related
to the garbagecollector. Without the patch, there are random segfaults in
several Kodi addons that use python3-sqlite3. Presumably there are real world
issues in other programs as well.
Signed-off-by: Ma
From: Ming Liu
The '.include' syntax has been dropped from latest systemd releases,
we need drop the systemd-udevd.service here, introduce a postinst
function to add "MountFlags=shared" to systemd-udevd.service.
Also lsblk binary is being called in mount.sh automount_systemd
function, add it to
From: Ming Liu
Since commit f077befd5f36ad88623aaf6a38b1a837ecb18650:
[ udev-extraconf: let automount base directory configurable ]
the mount base directory was configurable, we need drop 'run-media'
usage as well, change to figure it out from MOUNT_BASE.
Also 'get_label_name' function needs to
From: Muhammad Hamza
Failure message is shown in boot logs when trying to
mount lvm as automounter does not handle cases where
lvm is mounted. This simply skips lvm while automounting
to avoid failure message in boot logs.
Signed-off-by: Ansar Rasool
Signed-off-by: Muhammad Hamza
Signed-off-by
From: Muhammad Hamza
Automounting does not work cleanly in case systemd as well as
udev rules are being used simultaneously and in most cases
race conditions and unknown behavior can come up.
In case we're running on top of systemd we need to make sure
that systemd-udevd knows that udev is in pla
From: Muhammad Hamza
fdisk from util-linux (2.31.1) and above allows the user to
manipulate an already mounted device. In order to achieve this
functionality it issues a BLKRRPART (block device re-read part)
ioctl and in response the kernel generates remove/change/add
events if the device is not
From: Muhammad Hamza
Doing this will allow to fetch the exact name created by the
auto-mounter during the remove action where depending on the
scenario utilities such as the blkid might not be usable due
to actual device not being present on the system.
Signed-off-by: Awais Belal
Signed-off-by:
From: Muhammad Hamza
This alters the mountpoints such that if a device has a LABEL or
a PARTLABEL, it will be mounted at e.g.:
/run/media/$LABEL-
/run/media/$PARTLABEL-
/run/media/rootfs-sda2
otherwise the device will be mounted at e.g.:
/run/media/
/run/media/sda1
The appended wit
From: Richard Purdie
Signed-off-by: Richard Purdie
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard Purdie
(cherry picked from commit 69e486ddb3059f80ba538e1f59c2ca8a8df0faf9)
Signed-off-by: Ming Liu
Signed-off-by: Steve Sakoman
---
.../initrdscripts/files/init-install-efi-testfs.sh
From: Ming Liu
Dont hard-code automount base directory to '/run/media', introduce a
variable MOUNT_BASE to let it configurable, like in udisks2 the mount
base is also configurable by setting option: --enable-fhs-media.
Signed-off-by: Ming Liu
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard
From: Pavel Zhukov
Fixup commit for prevous CVE-2022-33068 fix.
Fixes:
| In file included from ../harfbuzz-4.0.1/src/hb-ot-face.cc:39:
4429| ../harfbuzz-4.0.1/src/hb-ot-color-sbix-table.hh:301:11: error: use of
bitwise '|' with boolean operands [-Werror,-Wbitwise-instead-of-logical]
4430|
From: Robert Joslyn
Backport fixes for:
* CVE-2022-32205 - https://curl.se/docs/CVE-2022-32205.html
* CVE-2022-32206 - https://curl.se/docs/CVE-2022-32206.html
* CVE-2022-32207 - https://curl.se/docs/CVE-2022-32207.html
* CVE-2022-32208 - https://curl.se/docs/CVE-2022-32208.html
Signed-off-b
Please review this set of patches for kirkstone and have comments back by
end of day Wednesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3928
The following changes since commit 171415e38e526033a0423f4dc39e9d8e9dc4e5f6:
perf: fix reproduci
On Sun, Jul 17, 2022 at 8:42 PM Yi Zhao wrote:
>
> Hi Steve,
>
>
> On 5/24/22 16:33, wangmy wrote:
> > Changelog:
> > ==
> > [security]
> > Fix a crash in DNS-over-HTTPS (DoH) code caused by
> > premature TLS stream socket object deletion.
> > (CVE-2022-1183) [GL #3216]
>
>
> There i
https://strace.io is down for some time now,
so switching to https://github.com.
Signed-off-by: Dragos-Marian Panait
---
meta/recipes-devtools/strace/strace_5.18.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/strace/strace_5.18.bb
b/meta/recipes-dev
An intermittent failure occurs in libical-native do_compile:
| Traceback (most recent call last):
| File
"/.../build/tmp/work/x86_64-linux/libical-native/3.0.14-r0/recipe-sysroot-native/usr/lib/python3.10/shutil.py",
line 813, in move
| os.rename(src, real_dst)
| OSError: [Errno 18] Invali
On Sun, 2022-07-10 at 13:43 -0300, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador
> ---
>
> (no changes since v1)
>
> .../cargo/cargo-cross-canadian.inc| 20 ++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
I did look into this with some local testing.
On 12 Jul 2022, at 16:28, Khem Raj via lists.openembedded.org
wrote:
>
> the ltp patch is upstream worthy. Have you thought about sending it to
> the ltp community ?
See the patch header:
>> +Upstream-Status: Submitted
>> [https://github.com/linux-test-project/ltp/pull/948]
That should now
From: Wentao Zhang
Backport patch from
https://github.com/harfbuzz/harfbuzz/commit/e421613e8f825508afa9a0b54d33085557c37441
Signed-off-by: Wentao Zhang
---
.../harfbuzz/harfbuzz/Fix-conditional.patch | 27 +++
.../harfbuzz/harfbuzz_4.0.1.bb| 3 ++-
2 files ch
FYI: This might be causing build issues with ld-is-gold:
| i686-webos-linux-ld: error: kvm_pagefault01-payload.bin:1:1: invalid
character
| ltp/20220527-r0/git/testcases/kernel/kvm/Makefile:55: recipe for target
'kvm_pagefault01-payload.o' failed
| make[3]: *** [kvm_pagefault01-payload.o] Error 1
81 matches
Mail list logo
