Thursday, 2018-05-03

*** adca <adca!~adca@> has quit IRC00:09
TartarusI ask since right now'ish we're about to mark that board Orphan in U-Boot00:15
TartarusAnd the main thing that's needed to have it not be orphan is someone with a board willing to boot U-Boot from time to time00:16
TartarusWhich is kinda something the Yocto person with the board needs to do anyhow :)00:16
*** martinkelly1 <martinkelly1!~martin@> has quit IRC00:22
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC00:37
*** kaspter <kaspter!~Instantbi@> has joined #yocto00:38
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto00:40
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC00:40
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC00:42
*** Bunio_FH <Bunio_FH!~bunio@> has quit IRC01:00
*** majuk_ <majuk_!> has joined #yocto01:02
*** majuk <majuk!> has quit IRC01:05
*** majuk_ <majuk_!> has quit IRC01:07
*** Guest45773 <Guest45773!95c73efe@gateway/web/freenode/ip.> has quit IRC01:10
*** armpit <armpit!~armpit@2601:202:4000:1184:2cf6:ec2c:db92:7477> has quit IRC01:14
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC01:20
*** vmeson <vmeson!> has joined #yocto01:25
*** armpit <armpit!~armpit@2601:202:4000:1184:29c7:2ead:a5b2:6da1> has joined #yocto01:27
*** nemunaire <nemunaire!~nemunaire@2a01:e35:8bb7:3c60::2> has quit IRC01:30
*** nemunaire <nemunaire!> has joined #yocto01:31
*** ntl <ntl!> has quit IRC01:33
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC02:00
*** tlwoerner <tlwoerner!~Trevor@> has joined #yocto02:02
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto02:02
*** kaspter <kaspter!~Instantbi@> has quit IRC02:43
*** majuk <majuk!> has joined #yocto03:04
*** kaspter <kaspter!~Instantbi@> has joined #yocto03:06
*** majuk <majuk!> has quit IRC03:08
*** ctlnwr <ctlnwr!~catalin@> has quit IRC03:38
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto03:50
-YoctoAutoBuilder- build #968 of build-appliance is complete: Success [build successful] Build details are at
*** ctlnwr <ctlnwr!~catalin@> has joined #yocto04:06
-YoctoAutoBuilder- build #978 of nightly-no-x11 is complete: Failure [failed BuildImages] Build details are at
*** stephano <stephano!~stephano@> has quit IRC04:27
*** Bunio_FH <Bunio_FH!~bunio@> has joined #yocto04:29
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC04:30
*** gabrbedd <gabrbedd!> has quit IRC04:39
*** Zajc <Zajc!> has quit IRC04:40
*** gabrbedd <gabrbedd!> has joined #yocto04:40
*** pk <pk!c6af4424@gateway/web/freenode/ip.> has joined #yocto04:40
*** Zajc <Zajc!> has joined #yocto04:40
*** yourfate <yourfate!~yourfate@unaffiliated/yourfate> has quit IRC04:40
pkhow can i modify recipe and upgrade "PR" for 'm4'04:41
*** gtristan <gtristan!~tristanva@> has joined #yocto04:42
*** yourfate <yourfate!~yourfate@unaffiliated/yourfate> has joined #yocto04:43
*** oob <oob!> has joined #yocto04:45
*** paulg_ <paulg_!~paulg@> has quit IRC04:49
*** OnkelUlla <OnkelUlla!> has quit IRC04:49
*** OnkelUlla <OnkelUlla!> has joined #yocto04:52
*** paulg_ <paulg_!~paulg@> has joined #yocto05:06
*** oob <oob!> has quit IRC05:10
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.> has quit IRC05:20
*** agust <agust!> has joined #yocto05:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:57
yoctiNew news from stackoverflow: do_rootfs: Can't install packagegroup-core-x11-utils-1.0-r40@all: no package provides xserver-nodm-init <>05:57
*** frieder <frieder!> has joined #yocto06:05
*** dv_ <dv_!> has quit IRC06:11
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC06:11
*** dlan <dlan!~dennis@> has joined #yocto06:13
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto06:13
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC06:13
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-frqmitfpmmiywdcf> has quit IRC06:19
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-zxbfctdyeuvpwhge> has joined #yocto06:19
*** mdnneo <mdnneo!~umaucher@> has joined #yocto06:22
*** dv_ <dv_!> has joined #yocto06:26
*** Kakounet <Kakounet!> has joined #yocto06:28
*** hamis <hamis!~irfan@> has joined #yocto06:36
*** hamis <hamis!~irfan@> has quit IRC06:41
*** hamis <hamis!~irfan@> has joined #yocto06:43
*** mckoan|away is now known as mckoan06:55
*** fl0v0 <fl0v0!> has joined #yocto06:56
*** t0mmy <t0mmy!~tprrt@> has joined #yocto07:03
*** mckoan <mckoan!> has quit IRC07:04
*** mckoan <mckoan!~marco@unaffiliated/mckoan> has joined #yocto07:04
*** TobSnyder <TobSnyder!> has joined #yocto07:07
*** rajm <rajm!~robertmar@> has joined #yocto07:12
*** vdehors <vdehors!~vdehors@> has joined #yocto07:15
*** fancer <fancer!sid180736@gateway/web/> has joined #yocto07:18
pkanyone know how to upgrade PR service of m4 recipe07:22
*** clement_ <clement_!> has joined #yocto07:34
*** acrap <acrap!> has joined #yocto07:36
acrapHi, folks!07:36
vladzouth<vladzouth> Hi i am facing some issue about installing linuxrc script on my rootfs, the error is :  miscellaneous-0.1-r0 do_package: QA Issue: miscellaneous: Files/directories were installed but not shipped in any package: /linuxrc.  Here is my recipe file Anyone know how to work around this issue?07:36
acrapI can get list of recipes with "bitbake -s", but how can I get it with license information? '-s' gives me only name of recipe, version and revision07:37
*** varjag <varjag!> has joined #yocto07:39
*** mm_ <mm_!5aa14b7c@gateway/web/freenode/ip.> has joined #yocto07:46
nayfevladzouth: what is "MY_FILES"? you cannot add something that is not in SRC_URI07:49
nayfeacrap: oe-pkgdata-util package-info -e LICENSE <package>07:50
nayfeacrap: or bitbake -e <recipe> | grep ^LICENSE07:51
*** vishnu_nk <vishnu_nk!~vishnunk@2001:420:5244:1300:b9c2:a00d:76ad:90d2> has joined #yocto07:53
vladzouthnayfe: "My_FILE" is the directory where the linuxrc script is.07:54
nayfevladzouth: you can look at to replace MY_FILES, and after that, you'll need in do_install() to replace install ... ${MY_FILES} by "install -m 0755 ${S}/linuxrc ${D}/linuxrc"07:55
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto07:55
*** morphis <morphis!~morphis@> has joined #yocto07:55
nayfein fact you don't need MY_FILES variable as it is in layer07:56
nayfejust replace it by ${S}07:56
nayfeit will search the correct path automatically07:57
vladzouthnayfe: OK, thanks!07:57
*** lfa <lfa!~lfa@> has quit IRC07:57
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto07:59
nayfe<vladzouth> finally in FILES_${PN}, you have to remove ${D}07:59
*** tz <tz!> has quit IRC08:01
nayfevladzouth: but, if you already have a linuxrc file provided by busybox for instance, you cannot create a "patch" recipe to replace it, you have to bbappend that recipe or patch linuxrc at the very end with
*** gtristan <gtristan!~tristanva@> has quit IRC08:03
*** tz <tz!> has joined #yocto08:05
vladzouthnayfe: In fact, i don't have a linuxrc provided by busybox in my images. Indeed, is there a way to tell busybox to include the linuxrc script file?08:05
acrapnayfe: thanks08:08
*** vishnu_nk <vishnu_nk!~vishnunk@2001:420:5244:1300:b9c2:a00d:76ad:90d2> has left #yocto08:09
*** clement_ <clement_!> has quit IRC08:10
nayfevladzouth: ok so your recipe will be ok after corrections08:13
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC08:21
*** rburton <rburton!> has joined #yocto08:22
vladzouthnayfe: i still have the same issue after adding INHERIT="externalsrc" on my local.conf, defining EXTERNALSRC on my recipe file and changing the do_install function with what you told me08:23
*** peacemem_ <peacemem_!~textual@> has joined #yocto08:27
nayfe<vladzouth: in fact you dont need externalsrc stuff, i was mistaken, all you need to do from original recipe is remove MY_FILES definition, in do_install(), replace MY_FILES by ${S} and in FILES_${PN} line remove ${D}08:28
*** peacemem_ <peacemem_!~textual@> has quit IRC08:29
vladzouthnayfe: it works, thank you!08:36
nayfevladzouth: np08:38
nayfeacrap: np08:38
*** adca <adca!~adca@> has joined #yocto08:53
*** majuk <majuk!> has joined #yocto09:02
*** majuk <majuk!> has quit IRC09:07
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto09:15
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC09:15
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:16
prabhakarladHi all, I am using the default network manager provided by yocto I want create a hotspot (AP) for my wifi interface, are ther any recipes to do that or any pointer for getting it working ?09:21
*** falk0n <falk0n!> has quit IRC09:22
*** ant_work <ant_work!> has joined #yocto09:22
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto09:23
*** falk0n <falk0n!> has joined #yocto09:24
*** lfa <lfa!~lfa@> has joined #yocto09:29
prabhakarladLetoThe2nd: thank you for the pointer :)09:36
*** fitzsim <fitzsim!> has quit IRC09:37
*** diembed <diembed!> has joined #yocto09:37
*** d3r3k <d3r3k!uid190567@gateway/web/> has quit IRC09:40
*** jmk <jmk!~julien@> has joined #yocto09:43
*** Kakounet <Kakounet!> has quit IRC09:50
*** rburton <rburton!> has quit IRC10:09
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto10:12
*** anujm <anujm!anujm@nat/intel/x-pkiinskpapwruvit> has joined #yocto10:23
*** morphis <morphis!~morphis@> has quit IRC10:25
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC10:26
*** lfa <lfa!~lfa@> has quit IRC10:44
-YoctoAutoBuilder- build #979 of nightly-no-x11 is complete: Success [build successful] Build details are at
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto11:18
*** armpit <armpit!~armpit@2601:202:4000:1184:29c7:2ead:a5b2:6da1> has quit IRC11:21
*** morphis <morphis!~morphis@> has joined #yocto11:25
*** morphis <morphis!~morphis@> has quit IRC11:33
*** acrap <acrap!> has quit IRC11:36
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC11:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:48
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:49
*** fitzsim <fitzsim!> has joined #yocto11:53
*** anujm <anujm!anujm@nat/intel/x-pkiinskpapwruvit> has quit IRC11:54
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto11:56
yoctiNew news from stackoverflow: Yocto - Bitbake - Example recipe to add a line in /etc/inittab file <>11:58
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:01
*** peacememories <peacememories!> has joined #yocto12:02
*** clement_ <clement_!> has joined #yocto12:02
pkwhile running build-appliance-image it resulted in - ERROR: libx11-native-1_1.6.5-r0 do_configure: autoreconf execution failed.12:07
*** diembed <diembed!> has quit IRC12:13
*** aratiu <aratiu!~adi@> has quit IRC12:19
*** aratiu <aratiu!~adi@> has joined #yocto12:19
-YoctoAutoBuilder- build #1005 of nightly-musl is complete: Success [build successful] Build details are at
*** gtristan <gtristan!~tristanva@> has joined #yocto12:24
*** Gintaro <Gintaro!~gintaro@2a00:8080:10:148:9017:2cff:fe26:adf0> has quit IRC12:25
*** Gintaro <Gintaro!~gintaro@2a00:8080:10:148:9017:2cff:fe26:adf0> has joined #yocto12:29
*** hackeron <hackeron!~hackeron@gentoo/user/hackeron> has joined #yocto12:39
hackeronHi, apologies for the ignorant question, I'm trying to choose a platform for an IoT Hub: I'm looking at Ubuntu Core and Yocto (and ResinOS also looks great). What would you say are the advantages/differences of Yocto over Ubuntu Core?12:41
LetoThe2ndits basically source-based, development host build (yocto) versus binary-based, in-target (ubuntu)12:42
LetoThe2ndnot absolutely, there are of course intersections. but basically its that.12:42
paulbarkerConfigurability and a good license compliance workflow are the advantages of Yocto for me12:44
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.> has joined #yocto12:44
hackeronah, ok, so Yocto is more low level, allowing you to build exactly what you want and ubuntu-core is more of a higher level package, trying to tie you into their cloud services and container type?12:44
Ramose its "{D}/usr/include/optee/export-user_ta/" not getting created on my rootfs12:45
paulbarkerResinOS would be good if you want to use Docker containers, but again, those docker containers won't be as configurable and you won't have the same tools you get with Yocto12:45
Ramosewhen I run this recipe12:45
paulbarkerhackeron: yep, I'd say that's fair12:45
*** eduardas_m <eduardas_m!~eduardas@> has joined #yocto12:46
hackeronpaulbarker: I see, thank you :) - from what I understand ResinOS is basically Yocto with a few customisation, so it should be possible to keep/remove anything that's useful for the specific requirement?12:46
paulbarkerNot sure, you'd need to talk to them about it12:47
Son_Gokuhackeron, Yocto is probably a better platform for this stuff12:48
Son_Gokubetween the two choices, Yocto is easier to customize, and it isn't that difficult to get started12:48
Son_Gokuit's supported by a number of companies, offering Yocto-based distributions that help you get off the ground quickly12:49
Son_Gokuwhereas Ubuntu Core significantly lacks in diversity12:49
LetoThe2ndSon_Goku: despite being a yocto supporter, i actually have to disagree12:49
LetoThe2ndthe only requirement we saw so far is "iot gateway", i firmly believe that theres absolutely no way for anybody to make a proper recommendation on that buzzword alone.12:50
LetoThe2ndah no, "iot hub"12:50
LetoThe2ndi'm sorry.12:50
*** marka <marka!~masselst@> has joined #yocto12:51
Son_GokuLetoThe2nd, judging by what they're comparing, they're looking for a way to build a minimal platform that's relatively easy to maintain going forward12:51
LetoThe2ndSon_Goku: assumptions, assumptions, assumptions.12:51
Son_Gokuhackeron, there's also Wind River Linux:
Son_Gokufully audited, supportable, and integrated platform12:52
Son_Gokuand most of the heavy lifting is done for you12:53
LetoThe2ndthe only really good advice one can give is to really (and i mean, really!) evaluate the specific use case and extract the requirements, then see what fits best. it might be any of the choices that have been named, or something different still12:53
LetoThe2nd(and no, "we want to start out with a minimal thing" does *not* count as a proper requirement)12:54
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC12:54
otavio[m]Tartarus: I think Stephano has it.12:56
hackeronSon_Goku: that's exactly what we're looking for - there are thousands of Gigabyte Brix and Raspberry Pi units at various locations, some on farms using solar panel. Currently we use Ubuntu Sever but a few times per month, the root filesystem inevitably gets corrupt and we need to send a replacement hard drive or SD card. So yes, looking for something that will address this but still won't require manual12:57
hackeronfirmware updates when we update the app (currently we just rsync the rails source, run bundle install and do a zero downtime restart)12:57
hackeronSon_Goku: hmm, is Wind River one of those Yocto based projects?12:58
LetoThe2ndhackeron: then you actually want a proper update mechanism first, totally independent from the underlying distribution12:58
LetoThe2ndhackeron: look at swupdate,, mender.io12:58
Son_Gokuhackeron, RPM-OSTree is a supported update option as well12:58
Son_GokuWRLinux offers it as an option, so you can use traditional infra to build software packages and compose it into immutable, atomic updates12:59
LetoThe2ndits true that anything openembedded based leans itself more easy to those mechanisms, but the real problem certainly is device management and updates.,12:59
nayfeotavio[m]: hey, you'r there?13:00
LetoThe2ndwhich again also suggests to look at, indeed.13:00
Ramosecan anyone point me out why "install -d ${D}/usr/include/optee/export-user_ta/"  do not create optee/export-user_ta/ in rootfs ?13:00
otavio[m]nayfe: yes13:01
otavio[m]LetoThe2nd: we also offer updatehub.io13:01
LetoThe2ndRamose: assuming that this is inside the do_install stage, you've probably not added it to FILES13:02
Ramoseyes its in do_install13:02
nayfeDid you see my message on mfgtools recipe?13:02
LetoThe2ndotavio[m]: there are certainly a variety of more options, absolutely agreed.13:02
otavio[m]nayfe: I did not13:02
otavio[m]nayfe: what is it?13:02
hackeronLetoThe2nd: that's one thing where ubuntu-core looks quite nice, they have unattended automated fill OS update13:02
nayfei just made a recipe for Freescale Mfgtools Linux (master) branch, it runs well on ARM . Recipe's quite dirty but do you think it makes sense to make a PR on meta-freescale?13:03
LetoThe2ndhackeron: don't get me wrong, i'm not trying to get you away from anything. its just that my impression is that your *actual* requirements are something that is not really an ubuntu vs. OE vs. anything question13:03
hackeronLetoThe2nd: in terms of device management, all the units are on an OpenVPN and provisioned by Ansible, there's an in house web interface that shows all the health stats and other metrics13:04
RamoseLetoThe2nd: What exactly you mean by ,  you've probably not added it to FILES ?13:04
otavio[m]nayfe: Sure. Please prepare a PR so we review it13:04
LetoThe2ndRamose: just what the sentence says. you have probably not added it to the FILES variable of the package, hence it is not packaged and installed to the rootfs, but only to the staging area.13:05
LetoThe2ndRamose: look up FILES in the yocto ref-manual :)13:05
otavio[m]hackeron: Usually I prefer to have ready to use images built from Yocto so no changes are need after installation;13:06
hackeronLetoThe2nd: sure, I'm just trying to understand what are the different components. So with resin-os you get the device management, which I don't necessarily need, with Yocto I guess I can plug my own in. So if I need to upgade the operating system, say to a new version of the kernel, I guess it's up to me to build that with Yocto?13:06
nayfeotavio[m] ok i'll do it when i have time :p13:07
RamoseLetoThe2nd:  this task runs well and packed images in rootfs of same recipe13:07
otavio[m]hackeron: that allows for reproducibility in long term13:07
otavio[m]and I see this as a critical thing13:07
hackeronaratiu: so once built, you never really update the kernel or anything like that?13:07
LetoThe2ndhackeron: well, the real power of OE is to create complete images, so no software deployment through pacakges or stuff is required on top13:07
RamoseLetoThe2nd:    install -m 644 ${B}/out/arm-plat-${OPTEEOUTPUTMACHINE}/core/*.bin ${D}${nonarch_base_libdir}/firmware/, It runs well13:08
otavio[m]nayfe: thanks I look forward to it. mfgtools is a nightmare :-)13:08
RamoseI guess you are talking about FILES_${PN} ?13:09
hackeronLetoThe2nd: in my case I want to push software updates multiple times per week, possible per day - but I guess there can be containers on top of the OS. In terms of US that generally is only updated once every 1-2 years, I guess this is the bit that would be difficult?13:09
hackeronin terms of the OS*13:10
*** JaMa <JaMa!~martin@> has quit IRC13:11
nayfeotavio: indeed :) i just saw yesterday that a new "uuu" is coming, hope it will be better ... I prefer imx_usb_loader, but when legacy stuff comes into game, it is hard to break it ... and it's quite funny to flash a board from another one :)13:11
LetoThe2ndhackeron: i'd say it depends a bit on the architecture. given a writeable rootfs, there's certainly nothign keeping you from deploying smaller updates as a package stream13:11
LetoThe2ndwhich on the other hand breaks more easily13:12
otavio[m]nayfe: for sure.13:12
nayfeyou prefer PR or mailing-list?13:12
hackeronLetoThe2nd: from what I understand there are 2 read-only root filesystems, so you can always revert if an update fails?13:13
otavio[m]nayfe: I think we can start on  a PR; so we can go over the review process.13:14
hackeronLetoThe2nd: so in terms of the software packages, that will just be say a docker container, which also handles revert, etc -- I'm more curious how the kernel updates happen and how to prevent bricking the units, hmmm13:14
otavio[m]nayfe: depending on how big it is, we can send it for ML13:14
LetoThe2ndhackeron: thats a common method, yes. but its actually part of the update strategy, not of yocto/OE. those do just buld those rootfs13:14
otavio[m]nayfe: otherwise I can pull it and send.13:14
nayfek PR will do13:14
RamoseLetoThe2nd: Cool, it gets created when I replace FILES_${PN}-dev = "/usr/include/optee" with FILES_${PN} = "/usr/include/optee"13:15
otavio[m]nayfe: remember, github is a mirror for meta-freescale13:15
LetoThe2ndhackeron: try to not think of the kernel as a singular thing to update. think of it (and anything else) as part of a monolithic OS image that is either updated in full, or not at all.13:15
otavio[m]hackeron: the A/B system is indeed the most secure way of update.13:15
otavio[m]hackeron: it allows you to revert manually or automatically13:16
otavio[m]hackeron: as LetoThe2nd said, usually we deal with the system as a single unit. So the kernel is part of it13:16
otavio[m]hackeron: the only exception is the bootloader. In updatehub case we detect the running version and update it only when it changes as it is the tricker part of it13:17
hackeronotavio[m]: LetoThe2nd: sure, that makes a lot of sense - but with Yocto, I'm guessing there isn't a kind of standard version that I can just go from Yocto 1.0 to Yocto 1.1 which will upgrade this one single unit, including kernel/code libs, etc?13:17
nayfeotavio[m]: sorry, which means? PR should be done on other git repo than github?13:17
LetoThe2ndhackeron: you're still thinking of yocto as a distribution, with updates. this is jsut not the reight thing. it creates a distribution image, with whatever content you like.13:19
otavio[m]hackeron: you can upgrate from 1.0 to 10.0 if need. But you are responsible to handle migrations from the apps yourself.13:19
LetoThe2ndhackeron: you have to get your head around the point that yocto is *NOT* running on the target. it is a tool that *CREATES* the image that runs on your target.13:19
otavio[m]hackeron: as LetoThe2nd said, you deal it as an atomic version.13:20
LetoThe2ndand of course you can feed new versions into that tool, then roll out a newer image.13:20
otavio[m]hackeron: not upgrade in package level13:20
otavio[m]hackeron: but a full move from A to B13:20
* otavio[m] sent a long message: otavio[m]_2018-05-03_13:21:30.txt <>13:21
*** stephano <stephano!~stephano@> has joined #yocto13:21
hackeronLetoThe2nd: otavio[m]: No, no, I get that, but say I rolled my own image, it has kernel 4.16, it has docker to run my containers, etc -- I then want to update my kernel and docker version and roll a new image. How do I do that? - do I need to go in and manually download the linux kernel sources and any other libraries that I might need to modify and then build a new image? - or is there a kind of base I13:24
hackeroncan start with that will give me the latest kernel, with sensible defaults and modules, etc?13:24
LetoThe2ndhackeron: the upstream state of poky respectively meta-openembedded is basically that base with sensible defaults.13:25
otavio[m]Yocto Project usually comes with fairly recent versions. So you'll need to upgrade your base version and use it as base.13:26
otavio[m]your base Yocto Project version13:26
otavio[m]HOWEVER you are free to do changes, if need.13:27
hackeronLetoThe2nd: ah, ok, so I just get the latest poky/meta-opembedded and hopefully my modifications on top of that will still build a working image (or not, lol)13:27
LetoThe2ndhackeron: thats the plan, in a nutshell. correct.13:27
LetoThe2ndyour modifications/addons are located in a so-called layer, that gets added on top13:27
otavio[m]That is exactly why Yocto Project serves better embedded devices than Ubuntu, Debian and others. It is very easy to customize whatever is need.13:28
otavio[m]hackeron: take a look on the first book I gave the link; it explains this very well13:28
hackeronok, thank you, I'l do more research and experiment, it's making a lot more sense now :)13:29
LetoThe2ndhackeron: grab a sandwich and some coolaid, then watch and properly digest
*** armpit <armpit!> has joined #yocto13:29
LetoThe2ndhackeron: thats the basically bare bones version of the yocto dev day beginner track. and depending on what your timeframe and location are, you might want to join one of the sessions in real life.13:29
hackeronaratiu: sorry I missed the book link, is it this? <
hackeronLetoThe2nd: that's fantastic, thank you, grabbing a coffee and some pork scratchings :P13:31
*** peacememories <peacememories!> has quit IRC13:31
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto13:31
LetoThe2ndhackeron: shameless plug: if you're based in germany near cologne, i'm doing a training early in june
hackeronLetoThe2nd: Based in London, UK :( - but I'll watch out fo anything yocto related in and around London :)13:32
*** tf <tf!> has joined #yocto13:32
LetoThe2ndhackeron: ELC-E is coming to edinburgh in late october, there probably will be dev day again13:33
*** tf <tf!> has quit IRC13:34
*** tf <tf!> has joined #yocto13:34
armpitLetoThe2nd, we are trying13:35
hackeronLetoThe2nd: what's ELC-E?13:35
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-zxbfctdyeuvpwhge> has quit IRC13:36
LetoThe2ndELCE: your annual chance to personally blame all OE devs!13:36
*** jmk <jmk!~julien@> has quit IRC13:37
hackeronlol, sorry, what's OE devs?13:37
hackeronoh, OpenEmbedded?13:37
Crofton|workThe guys that do all the work on the YP :)13:37
hackerongot it :) - thank you13:37
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-sfkddcxbyktyehpr> has joined #yocto13:37
mckoanOpenEmbedded, that weird thing which is the foundation of Yocto Project :-D13:38
Crofton|workI need to bitch about Active COmmunity members getting labled as hobbyists13:38
hackeronSo wrlinux-x is built on top of Yocto which is built in top of OpenEmbedded?13:39
LetoThe2ndi usually go like this: i blame everybody for breaking everything, making everything overly complicated, and generally being stupid and ugly. then we all get shitfaced.13:39
LetoThe2nd(ELCE in a nutshell)13:39
Crofton|workAnd LetoThe2nd brings me beer. At least if he doesn't have to fly13:41
otavio[m]hackeron: yes, thatis the book link13:41
Crofton|workhackeron, basically :)13:41
Crofton|workand we get shitfaced, we argue about the meaning of words13:42
LetoThe2ndok, that actually was a bit exaggerated, we're all pretty nice guys.13:42
Crofton|workexcept for me13:42
LetoThe2ndbut it sounds way more cool13:42
LetoThe2ndand i can say with absolute certainty that i have never been sober to the yocto BoF!13:43
Crofton|workalso there will very likely be an OpenEmbedded developer meeting Sunday before13:43
Son_Gokuhackeron, yes, WRLinux -> Yocto -> OE13:43
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC13:43
* armpit OE -> MSDos ?13:44
mckoanWRLinux is Yocto for rich people13:44
*** peacememories <peacememories!> has joined #yocto13:44
eduardas_mhello, has anyone successfully generated an SDK with rocko and meta-qt5 (Qt 5.10)?13:44
armpitmckoan, the 1%13:44
mckoaneduardas_m: yes, of course13:45
eduardas_msomething broke when moving from Qt 5.9.4 to Qt 5.1013:45
eduardas_mmckoan: I can no longer export the environment correctly13:45
mckoaneduardas_m: how do you generate the SDK?13:45
LetoThe2ndarmpit: \o/13:46
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto13:46
eduardas_mmckoan: -c populate_sdk13:46
mckoaneduardas_m: nah13:46
*** stephano <stephano!~stephano@> has quit IRC13:46
LetoThe2ndi think we need badges here. who's working for which company. :)13:46
mckoaneduardas_m: meta-toolchain-qt513:46
*** stephano <stephano!~stephano@> has joined #yocto13:46
RParmpit: I merged rocko, thanks!13:47
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC13:47
LetoThe2ndRP: i merged rock into my hifi, does that count too? </SCNR>13:47
armpitRP, I saw. thank you13:47
eduardas_mmckoan: I was told once by wise Yocto people that Yocto project does not care about that since it's a meta-qt5-specific method13:47
*** dlan <dlan!~dennis@> has joined #yocto13:48
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto13:48
* mckoan bows to wide people13:48
LetoThe2ndrly? oO13:48
eduardas_mmckoan: it also has the downside of not pulling in everything in the target sysroot13:48
*** jmk <jmk!~julien@> has joined #yocto13:49
eduardas_mlike v4l2 libraries, etc.13:49
armpitRP, pyro is segfaulting in musl ruby, but rocko is not so I suspect fix in later version of ruby13:49
mckoaneduardas_m: you could customize the meta-toolchain-qt5 though13:49
RParmpit: quite likely, ruby seems to be good at faulting :(13:49
LetoThe2ndmckoan: i hereby declare that "typo of the day."13:49
mckoanLetoThe2nd: people on diet may become upset13:50
Crofton|workif something is worth doing, it is worth doing well. Even segfaulting13:50
otavio[m]eduardas_m: you can inherit populate_sdk_qt5 in your custom image and use it instead13:50
LetoThe2ndmckoan: thats the point, right13:50
eduardas_motavio[m]: that is exactly what I am doing13:50
otavio[m]and what is failing?13:51
* RP decides he probably doesn't want to think about what meta-qt5 is doing :/13:51
eduardas_motavio[m]: the problem is when executing qt5.sh13:51
otavio[m]nayfe: I reviewed it. Some comments.13:52
eduardas_motavio[m]: something like qmake -query QT_INSTALL_LIBS gets me an "Empty filename passed to function"13:52
otavio[m]eduardas_m: check if it is included inside the environment.d13:52
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC13:52
eduardas_motavio[m]: the script itself is definitely there13:52
otavio[m]eduardas_m: that is inside master / sumo?13:52
otavio[m]eduardas_m: or rocko?13:53
mckoanRP: why?13:53
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto13:53
otavio[m]mckoan: hehe Qt does some black magic to make it all work ;-)13:53
otavio[m]RP: so do I; but I can't heh13:54
eduardas_motavio[m]: I am using the meta-qt5 branch for Qt 5.10 currently mainatined by Qt comapny, but same thing used to happen with community meta-qt5 on master (when it was on Qt5.10)13:54
LetoThe2ndRP: have you looked at behans intro to bitbake/yp from ELC?13:54
otavio[m]eduardas_m: well if you are using Qt company's layer so ask them to support it.13:54
otavio[m]eduardas_m: I don't use it myself (but for customers)13:55
RPLetoThe2nd: no...13:55
eduardas_motavio[m]: same thing happens with "mainline" meta-qt5 on master last time I used it13:55
otavio[m]eduardas_m: if it fails in meta-qt5's layer, in our branches, I can take a look13:55
otavio[m]eduardas_m: today?13:56
LetoThe2ndRP: citation: ".. its so complex that I doubt anybody knows all about it. Well, maybe except RP."13:56
otavio[m]eduardas_m: please check, if it fails I can look at it.13:56
RPLetoThe2nd: I'm not sure any of us know all of the system ;-)13:57
*** TobSnyder <TobSnyder!> has quit IRC13:57
eduardas_motavio[m]: ok, will try with master...will take long to build though... what is the best way to get in touch after checking?13:57
LetoThe2ndRP: hehe, it just kinda stuck :)13:57
otavio[m]eduardas_m: ping me here or pvt message13:58
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC13:58
eduardas_motavio[m]: thank you, will try tomorrow morning with master since my work hours are pretty much over today13:59
*** dlan <dlan!~dennis@> has joined #yocto13:59
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto13:59
nayfeotavio[m]: thanks i'll correct PR tomorrow13:59
otavio[m]eduardas_m: that's fine.14:00
otavio[m]nayfe: sure.14:00
otavio[m]nayfe: I think it is simple to fix the build system to properly build the cli and use a single recipe for it14:00
*** eduardas_m <eduardas_m!~eduardas@> has quit IRC14:00
otavio[m]nayfe: did you prepare an image for its use?14:01
nayfeindeed, but I didn't want to go deeper in that CMakeList.txt :D14:01
*** peacememories <peacememories!> has quit IRC14:01
otavio[m]nayfe: it'll buy some time later, for sure. Also I can push NXP to apply it for next release14:01
nayfebuild is quite awfull, with plain Makefile that calls cmake, do some copy, relaunch cmake etc :)14:02
otavio[m]So think if putting it into the cmake only does not make it simpler. If it does, fork the repository and prepare the changes14:03
otavio[m]we can use your fork in meanwhile or fork it inside our orga if you prefer14:03
*** ntl <ntl!> has joined #yocto14:03
nayfenot sure i'll have time for this rework this month is plenty of holidays :)14:08
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:11
otavio[m]nayfe: I hope you do :-D14:11
*** behanw <behanw!uid110099@gateway/web/> has joined #yocto14:29
nayfethere is also the "native" part that could be added too to run it on host ...14:29
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-sfkddcxbyktyehpr> has quit IRC14:32
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-lwhcchhdgwmvgccs> has joined #yocto14:32
*** varjag <varjag!> has quit IRC15:03
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has joined #yocto15:07
*** martinkelly1 <martinkelly1!> has joined #yocto15:16
*** AbleBacon_ <AbleBacon_!~AbleBacon@unaffiliated/ablebacon> has joined #yocto15:20
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC15:23
*** AbleBacon_ is now known as AbleBacon15:23
TartarusHmmm, can INITRAMFS_FSTYPES even theoretically be a list?  I don't see anyone doing more than one off hand15:25
*** martinkelly1 <martinkelly1!> has quit IRC15:25
Tartarusand documentation uses singular words15:25
ant_workINITRAMFS_FSTYPES ?= "cpio.gz cpio.xz" works beautifully15:26
ant_workhi khem15:27
khemhey ant_work15:27
ant_worksorry for bothering you by mail15:28
ant_workbut one of the two klibc devs is 'krank', the other disappeared/ you get the idea15:28
Tartarusant_work: Define works please15:29
Tartarusbitbake certainly won't blow up15:29
TartarusBut does anything that comes back and plays with INITRAMFS_FSTYPES work as expected?15:29
ant_workTatarus: in use since 5-6 years15:29
Tartarusant_work: where?15:29
TartarusI do believe they will be produced, yes15:29
ant_worksince kernel could decompress xz intramfs's15:29
TartarusBut will wic work or just use the first one found?15:30
Tartarusor blow up15:30
ant_workyou get the two, the kernel recipe defines which one to use15:30
Tartarusant_work: Ah, via which variable?15:30
TartarusOr just a loop and guess?15:31
ant_worksee meta-handheld layer15:31
Tartarusant_work: OK, any particular machine too?15:32
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC15:34
ant_workwell, note you have to define INITRAMFS_IMAG15:34
ant_workin our case we do force  INITRAMFS_TASK = "${INITRAMFS_IMAGE}:do_image_complete"15:35
TartarusSo, I'm kicking to be more robust15:36
TartarusAnd use update-alternatives too in the non-bundled case15:36
TartarusAnd with your hints, I think the answer is that no, I can't assume INITRAMFS_FSTYPES is singular15:36
TartarusAnd i need to drop that break out, and continue not using the update-alternatives class directly15:36
ant_workI lost track of the last changes butnowadays it should be possible to build two kernel flavours whithout issues15:37
TartarusOr study busybox a bit more15:37
TartarusFor dynamic playing with the alternatives list15:37
*** rajm <rajm!~robertmar@> has quit IRC15:47
*** kaspter <kaspter!~Instantbi@> has quit IRC15:47
*** scottrif <scottrif!~scottrif@> has joined #yocto15:55
*** stephano <stephano!~stephano@> has quit IRC15:58
*** hamis <hamis!~irfan@> has quit IRC15:58
*** ant_work <ant_work!> has quit IRC16:04
*** fl0v0 <fl0v0!> has quit IRC16:16
*** lusus <lusus!~lusus@> has quit IRC16:19
*** mckoan is now known as mckoan|away16:20
*** gnac <gnac!> has quit IRC16:26
*** lucaceresoli <lucaceresoli!> has quit IRC16:28
*** Zajc <Zajc!> has quit IRC16:29
*** Zajc <Zajc!> has joined #yocto16:29
*** Snert_ <Snert_!~snert_@> has quit IRC16:35
*** Snert_ <Snert_!~snert_@> has joined #yocto16:35
*** rburton <rburton!> has joined #yocto16:44
*** abelal <abelal!~quassel@> has quit IRC16:51
*** abelal <abelal!~quassel@> has joined #yocto16:52
*** vdehors_ <vdehors_!> has joined #yocto16:53
*** vdehors <vdehors!~vdehors@> has quit IRC16:56
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:f8d9:318d:e1a0:814d> has joined #yocto16:57
*** vladzouth <vladzouth!500c5411@gateway/web/freenode/ip.> has quit IRC17:02
*** mdnneo <mdnneo!~umaucher@> has quit IRC17:20
*** WillMiles <WillMiles!> has joined #yocto17:37
*** vdehors_ <vdehors_!> has quit IRC17:44
*** aarcane <aarcane!~Christ@> has joined #yocto17:49
*** sbach <sbach!~sbach@> has joined #yocto18:14
*** t0mmy <t0mmy!~tprrt@> has quit IRC18:22
*** rob_gries <rob_gries!~rob@> has quit IRC18:37
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:f8d9:318d:e1a0:814d> has quit IRC18:40
*** frieder <frieder!> has quit IRC18:42
*** gtristan <gtristan!~tristanva@> has quit IRC18:50
*** HavoK__ <HavoK__!> has joined #yocto19:19
HavoK__I added new kernel modules and this caused me to have a new kernel package. I used smart PM to update the packages and I can see the modules present under the folder for the new kernel.19:20
HavoK__My question is how can tell the machine to boot using the new kernel. when i put uname -r it seems to be using the old one still19:21
*** JaMa <JaMa!~martin@> has joined #yocto19:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:35
*** bavery_fn <bavery_fn!~bavery@> has joined #yocto19:36
*** HavoK__ <HavoK__!> has left #yocto19:41
kergoththat depends on what bootloader you're using19:49
kergothyou haven't told us anything about what you're doing, distro, machine, anything19:49
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:00
*** Bunio_FH <Bunio_FH!~bunio@> has quit IRC20:33
*** fischerm <fischerm!~mfischer@> has quit IRC20:53
*** CoRfr <CoRfr!> has quit IRC20:55
*** marka <marka!~masselst@> has quit IRC20:59
*** CoRfr <CoRfr!> has joined #yocto21:00
*** CoRfr <CoRfr!> has quit IRC21:07
*** CoRfr <CoRfr!> has joined #yocto21:08
*** fischerm <fischerm!~mfischer@> has joined #yocto21:29
*** WillMiles <WillMiles!> has quit IRC21:40
*** vmeson <vmeson!> has quit IRC21:55
-YoctoAutoBuilder- build #987 of nightly-qa-extras is complete: Failure [failed Running Sanity Tests_7] Build details are at
*** JaMa <JaMa!~martin@> has quit IRC22:01
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC22:03
*** vmeson <vmeson!> has joined #yocto22:20
*** d3r3k <d3r3k!uid190567@gateway/web/> has joined #yocto22:24
*** Bunio_FH <Bunio_FH!~bunio@> has joined #yocto22:28
*** nathani_ <nathani_!> has quit IRC22:36
*** nathani_ <nathani_!> has joined #yocto22:36
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto22:42
*** anujm <anujm!~anujm@> has joined #yocto22:47
fischermtrying to decide for the correct place for network configuration files for systemd. It seems like my BSP layer is the wrong place. Any way to make these kind of things specific to an image?23:00
*** sysdef <sysdef!~sysdef@debiancenter/founder.developer/pdpc.professional.sysdef> has quit IRC23:12
*** RP <RP!> has quit IRC23:16
*** Bunio_FH <Bunio_FH!~bunio@> has quit IRC23:40
*** rburton <rburton!> has quit IRC23:59

Generated by 2.11.0 by Marius Gedminas - find it at!