On Fri, Feb 23, 2024, 5:26 PM Konstantin Aladyshev
wrote:
> Thanks Richard! That did the trick!
>
> I've made the following changes to the "kern-tools-native_git.bb":
> ```
> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> b/meta/recipes-kernel/kern-tools/kern-tools-native_
Thanks Richard! That did the trick!
I've made the following changes to the "kern-tools-native_git.bb":
```
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 941160ea9c..7f8ea3e050 100644
--- a/meta/recipes-kernel/ke
On Fri, 2024-02-23 at 13:45 -0500, Bruce Ashfield wrote:
> On Fri, Feb 23, 2024 at 12:15 PM Konstantin Aladyshev
> wrote:
> >
> > Should I see the new git version in the linux-yocto devshell?
> > """
> > bitbake linux-yocto -c devshell
> > """
> >
> > I've tried to check it in the current poky m
Thanks Bruce! I would appreciate that.
Should we move this discussion to linux-yocto as well?
Best regards,
Konstantin
On Fri, Feb 23, 2024 at 9:45 PM Bruce Ashfield wrote:
>
> On Fri, Feb 23, 2024 at 12:15 PM Konstantin Aladyshev
> wrote:
> >
> > Should I see the new git version in the linux-y
On Fri, Feb 23, 2024 at 12:15 PM Konstantin Aladyshev
wrote:
>
> Should I see the new git version in the linux-yocto devshell?
> """
> bitbake linux-yocto -c devshell
> """
>
> I've tried to check it in the current poky master, and it gives me:
> """
> $/data/poky/build/workspace/sources/linux-yoc
Should I see the new git version in the linux-yocto devshell?
"""
bitbake linux-yocto -c devshell
"""
I've tried to check it in the current poky master, and it gives me:
"""
$/data/poky/build/workspace/sources/linux-yocto# git --version
git version 2.30.2
$/data/poky/build/workspace/sources/linux-
On Fri, Feb 23, 2024 at 6:43 AM Alexander Kanavin
wrote:
>
> On Fri, 23 Feb 2024 at 12:32, Konstantin Aladyshev
> wrote:
> > Thanks for the response! What would be a proper way to fix this problem
> > then?
>
> 1. show how to reproduce the issue in plain poky master.
> 2. check why none of the t
On Fri, 23 Feb 2024 at 12:32, Konstantin Aladyshev
wrote:
> Thanks for the response! What would be a proper way to fix this problem then?
1. show how to reproduce the issue in plain poky master.
2. check why none of the tests expose the issue. You can for example
grep related keywords in meta/lib
Hi, Alex!
Thanks for the response! What would be a proper way to fix this problem then?
Konstantin
On Fri, Feb 23, 2024 at 2:24 PM Alexander Kanavin
wrote:
>
> It's probably just a simple oversight. If the problematic code path is
> not taken in automated tests, no one will see the issue when i
It's probably just a simple oversight. If the problematic code path is
not taken in automated tests, no one will see the issue when it's
introduced by the commit.
Alex
On Thu, 22 Feb 2024 at 16:11, Konstantin Aladyshev
wrote:
>
> Hello!
> I was investigating some problems with the `devtool modif
Hello!
I was investigating some problems with the `devtool modify linux`
command and have discovered that part of the problems is generated
from the commit
https://git.yoctoproject.org/yocto-kernel-tools/commit/?id=923a9de418b3ca8592c3fd0a0d0b1e4b29533891
This commit is very simple and just adds th
11 matches
Mail list logo
