Can you try the tip of master please?
Alex
On Mon, 21 Nov 2022 at 13:32, Marek Belisko wrote:
>
> Hi,
>
> on kirkstone branch when trying to build rust for raspberrypi machine
> I'm getting:
>
> ERROR: rust-cross-arm1176jzfshf-vfp-glibc-1.59.0-r0
> do_rust_gen_targets: Error executing a python
Does this mean that master should be excluded too?
Alex
On Fri, 18 Nov 2022 at 15:28, Steve Sakoman wrote:
>
> langdale isn't currently supported on any branch of meta-agl
>
> Signed-off-by: Steve Sakoman
> ---
> config.json | 17 -
> 1 file changed, 17 deletions(-)
>
> diff
You have to define an additional distribution I'm afraid. It can share
almost everything with the existing distro, but set PREFERRED_PROVIDER
differently.
Alex
On Thu, 17 Nov 2022 at 16:22, Maik Vermeulen
wrote:
> Hi,
>
> Depending on the image that's being built, e.g. development vs.
>
Making your own! You can have it added to the layer index for better publicity.
Alex
On Thu, 17 Nov 2022 at 13:27, Yishai Jaffe wrote:
>
> What layer would you suggest?
>
> Yishai Jaffe
>
> On Thu, Nov 17, 2022, 2:21 PM Alexander Kanavin
> wrote:
>>
with it all the way. You can decide if to include pyc files but not
> the opposite. Also, this feature which does exist only applies to the python
> recipe but not to all other non-base python module recipes. Maybe this can be
> added to setuptools3 bbclass?
>
> Yishai Jaffe
>
>
:
> tar.bz2 - 5.8MB
> squashfs-xz - 5.2MB
>
> So that's about a 15% decrease in size.
> Again, this is for an image only with python3-core. Logically that would mean
> that if you had an image with more python packages it would be even a bigger
> percentage.
>
>
> Yisha
This is the correct way, yes. You can put SDKMACHINE into local.conf
(default is 'linux sdk'), or you can specify it on command line (in
which case it will override the local.conf setting).
Alex
On Tue, 15 Nov 2022 at 13:02, Johann Obermayr via
lists.yoctoproject.org
wrote:
>
> Hello,
>
>
>
>
Generally we slim down python installations by not installing all of
the standard library, and rather having precise dependencies for
specific modules. Can you illustrate the kind of space savings that
can be gained in actual numbers?
Another issue is that this should be supported upstream and in
You need to show the whole log.
Alex
On Fri, 11 Nov 2022 at 07:29, Mistyron wrote:
>
> Hi,
>
> I'm wondering how to resolve the following error:
>
> ERROR: sample-image-cp-lwb5plus-1.0-r0 do_rootfs: Postinstall scriptlets of
> ['lrd-networkmanager-sterling'] have failed. If the intention is to
On Mon, 7 Nov 2022 at 18:57, Ron Eggler wrote:
> Exactly, the customer will have full access to the source code incl. the
> complete set of Yocto layers and all.
>
Then your best option is to drop meta-gplv2 layer from builds altogether.
This will update everything to current, compatible
On Mon, 7 Nov 2022 at 16:13, Ron Eggler wrote:
> > Are you able to fulfil that obligation you have under the license?
>
> Yes, that will definitely be doable for the recepient if they chose to
> do so.
I'm curious as to how though. Are you going to give them a complete
set of yocto layers and
On Mon, 7 Nov 2022 at 03:19, Ron Eggler wrote:
> > On Sun, 6 Nov 2022 at 18:36, Mistyron wrote:
> >> I'll attempt to "just drop" meta-gplv2, then. However I see that there are
> >> other dependencies on readline too, i.e. it might be easier to just
> >> replace the existing 5.2 version in
On Mon, 7 Nov 2022 at 02:35, Ron Eggler wrote:
> > Are you going to ship what you're working on to other users, or is it
> > just experimentation?
> The intent is, that's it's going to be shipped (but with full access to
> the sources)
If you're shipping anything that is under gplv3 you also
On Sun, 6 Nov 2022 at 18:36, Mistyron wrote:
> I'll attempt to "just drop" meta-gplv2, then. However I see that there are
> other dependencies on readline too, i.e. it might be easier to just replace
> the existing 5.2 version in meta-gplv2 with 8.2 from here:
>
On Sun, 6 Nov 2022 at 17:48, Anders Montonen wrote:
> If your project doesn’t have any special requirements about not using
> (L)GPLv3-licensed packages, then dropping meta-gplv2 is by far the best
> option.
> The dependency on readline comes from Networkmanager’s user interfaces
> (nmcli,
It may help if you show the complete logs for configure and compile ,
otherwise there is not enough information in your message to diagnose the
issue.
Alex
On Sun 6. Nov 2022 at 8.45, Mistyron wrote:
> Hi,
>
> I'm working with dunfell and want to compile and install the drivers for
> the Laird
This is probably not available in dunfel, but in master there are
bbclasses that handle this:
inherit pypi python_setuptools_build_meta
So try with master, and then consider your options.
Alex
On Fri, 4 Nov 2022 at 00:03, John Klug wrote:
>
> I am using Dunfell.
>
> What should I do in a
It is not possible to say what went wrong if I cannot see the changes
you did, what commands you type, and what is the outcome (vs. what you
expect). So you need to publish your code somewhere, and describe all
of those things.
Alex
On Tue, 1 Nov 2022 at 08:37, Nikita Gupta wrote:
>
> Hello
You need to be more specific, otherwise it is not clear how can we
help. Show exactly what you did, and what happened (or didn't happen
even though you expected that).
The basic way to trim dependencies is to set PACKAGECONFIG to a minimal set.
Alex
On Mon, 31 Oct 2022 at 02:34, Priyanshu
There is a version mismatch. If you want to patch the 5.4 kernel, why
is the bbappend for 4.12?
Alex
On Sat, 29 Oct 2022 at 13:38, Nikita Gupta wrote:
>
> Hello List
>
> i want to apply rt-patch in raspberry-pi by following
> (using-traditional-kernel-development-to-patch-the-kernel) So in
On Thu, 27 Oct 2022 at 19:51, wrote:
> linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with
> machine beaglebone-yocto (not in COMPATIBLE_MACHINE)
This is the key piece. Beaglebone target only allows a standard non-rt
kernel. Perhaps Bruce can clarify the steps needed to
On Mon, 24 Oct 2022 at 13:58, Peter via lists.yoctoproject.org
wrote:
> However, the documentation recommends the global ban and does not mention the
> per-image variant?
> https://docs.yoctoproject.org/ref-manual/images.html
>
? Some go convention
> I don't know about...
>
> ____
> Von: Alexander Kanavin
> Gesendet: Donnerstag, 20. Oktober 2022 12:09:47
> An: Roos, Thomas
> Cc: yocto@lists.yoctoproject.org
> Betreff: RE: [EXTERNAL][yocto] devtool upgrade for
fetcher.ud[url].parm['destsuffix'] = os.path.join(s_dirname,
> '', d.getVar('GO_IMPORT')) + '/'
> #FIX
> fetcher.unpack(d.getVar('WORKDIR'))
> }
>
> # src folder will break devtool upgrade
> go_do_configure() {
> #cause problems ln -snf ${S}/src ${B}/
> #FIX
> ln -snf $
pts/lib/devtool/upgrade.py", line 134, in
> _upgrade_error
> _cleanup_on_error(rd, srctree)
> File "/home/ubuntu/yocto/poky/scripts/lib/devtool/upgrade.py", line 126, in
> _cleanup_on_error
> if not len(os.listdir(rdp)):
> FileNotFoundError: [Errno 2] N
It helps if you show the exact error, and a way to reproduce this
using a minimal setup (ideally only poky).
Alex
On Thu, 20 Oct 2022 at 11:18, Thomas Roos via lists.yoctoproject.org
wrote:
>
> Hi,
> when doing a "devtool upgrade" for a recipe which inherits "go" and using a
> SRC_URI to a git
This would be a much welcome feature. I suspect however that devtool
relies on the current target, and won't be easily convinced to update
other targets.
Alex
On Thu, 20 Oct 2022 at 10:51, Thomas Roos via lists.yoctoproject.org
wrote:
>
> Hi,
> wondering if it's possible when doing a "devtool
he info you wanted.
>
> Am 10. Oktober 2022 15:04:18 MESZ schrieb Alexander Kanavin
> :
>>
>> You still have not introduced yourself.
>>
>> I have reproduced; the key difference is that you are building for
>> qemuarm64. This does seem like a bug somewhere,
he command!
>
> Regards
>
> Am 10. Oktober 2022 05:55:35 MESZ schrieb Alexander Kanavin
> :
>>
>> It works for me. If it does not work for you, you need to show the full
>> content of your local modifications and full content of error messages, and
>> pre
MESZ schrieb Alexander Kanavin <
> alex.kana...@gmail.com>:
>>
>> That depends on what is your target. If you're running qemu on a x86
>> host, it's better to not do software emulation and build for
>> qemux86_64 as well, and then run qemu with kvm, so it exe
://git.yoctoproject.org/poky/tree/meta/lib/oeqa/selftest/cases/incompatible_lic.py#n100
Alex
On Fri, 7 Oct 2022 at 11:35, Alexander Kanavin via
lists.yoctoproject.org
wrote:
>
> For what it's worth, I have eliminated meta-gplv2 from the
> infotainment stack (e.g. a major build) of a major ca
For what it's worth, I have eliminated meta-gplv2 from the
infotainment stack (e.g. a major build) of a major car OEM, so this is
doable. It would help if you bring up specific issues that you see and
we try to figure out how to solve them, and come up with a list of
'standard practices'. Even
On Thu, 6 Oct 2022 at 15:27, Peter via lists.yoctoproject.org
wrote:
> "It is over. There are no excuses left if you are still using meta-gplv2."
> -- https://twitter.com/yoctoproject/status/1552209990148145153
> "There are other ways of removing GPLv3 components from modern OE/YP builds
> and
On Wed, 5 Oct 2022 at 19:47, Michael Opdenacker
wrote:
> Thank you for the proposed documentation.
> Do you want me to look for an appropriate place in the documentation
> sources where it could be included, and then propose a patch?
The middle section is actually copied from documentation (I
l these
> information as I didn't find all these info in one document.
>
> As I am new in this thing please guide me . Your guidance is highly
> appreciated.
>
>
>
> On Tue, Oct 4, 2022, 18:31 Alexander Kanavin wrote:
>>
>> The log file seems truncated?
>
The log file seems truncated?
To enable the standard rt test, use
TEST_SUITES:append = ' rt'
as seen in
https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json#n1138
and build core-image-full-cmdline. core-image-rt is not well tested
unfortunately.
Alex
On Sun, 2 Oct 2022 at
It helps if you show log.do_rootfs for the image, so it's possible to
inspect what actually got installed into it.
Alex
On Sun, 2 Oct 2022 at 09:29, Nikita Gupta wrote:
>
> Hello All,
>
> I have made a preempt-rt image with "core-image-rt" by including the
> following line in local.conf file.
or do you mean arm?
>
> Am 30. September 2022 22:39:44 MESZ schrieb Alexander Kanavin
> :
>>
>> You might want to try enabling gallium-llvm only for the target mesa:
>>
>> PACKAGECONFIG:append:x86-64:pn-mesa = ' gallium-llvm'
>>
>> Alex
>&
r changes for mesa.inc.
> After a few hours of building core-image-weston it again complains that it
> tries to copy llcm-config14.0.6 over itself. I don't know what to do anymore.
>
> ____
> From: Alexander Kanavin
> Sent: Thursday, September 29, 202
Am 28. September 2022 13:37:05 MESZ schrieb Alexander Kanavin <
> alex.kana...@gmail.com>:
>>
>> Try latest poky master?
>>
>> Alex
>>
>> On Wed, 28 Sept 2022 at 13:23, PHIL wrote:
>>
>>>
>>> Mesa build fails. It complains tha
Try latest poky master?
Alex
On Wed, 28 Sept 2022 at 13:23, PHIL wrote:
>
> Mesa build fails. It complains that it copies llvm-config14.0.6 to the same
> file.
>
> Am 28. September 2022 12:48:04 MESZ schrieb Alexander Kanavin
> :
>>
>> The following works for me.
freedreno', '', d)}"
Alex
On Wed, 28 Sept 2022 at 11:49, PHIL wrote:
>
> Also vulkan-drivers is empty in meson generated by bitbake. If I add it
> manually it will complain that llvm is disabled. How would I enable it?
>
> Am 28. September 2022 10:51:26 MESZ schrieb Alexander Kan
ill get ERROR_INCOMPATIBLE_DRIVER when running vulkaninfo.
>
> What am I missing for Software Mode?
>
> Am 28. September 2022 10:29:28 MESZ schrieb Alexander Kanavin
> :
>>
>> I would first check whether any of that work in the branch has meanwhile
>> landed upstrea
ollabora.com/news-and-blog/blog/2021/11/26/venus-on-qemu-enabling-new-virtual-vulkan-driver/
>
> According to the author the modified qemu branch is still necessary so I
> want to enable that.
>
>
> Am 28. September 2022 10:14:24 MESZ schrieb Alexander Kanavin <
> ale
You need to clarify what you want to do exactly. Why can’t you use the
existing recipe?
Alex
On Wed 28. Sep 2022 at 9.58, Edgar Mobile wrote:
> Greetings,
>
> I want to change the git repo url in order to test the Venus driver. Can
> someone tell me which variable in which recipe I'd have to
Do keep in mind that PARALLEL_MAKE can and should be set per recipe,
so you can make-limit only the worst items.
Alex
On Tue, 27 Sept 2022 at 10:34, Westermann, Oliver
wrote:
>
> > Am Montag, 26. September 2022 19:33 schrieb Alexander Kanavin
> >
> >
> > An
Anything written in C++ tends to consume 1-2 Gb of ram per compiler
process. If that lands you in OOM, you probably should limit that with
PARALLEL_MAKE:pn-nodejs, but otherwise that is the sad reality of C++
builds.
Alex
On Mon, 26 Sept 2022 at 19:20, Oliver Westermann via
TL;DR version
=
If you want to get everything needed to run a yocto build:
- clone the bootstrap repository (ask your distribution maintainer where it is):
$ git clone bootstrap_repo_uri
- run 'setup-layers' from that repo:
$ /path/to/bootstrap_repo/setup-layers
If you want
l command as I can not find
> an environment variable that has it.
>
> Regards
>
> ________
> From: Alexander Kanavin
> Sent: Friday, September 23, 2022 1:45 PM
> To: Edgar Mobile
> Cc: Yocto-mailing-list
> Subject: Re: [yocto] Building v
I finally got a moment to look at this. The binary with the samples is
being built (you can find it in
$WORKDIR/build/app/bin/x86_64/vulkan_samples), but is not installed.
So if you want to get it packaged for targets you need to adjust the
recipe and add a do_install:append() section that does it
rs etc. I don't know how to process from here.
>
> Am 21. September 2022 14:38:10 MESZ schrieb Alexander Kanavin
> :
>>
>> You need to check package-split/ to find out why.
>>
>> Alex
>>
>> On Wed, 21 Sept 2022 at 14:30, PHIL wrote:
>>>
>&
an_virtio.so but they are not installed to the Image.
>
> Am 21. September 2022 14:14:10 MESZ schrieb Alexander Kanavin
> :
>>
>> This is not logs from mesa, this is logs from your image recipe. You
>> need to start with mesa.
>>
>> Alex
>>
>> On Wed, 21 Se
ro-base-1.0-r83.qemuarm64
> (try to add '--skip-broken' to skip uninstallable packages)
>
> Am 21. September 2022 13:57:17 MESZ schrieb Alexander Kanavin
> :
>>
>> You need to go to mesa's build directlory and inspect what is getting
>> built, with which
(and then do_compile and do_install).
Alex
On Wed, 21 Sept 2022 at 13:38, PHIL wrote:
>
> If I read the mesa-vulkan-drivers recipe right it should install
> libvulkan_*.so but it didnt I had to use vulkan-loader. Any idea in how to
> debug that?
>
> Am 20. September 2022 15:26:45 MESZ schrieb
What often works is running it under strace - you might be able to see the
one key syscall that causes the failure. Otherwise you might have to go
through the heavier gdb step through.
Alex
On Tue 20. Sep 2022 at 10.25, PHIL wrote:
> Ok it seems to use Software now given how slow
r 2022 10:23:38 MESZ schrieb Alexander Kanavin <
> alex.kana...@gmail.com>:
>>
>> Don’t bother with virgl yet. Start with the pure software implementation
>> in Mesa.
>>
>> Alex
>>
>> On Tue 20. Sep 2022 at 8.39, Edgar Mobile wrote:
>>
&g
m-native',
> 'virglrenderer-native', 'ninja-nativevulkan-loader'
>
> --
> *From:* Markus Volk
> *Sent:* Monday, September 19, 2022 5:16 PM
> *To:* Edgar Mobile
> *Cc:* Alexander Kanavin ;
> yocto@lists.yoctoproject.org
> *Subject:* Re: [yocto] Addi
ing meson_options.txt the recommended way to customize Mesa in
> Yocto?
>
> --
> *From:* Alexander Kanavin
> *Sent:* Monday, September 19, 2022 2:36 PM
>
> *To:* Edgar Mobile
> *Cc:* yocto@lists.yoctoproject.org
> *Subject:* Re: [yocto] Addi
vulkan package? meson logs show it wasnt't compiled with
> vulkan-drivers.
>
> --
> *From:* Alexander Kanavin
> *Sent:* Monday, September 19, 2022 2:20 PM
>
> *To:* Edgar Mobile
> *Cc:* yocto@lists.yoctoproject.org
> *Subject:* Re: [yocto] A
>
> Regards
>
> ------
> *From:* Alexander Kanavin
> *Sent:* Monday, September 19, 2022 1:31 PM
>
> *To:* Edgar Mobile
> *Cc:* yocto@lists.yoctoproject.org
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> As I said you nee
l more samples?
>
> --
> *From:* Alexander Kanavin
> *Sent:* Monday, September 19, 2022 8:25 AM
>
> *To:* Edgar Mobile
> *Cc:* yocto@lists.yoctoproject.org
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I suppose you need
t see any sample binaries
> that look like Vulkan. Is there a list somewhere for all the files in
> vulkan-samples?
> Regards
>
> ------
> *From:* Alexander Kanavin
> *Sent:* Saturday, September 17, 2022 8:28 AM
>
> *To:* Edgar Mobile
> *Cc:* y
CORE_IMAGE_EXTRA_INSTALL list.
Alex
On Fri, 16 Sept 2022 at 19:17, Edgar Mobile wrote:
>
> Ok, so I switched to Kirkstone and added vulkan-samples to
> CORE_IMAGE_EXTRA_INSTALL.
> But no libvulkan.so in /usr/lib.
>
> Am I missing something?
>
> __
You can start by adding vulkan-samples to the image - the recipe is in
core. We do not test vulkan in qemu, because the software vulkan
rendering is still under active development, and marked as
experimental in virglrenderer.
It may help if you use qemux86_64 and kvm for it, because software
ependencies I need under
> https://github.com/priv-kweihmann/meta-sca
> That means at least I don't have to do them all myself.
>
> Thanks
>
>
>
> Ed Watson
> Tel: +46 702053827
>
>
>
> On Wed, 14 Sept 2022 at 20:53, Alexander Kanavin
> wrote:
>>
&
will compose the source tree in a 'vendored' fashion.
Alex
On Wed, 14 Sept 2022 at 20:05, Ed Watson wrote:
>
> Hello
>
> Sure thanks it is https://github.com/aler9/rtsp-simple-server
>
> Ed Watson
>
>
>
>
> On Wed, 14 Sept 2022 at 19:53, Alexander Kanavin
> w
It helps if you can name the project. Are the sources public?
Alex
On Wed 14. Sep 2022 at 18.42, wrote:
> Hello,
>
>
> I am trying to include a go project in my yocto build. It has quite a few
> dependencies. I may have missed something, there is a meta-go around that I
> have missed? Or a
With the recent template config changes to oe-core its content is no longer
backwards compatible.
'-f' is to guarantee future compatibility with build setups where the file
is not present.
Signed-off-by: Alexander Kanavin
---
scripts/run-patchmetrics | 1 +
1 file changed, 1 insertion(+)
diff
question, does this issue exist in kirkstone-4.0.2 ?
>
> Thanks,
> Steve
>
> -Original Message-
> From: Alexander Kanavin
> Sent: Wednesday, August 31, 2022 7:42 AM
> To: Monsees, Steven C (US)
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #yocto
he kernel comes up with errors...
>
> Will full wayland support be added to the dunfell release ?
>
> Steve
>
> -Original Message-
> From: yocto@lists.yoctoproject.org On Behalf
> Of Alexander Kanavin
> Sent: Wednesday, August 31, 2022 7:23 AM
You need to run this in a X11 session, or use 'nographic' parameter.
Alex
On Wed, 31 Aug 2022 at 13:17, Monsees, Steven C (US) via
lists.yoctoproject.org
wrote:
>
>
>
> Hello:
>
>
>
> I am attempting to evaluate dunfell -23.0.17, on a cetos7 linux box.
>
>
>
> When building the default :
On Tue, 30 Aug 2022 at 22:40, Richard Purdie
wrote:
> I think I may be lagging a little behind on status. I did see a lot of
> confusion about the patches and I know they didn't make the last
> testing cut. Hopefully they'll be in the next patch.
I just resent the complete patchset (across three
On Tue, 30 Aug 2022 at 22:40, Richard Purdie
wrote:
> > > operl builds hanging indefinitely:
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
> >
> > I will look into this. Findings will go into the ticket.
>
> Thanks! We haven't quite found the exact trigger to reproduce it but
On Tue, 30 Aug 2022 at 22:40, Richard Purdie
wrote:
> Thanks! We haven't quite found the exact trigger to reproduce it but it
> seems related to rebuilds somehow.
Yes, this usually happens when new patches from master get pulled in
and perl is rebuilding on top of a previous build. It then
On Tue, 30 Aug 2022 at 16:49, Stephen Jolley wrote:
> layer setup changes didn’t test successfully
The latest patchset has no known issues.
> operl builds hanging indefinitely:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
I will look into this. Findings will go into the
One option is to actually build an image for a qemux86_64 machine with the
items you need (or qemuarm64 if that's your build host), then use 'runqemu
kvm' to get native execution speed in a fully virtualized environment.
'native' recipes are generally meant as a springboard to get the binaries
You need to rebuild the image:
bitbake core-image-minimal
Alex
On Mon, 22 Aug 2022 at 12:32, Nikita Gupta wrote:
>
> Hello
>
> i was not able to find that how to force a no-graphical execution by unset
> Display before running bitbake . So i again tried to test my image by
> previous method
The neat way would be to include appropriate configuration into the
webserver recipe, e.g. a file installed in /etc/firewall.d/ that opens the
port (and nothing else).
Alex
On Tue, 16 Aug 2022 at 10:35, Maik Vermeulen
wrote:
> Hi,
>
> Currently we are struggling with 'interdependent' recipes.
It's hard to say what happens if we can't see your recipes. Can you
publish them?
Alex
On Mon, 15 Aug 2022 at 00:54, Gian Lorenzo Meocci wrote:
>
> Inside the do_install I copy some files
> but it seems that bitbake set those files in the RDEPENS.
>
> In the log during the do_root_fs I see:
>
Then you need to check the output of 'env'
a) when you start the shell
b) when you use oe-init-build-env
and figure out how the incorrect variable gets into the environment.
Are you using oe-init-build-env from an old yocto?
Alex
On Sat, 13 Aug 2022 at 15:02, Kaiwan N Billimoria
wrote:
>
>
Hello,
you probably need to exit the shell and then restart it and
re-initialize your environment (with oe-init-build-env), as it
contains the obsolete variable.
Alex
On Sat, 13 Aug 2022 at 05:13, wrote:
>
> Hellow everyone, this is Yan. I am new to Yocto Project, still, I am learning.
>
>
You need to run runqemu inside a graphical X11 session (we do not
support pure wayland yet). Alternatively, use 'publicvnc' parameter,
and connect with a vnc client (e.g. tigervnc) to port 5900 on the
machine where runqemu runs.
Alex
On Mon, 8 Aug 2022 at 11:36, Nikita Gupta wrote:
>
> Hello
I don't have a ready example, but you can start by reading
meta/classes/insane.class - I think all of the things defined in it
are extensible from a different class.
Alex
On Sun, 7 Aug 2022 at 21:21, Paul Wicks wrote:
>
> Is it possible to create additional QA checks such that they apply to all
A patch to address this would be appreciated.
Alex
On Wed, 3 Aug 2022 at 03:36, Craig McQueen
wrote:
> I've recently been upgrading from dunfell to kirkstone. I see a regression
> in the resolvconf package, so DNS lookups aren't functional.
>
> I see in /var/log/messages:
>
> Aug 2 19:39:31
ork/exec.go:187 +0x3da
> | Makefile:72: recipe for target 'install' failed
> | make: *** [install] Error 2
> | make: Leaving directory
> '/builddir/randomfirmware/build/tmp/work/x86_64-linux/mender-artifact-native/3.8.0-r0/git/src/github.com/mendersoftware/mender-artifact'
> | ERROR: oe_r
There's no way to build two versions of the same component, if the
versions share the recipe name. You have to fix the application, or
try to rename one set of the go recipes so it is separate from the
other set, to something like 'go-old'.
Alex
On Tue, 2 Aug 2022 at 15:15, Sebastian Rühl via
On Wed, 20 Jul 2022 at 17:46, Alexander Kanavin via
lists.yoctoproject.org
wrote:
>
> On Wed, 20 Jul 2022 at 17:41, Mittal, Anuj wrote:
> > I don't know if there are any Yocto users of it who might notice.
> >
> > Instead of dropping the testing completely,
There has been a persistent stream of graphical failures on x32,
and there is doubt about whether x32 is at all used by anyone
nowadays - let's reduce the scope of x32 QA, and perhaps
later drop it altogether.
Signed-off-by: Alexander Kanavin
---
config.json | 4 ++--
1 file changed, 2
On Wed, 20 Jul 2022 at 17:41, Mittal, Anuj wrote:
> I don't know if there are any Yocto users of it who might notice.
>
> Instead of dropping the testing completely, may be we should switch to
> building/testing just the core-image-minimal image on autobuilder and
> keep at least some minimal
This works as intended.
So the problem is that when qemu runs from testimage it tries to open
a graphical window using X and that for some reason fails. You can
perhaps force a no-graphical execution by
unset DISPLAY
before running bitbake.
Alex
On Wed, 20 Jul 2022 at 12:44, Nikita Gupta
Can I also see the output of 'runqemu nographic' please?
Alex
On Wed, 20 Jul 2022 at 12:25, Nikita Gupta wrote:
>
> Hello Alexander
>
> Please find the output of 'env' below .
>
> SHELL=/bin/bash
> SESSION_MANAGER=local/Linux:@/tmp/.ICE-unix/1288,unix/Linux:/tmp/.ICE-unix/1288
>
On Wed, 20 Jul 2022 at 12:00, Marko Lindqvist wrote:
> How much difference is there between x32 and riscv32 in upstreams? As
> they would trip on the same issues, one would assume that if the issue
> is fixed for one, it gets fixed for the other too.
> But might be that relevant upstreams need
On Wed, 20 Jul 2022 at 11:50, Ross Burton wrote:
> Also, Intel should get to have an opinion on this. If they actually care
> about x32 then they can help fix the issues, if they don’t then we can easily
> switch to a platform that has support.
Ok, let's ask Intel, specifically Anuj :-)
On Wed, 20 Jul 2022 at 11:23, Richard Purdie
wrote:
> That amounts to dropping x32 support because as soon as we remove these
> tests, it will bitrot.
>
> There is still some value in the project being able to support
> different architectures and different type sizes so I do still lean
> towards
to ship anything
to customers, and was only devised to look better in benchmarks
against competition.
Alex
On Wed, 20 Jul 2022 at 10:44, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> Signed-off-by: Alexander Kanavin
> ---
> .../rpm/files/0001-CVE-2021-3521.patch
This is not what I asked for (which was output of 'env'). Also, this
shows the output of bitbake -c testimage, not of runqemu with
nographic parameter.
Alex
On Wed, 20 Jul 2022 at 09:07, Nikita Gupta wrote:
>
> Hello Alexander,
>
> Please find the output file in attachment .
>
> Thanks
>
>
Can I see the output of 'env' please?
Alex
On Tue, 19 Jul 2022 at 20:45, Nikita Gupta wrote:
>
> Hello Alexander
>
> Yes I have tried that already but i am getting same error.
> If anyone could it would be great.
>
> Thanks in advance
>
> On Wed, Jul 20, 2022, 00:
You can try adding nographic option to runqemu if you do not need to
see graphical output from your image.
Alex
On Tue, 19 Jul 2022 at 20:30, Nikita Gupta wrote:
>
> Hello Alexander,
>
> Thanks for your precious time .
>
> I applied you suggestion and it worked and i setup tap interface with
>
This is optional, enabled by default, and allows easy extraction of patches
and other information to one's local disk (no need to go over individual
maintainer
emails).
Signed-off-by: Alexander Kanavin
---
upgrade-helper.conf | 4
upgrade-helper.py | 14 ++
2 files changed
MIMEBase should not be used directly and results in
sending raw binary data without encoding it with base64.
Signed-off-by: Alexander Kanavin
---
modules/utils/emailhandler.py | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/modules/utils/emailhandler.py b/modules/utils
301 - 400 of 704 matches
Mail list logo
