Thursday, 2015-06-25

*** sjolley <sjolley!~sjolley@> has joined #yocto00:06
*** rburton <rburton!> has quit IRC00:30
*** rburton <rburton!> has joined #yocto00:32
*** paulg_ <paulg_!> has quit IRC00:35
*** hellerbarde <hellerbarde!> has quit IRC00:44
*** paul_ <paul_!> has joined #yocto01:01
*** vmeson <vmeson!> has joined #yocto01:31
*** paul_ <paul_!> has quit IRC02:40
*** zeddii_home_ <zeddii_home_!> has joined #yocto03:11
*** zeddii_home <zeddii_home!> has quit IRC03:11
*** zeddii_home_ is now known as zeddii_home03:11
*** kscherer__ <kscherer__!~kscherer@> has quit IRC03:13
*** kscherer__ <kscherer__!~kscherer@> has joined #yocto03:14
*** jmleo <jmleo!> has joined #yocto03:24
*** _jmleo <_jmleo!> has quit IRC03:26
*** AndersD <AndersD!> has joined #yocto05:09
*** [Sno] <[Sno]!> has quit IRC05:11
*** roric_ <roric_!> has joined #yocto05:28
*** akhandav <akhandav!~arun@> has quit IRC05:29
*** dshwang <dshwang!dshwang@nat/intel/x-ggpnibnsfctcmbya> has quit IRC05:32
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has quit IRC05:40
*** dshwang <dshwang!~dshwang@> has joined #yocto05:40
*** marekb <marekb!> has joined #yocto05:44
*** roric_ <roric_!> has quit IRC05:45
*** stiandre <stiandre!> has joined #yocto06:05
*** pohly <pohly!> has joined #yocto06:05
*** stiandre <stiandre!> has quit IRC06:09
*** frsc <frsc!> has joined #yocto06:14
*** ntl <ntl!> has quit IRC06:15
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto06:17
*** wadim_ <wadim_!> has joined #yocto06:21
*** TobSnyder <TobSnyder!> has joined #yocto06:28
*** ntl <ntl!> has joined #yocto06:28
*** frsc <frsc!> has quit IRC06:34
*** frsc <frsc!> has joined #yocto06:39
*** Metanaou <Metanaou!c3dc2512@gateway/web/freenode/ip.> has joined #yocto06:42
MetanaouWhen building an image with IMAGE_TYPES = "iso", I've an error :06:43
MetanaouMissing or unbuildable dependency chain was: ['core-image-minimal', 'syslinux']06:43
MetanaouHow do I add syslinux ?06:43
*** fabo <fabo!~fabo@linaro/fabo> has quit IRC06:44
*** fabo <fabo!~fabo@linaro/fabo> has joined #yocto06:44
Metanaou(IMAGE_FSTYPES, not *TYPES)06:44
LetoThe2ndMetanaou: its not about building syslinux, its about finding out why its not found or cannot be built.06:47
LetoThe2ndMetanaou: and a quick check in the layer index suggests that you need oe-core06:49
*** roric_ <roric_!~roric@> has joined #yocto06:51
MetanaouLetoThe2nd: oe-core isn't in Poky ?06:51
*** frsc <frsc!> has quit IRC06:53
LetoThe2ndMetanaou: i can properly explain it, just got that bit from
MetanaouReading this :
MetanaouIt seems that oe-core is in Poky.06:54
MetanaouSo I could add it, but I'll have two times the same thing.06:55
LetoThe2ndMetanaou: yeah you're right syslinux is in recipes-devtools06:56
LetoThe2ndso next step: find out why it can't be built. are you targetting something other than x86, maybe?06:57
MetanaouIt's for ARM.06:57
LetoThe2ndno syslinux for you, then.06:57
LetoThe2ndso no iso06:57
MetanaouAww, shit.06:57
LetoThe2ndc'mon, how did you expect it to boot?06:57
MetanaouSo if I want to have a deployable image, how can I manage that ?06:57
MetanaouMaybe syslinux was used only to built it. :D06:58
LetoThe2nddepends on your way of deployment.06:58
MetanaouFor Freescale, I use .sdcard image, it's pretty cool.06:58
LetoThe2ndMetanaou: you are aware that the boot process in ARM land is heavily machine specific, in contrast to x86's bioses and such?06:58
Metanaoudd if=image.sdcard of=/dev/sdX, done.06:58
MetanaouLetoThe2nd: no, I wasn't.06:59
LetoThe2ndwell then you are now.06:59
MetanaouI'm pretty new in embedded.06:59
LetoThe2ndplus, the sdcard thing isn't freescale specific, it's specific to a line of boards that share a common hardware setup in terms of sd card interfacing and boot settings.07:00
_4urele_Metanaou, what board do you have? (beaglebone black, raspberry pi, sabre sd...)07:00
LetoThe2ndi can easily crank up a fsl board where that "sdcard" thing won't do anything at all.07:00
LetoThe2ndMetanaou: so your first step is: specify the board in use, and determine the way of deployment.07:01
Metanaou_4urele_: the fsl is an i.mx6q sabresd.07:01
MetanaouI have also an Olimex lime207:01
MetanaouLetoThe2nd: with the sabresd, I boot on u-boot and I download a minimal image on RAM (rootfs is .cpio.gz.u-boot). Then I download the real system and flash it on eMMC.07:02
MetanaouAnd I separatly flash a specific u-boot in the boot partition, in order to enable the boot on eMMC.07:03
_4urele_Metanaou, then you are pretty aware of the boot process!07:03
LetoThe2ndMetanaou: to me, that does not specify how you deploy, but rather a manual reflashing07:04
MetanaouWith the Olimex, it's way harder, 'cause I don't have a depployable image.07:04
MetanaouLetoThe2nd: so what do you mean by "how you deploy" ?07:04
LetoThe2ndwhat do you want to hand out? some blob that people have to reflash manually as you described? or some blob that automatically reflashes a board upon boot? if so, what medium are you using?07:05
LetoThe2ndthe sdcard image that you named for fsl is an example of the latter, with sd card being the medium07:06
MetanaouThe first boot is done using the sd card, in order to have u-boot.07:07
MetanaouBut after, I'd like to do it all by network.07:07
MetanaouSo the simplest is to have a deployable image (like the .sdcard, that I use without sd card) that I can flash on the eMMC.07:08
LetoThe2ndand having a short look at the olimex board, i'm pretty convinced one could also create a sdcard image comparable to the fsl one for it. its just hte the sdcard magic you know is provided by fsl, and specific to them. you might be able to beat it into shape, of course.07:09
MetanaouIt's seems interesting.07:09
LetoThe2ndMetanaou: ok, so you're actually looking for a way to deploy a *new* blob to devices that are already initially flashed and functional, right?07:09
MetanaouI'll have a look into it, thanks.07:09
MetanaouLetoThe2nd: almost.07:10
LetoThe2ndMetanaou: in that case, have a look at meta-swupdate by sbabic.07:10
MetanaouOn the first boot, I have a functionnal system booted on RAM?07:10
MetanaouBut then, yes, I want to deploy another blob on the device.07:10
LetoThe2ndso you need the deployment-receiver mechanism to be present in the blob AND then initial boot.07:11
LetoThe2ndwhich again is of course possible.07:11
*** else58 <else58!> has quit IRC07:11
LetoThe2ndswupdate could probably be used to archieve that, so my advice would be to have a proper look at it.07:13
*** sameo <sameo!~samuel@> has joined #yocto07:14
*** jku <jku!jku@nat/intel/x-pcuitkaysxoqlnkw> has joined #yocto07:14
MetanaouLetoThe2nd: can't I use a simple bash script ?07:15
MetanaouWhich download the sdcard image and u-boot binary and flashs them in the eMMC ?07:15
LetoThe2ndof course you can, but then your and my defintion of "simple" won't share too much intersection07:16
LetoThe2ndof course if leave out any kind of fault-tolerance, power interruption, broken rom and all those fun parts, then it becomes almost "simple"07:16
LetoThe2ndbeen there, done that. now we're using swupdate, as its just more bang for the buck - we don't have to replicate functionality that somebody else already has properly implemented and tested07:17
LetoThe2ndfor something in private tinkering, no problem with a small script. you can fix it whenever it fails.07:18
*** ericbutters <ericbutters!~eric@> has quit IRC07:19
LetoThe2ndif you want to ship a real product, i seriously advice you to evaluate existing, proven and well-tested mechanisms first.07:19
LetoThe2nd(with swupdate just being one of them, i'm not trying to sell you anything.)07:19
*** stiandre <stiandre!~stiandre@> has joined #yocto07:21
_4urele_LetoThe2nd, I didn't knew swupdate, I'm very interested about it! are you using it?07:21
MetanaouLetoThe2nd: the same, it seems really cool.07:21
MetanaouToo bad I haven't found it before. :(07:21
LetoThe2nd_4urele_: we're using it, yes.07:21
_4urele_is it possible to update the current used rootfs  with it?07:22
LetoThe2ndI can't share too many details as i'm really just a user, not the architect - but it works, and it certainly is vastly superior to our previous homebrew mechanism07:22
LetoThe2nd_4urele_: don't think so.07:22
LetoThe2ndyou always need some kind of twin or intermediate system.07:22
*** else58 <else58!> has joined #yocto07:23
_4urele_LetoThe2nd, that's make sense ;) just wanted to be sure, but it seems pretty awesome!07:23
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:24
LetoThe2ndi repeat, don't get me wrong: i do *not* advocate using that particular thing, i advocate properly evaluating exiting things before wasting time on a limited homebrew solution.07:24
MetanaouLetoThe2nd: it doesn't seem to be supporting yocto 1.7+07:33
*** Biliogadafr <Biliogadafr!> has joined #yocto07:34
LetoThe2ndMetanaou: ok, so?07:38
MetanaouSo there are some awful errors. :p07:38
*** miandonmenmian_ <miandonmenmian_!~miandonme@> has joined #yocto07:38
miandonmenmian_how can i check if my bbapped is read or loaded?07:39
*** jimBaxter <jimBaxter!> has joined #yocto07:43
LetoThe2ndMetanaou: can always be fixed :-)07:46
*** frsc <frsc!> has joined #yocto07:50
*** frsc <frsc!> has quit IRC07:51
*** frsc <frsc!> has joined #yocto07:52
*** [Sno] <[Sno]!> has joined #yocto07:56
*** CromFr <CromFr!~CromFr@> has joined #yocto08:21
*** nighty^ <nighty^!> has joined #yocto08:26
*** Metanaou <Metanaou!c3dc2512@gateway/web/freenode/ip.> has left #yocto08:32
redenginmiandonmenmian_, bitbake "myrecipe"08:37
miandonmenmian_from what I can tell, if it doesnt complain, then it is loaded. I suppose what I'm doing wrong has to be somewhere whiting the priority of my layer08:40
miandonmenmian_because in spite that my layer includes some extra packages, those packages are not loaded08:41
miandonmenmian_on the image08:41
*** hitlin37 <hitlin37!uid16371@gateway/web/> has joined #yocto08:41
redengindoes your image include the dependency on the recipe?08:41
redenginmiandonmenmian_, how are you testing for "loaded"?08:42
*** ant_work <ant_work!> has joined #yocto08:45
miandonmenmian_the recipe require dependencies, so i suppose it would complain is it isnt there. however one of the dep might not be included on the image conf08:47
miandonmenmian_im testing for loaded, because its not on the image when the image is run08:47
miandonmenmian_i'd rather find a faster approach to this kind of tests08:48
redenginmiandonmenmian_, have you done this before?08:51
miandonmenmian_was working before i updated my yocto environment08:51
miandonmenmian_but i did use the bbappend before for the included packages, instead i edited other layer directly08:51
redengindid you check that your layer is on the new environment?08:51
miandonmenmian_yes, layer is there08:52
miandonmenmian_just realized that not all packages are built08:52
miandonmenmian_i dont understand why some are built, but no error output08:52
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-ztwlymuylsjmefjt> has joined #yocto08:52
redenginmiandonmenmian_, is there a reason you customized another layer rather than creating your own?08:53
miandonmenmian_i created my own, but seems the append didnt work, so just added the steps of my layer to the other layer on top08:53
miandonmenmian_Now im trying to get my layer really working08:53
redenginthe bbappend will only get applied if the original recipe is used08:54
miandonmenmian_both my own and the original recipes are loaded08:54
miandonmenmian_bitbake has them when compiling image. bitbake-layers also includes them08:54
*** ddalex1 <ddalex1!> has quit IRC08:56
*** Ulfalize1 <Ulfalize1!> has quit IRC09:00
*** ddalex <ddalex!~ddalex@> has joined #yocto09:02
miandonmenmian_redengin: does the append have to name the main source on it? i see no reference to this, but i saw some appends have a similar line09:05
miandonmenmian_like this: require conf/distro/poky.conf09:05
*** ][Sno][ <][Sno][!> has joined #yocto09:11
*** [Sno] <[Sno]!> has quit IRC09:13
redenginconfs are different than recipes09:13
redenginmiandonmenmian_, is there any way to see what you're working on?09:15
miandonmenmian_redengin: i'll try to clean it up and post it later on. but i was trying to make some sense of it before doing that, i'll try to put it somewhere09:16
redenginI'd start by comparing your local.conf between environments09:24
redengindid you create a custom image, or are you using local.conf to define your image dependencies?09:25
*** arfoll <arfoll!arfoll@nat/intel/x-dysejognaoqkvczr> has quit IRC09:25
redenginand yes, if you have just "x.bbappend" in your layer, you'll still need the layer that provided the original ""09:26
redenginbut you should see errors if there are unmet dependencies09:27
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-ztwlymuylsjmefjt> has left #yocto09:34
*** wrock <wrock!4d5006dc@gateway/web/freenode/ip.> has joined #yocto09:41
*** wrock <wrock!4d5006dc@gateway/web/freenode/ip.> has joined #yocto09:42
wrockhello everyone, I'm trying to compile an arm distr on ubuntu 15.04, and the only thing i can't compile is mesa(warning treated as errors", someone has an idea at which point i need to fix that?09:43
*** zwerch <zwerch!> has joined #yocto09:43
rburtonwrock: helpful if you pastebin the actual errors09:45
*** leowt <leowt!> has joined #yocto09:48
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-zbydnwntehqerzmn> has joined #yocto09:52
wrockhere are the last couple of line rburton:
wrocki tried to delete all -werror flags in the package10:00
wrockbut that didnt work10:00
wrocksomehow the changes didn't apply10:00
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-zbydnwntehqerzmn> has left #yocto10:00
wrockalso, in run.do_compile i can't find an Werror flag10:06
*** zloy` <zloy`!~user@> has joined #yocto10:07
zloy`hey guys10:07
zloy`is there a documentation about creating my own rootfs and building busybox?10:07
redenginzloy`, wouldn't you just bitbake busybox?10:09
zloy`redengin: I have my own config file for busybox10:09
redenginzloy`, what do you mean by rootfs?  busybox won't boot10:10
zloy`redengin: furthmore, I'd like to create my own rootfs with init scripts10:10
zloy`redengin: by rootfs I mean the directories structures /bin, /sbin, /root, /dev, /sys, etc.10:11
zloy`redengin: and why busybox won't boot? Actually I built busybox and created rootfs manually and it boots perfectly10:11
redenginzloy`, did you make the init busybox?10:12
zloy`redengin: yes, I did10:12
*** rburton <rburton!> has quit IRC10:12
*** rburton <rburton!> has joined #yocto10:13
redenginzloy`, ah, then I understand10:13
zloy`redengin: so, what about the documentation? :)10:13
zloy`I just want to create my own meta for building busybox and rootfs10:13
redenginzloy`, I'm not sure I understand what documentation there would be10:13
redenginzloy`, as in you just want an image that defines busybox as the init?10:14
zloy`redengin: and creates my own rootfs folders structure10:16
zloy`and scripts of course10:16
redenginzloy`, then you'd make a (or many recipes) to add those folders/scripts10:17
zloy`redengin: as far as I understood this ( document is that what I want, right?10:18
redenginsomewhat, but really you just need a recipe for your customization, that recipe needs to be in a layer10:18
*** husanu4 <husanu4!~husanu@> has joined #yocto10:19
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto10:19
redenginand then that layer needs to be added to your build environment10:19
zloy`should I create my own layer?10:20
zloy`or I can customize an existing one?10:20
redenginzloy`, layers just make it easier to reuse what you make10:20
redenginzloy`, that way you won't have to push your changes onto the parent layer10:21
redenginzloy`, inside your build environment it doesn't care about the git heritage10:22
redenginzloy`, make sense?10:23
zloy`redengin: I think yes :) I am creating my own layer anyway :)10:25
*** husanu4 <husanu4!~husanu@> has quit IRC10:25
*** husanu4 <husanu4!~husanu@> has joined #yocto10:26
redenginlayers are a best practice, but once you've added it to your build environment (bblayers.conf) its all one big pool10:26
zloy`understood, thank you10:27
redenginalso, per previous confusion, if you add a layer of bbappend, you still need the layer that includes the bb10:28
*** husanu4 <husanu4!~husanu@> has quit IRC10:28
zloy`ok, I will create a layer :)10:29
*** husanu4 <husanu4!~husanu@> has joined #yocto10:29
zloy`thank you for the support10:29
*** ddalex <ddalex!~ddalex@> has quit IRC10:30
*** husanu4 <husanu4!~husanu@> has quit IRC10:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:39
*** ][Sno][ is now known as [Sno]10:50
zloy`redengin: btw, if I create by own layer, where I want to build busybox and rootfs, should I include meta, meta-yocto and meta-yocto-bsp to bblayers.conf file in the build/conf/ directory?10:51
*** JaMa <JaMa!> has joined #yocto10:56
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC11:05
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:06
rburtonyou only need meta-yocto if you're using poky, and meta-yocto-bsp if you're using a bsp from there11:11
*** miandonmenmian_ <miandonmenmian_!~miandonme@> has quit IRC11:36
*** miandonmenmian <miandonmenmian!~miandonme@> has quit IRC11:37
Crofton|workrburton, thanks for watching stackoverflow11:37
Crofton|workdo postint run at first boot on oe-classic?11:39
florianIf I remember correctly they all run both at install time and at first boot11:51
zwerchCrofton: what florian said, but there is a way to test if it currently runs at first boot. you want it?11:52
rburtonCrofton|work: got a rss feed for "yocto", should probably add more keywords ;)11:53
floriansome scripts that contain bits which will fail not running at boot time test if they executed during install to an offline root11:54
Crofton|workyeah, I think that is correct11:54
floriandbus e.g.11:54
rburtonCrofton|work: he used ${D} in a postinst, which will get expanded during the build11:56
rburtonso have the wrong value11:56
zwerchpkg_postinst_stuff() {11:56
zwerch#!/bin/sh -e11:56
zwerchif [ x"$D" = "x" ]; then11:56
zwerch    # do something at first boot here11:56
zwerch    exit 111:56
Crofton|worksomeone reply on Stackoverflow :)11:57
zwerchWill do :)11:57
Crofton|workwe need to build reputation there11:57
Crofton|workso we can vote down bad answers11:57
Crofton|workrburton, I marked openembedded yocto and poky11:57
rburtonoh, thanks to jku for monitoring stackoverflow12:01
zwerchI answered, UPVOTE PLS 😄12:01
rburtonzwerch: runs at firstboot if rootfs fails12:02
rburtonif rootfs run exits 0, firstboot doesn't happen12:02
rburtoni'd put that in a comment but i don't have enough reputation12:02
rburton(firstboot is basically fallback)12:03
Crofton|workearning reputation seems hard12:03
rburtonespecially when you can't earn reputation with "well, actually" comments :)12:03
zwerchI edited it, better like this?12:04
rburtonwould be good to say that the behaviour is run all postinsts at rootfs time, and any that fail run again on first boot.12:05
rburtonwhich leads to your example12:05
zwerchseems right, yes12:06
rburton*but* the question was about doing something at rootfs time, so he just needs to use $D properly12:06
rburtonoh, unless there's an ordering problem12:06
rburtondoes rpm ensure all depends are installed when it runs the postinst?12:08
Crofton|workwhat do people use to view rss feeds these days?12:16
rburtoni used feedkit on my macbook ;)12:17
Crofton|worklooking at the feedly chrome thing12:18
zwerchReeder on iOS / OS X12:30
*** sameo <sameo!~samuel@> has quit IRC12:39
Crofton|workI'm setting up fedely, see if this helps me12:46
*** husanu3 <husanu3!~husanux1@> has joined #yocto12:50
*** sameo <sameo!~samuel@> has joined #yocto12:52
*** husanu5 <husanu5!~husanux1@> has joined #yocto12:56
*** dmoseley <dmoseley!> has quit IRC12:59
*** husanu5 <husanu5!~husanux1@> has quit IRC13:00
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:02
*** Nilesh_ <Nilesh_!~nilesh@> has joined #yocto13:03
*** Nilesh_ <Nilesh_!~nilesh@> has left #yocto13:04
*** ddalex <ddalex!~ddalex@> has joined #yocto13:04
*** Nilesh_ <Nilesh_!~nilesh@> has joined #yocto13:04
*** hellerbarde <hellerbarde!> has joined #yocto13:05
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:05
*** hugovs <hugovs!~hugo@> has quit IRC13:10
*** hugovs <hugovs!~hugo@> has joined #yocto13:11
*** husanux1 <husanux1!~husanux1@> has joined #yocto13:13
*** husanux1 <husanux1!~husanux1@> has quit IRC13:13
wrockhey, how can you modify the the bitbake core-minimal / core-sato? (I'd like to have some modules from sato in the minimal image)13:14
*** husanux5 <husanux5!~husanux5@> has joined #yocto13:14
wrocksince the sato image is too load it on the zedboard13:15
*** Nilesh_1 <Nilesh_1!~nilesh@> has joined #yocto13:15
*** Nilesh_ <Nilesh_!~nilesh@> has quit IRC13:15
*** husanux5 <husanux5!~husanux5@> has quit IRC13:18
LetoThe2ndwrock: create new image recipe, start with the core minimal one and add the stuff you want13:19
jkuwrock: making your own image is not difficult. You can copy e.g. meta/recipes-sato/images/ and then remove/add image features, and install extra packages and packagegroups13:19
*** tsramos <tsramos!tsramos@nat/intel/x-ohxzwuxohdraxpce> has joined #yocto13:19
*** husanux9 <husanux9!~husanux9@> has joined #yocto13:20
*** husanux9 <husanux9!~husanux9@> has quit IRC13:21
*** varibull <varibull!> has quit IRC13:22
*** varibull <varibull!> has joined #yocto13:22
wrockso minimal is everything in meta/ but without recipes-sato? jku13:24
hellerbardewhat determines the order of layers from which bbappend files are parsed? I have some trouble overriding a variable in a bbappend file from an upstream layer.13:25
*** husanux2 <husanux2!~husanux2@> has joined #yocto13:25
hellerbardeOh and how can I best debug this without building the complete image and flashing it to see what changed?13:25
jkuwrock: minimal is what meta/recipes-core/images/ defines (definitely not everything in meta)13:26
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto13:28
*** husanux2 <husanux2!~husanux2@> has quit IRC13:29
jkuhellerbarde: "bitbake -e <recipe>" is very useful for debugging variables (lots of output though, pipe to a file and search there)13:30
hellerbardejku: okay. thanks a lot.13:31
wrocki have something like that there,were are they defined? IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}"13:33
wrocki guess its the best i lloking for a manual..13:33
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC13:46
kergothhellerbarde: bbappend application order is done in layer priority order, so check your layer priority in your layer.conf.13:47
hellerbardeohhhh, right. I thought i remembered that from somewhere. kergoth thanks so much. So much to remember when getting into this system.13:48
*** jku <jku!jku@nat/intel/x-pcuitkaysxoqlnkw> has quit IRC13:54
*** wadim_ <wadim_!> has quit IRC13:54
*** dfaught <dfaught!> has joined #yocto14:00
*** AndersD <AndersD!> has quit IRC14:00
*** timsche <timsche!> has joined #yocto14:02
*** manderke <manderke!> has joined #yocto14:03
manderkehi guys14:04
manderkeI'm trying to build an image for x86 but I can't seem to make it get rid of the initramfs14:04
manderkeI do not want a live image, I want a normal installation on an usb key14:04
*** dfaught <dfaught!> has quit IRC14:04
manderkeso first step would be to get rid of the initramfs14:05
manderkeif I try to do INITRD_IMAGE = "", build is complaining that: ERROR: Nothing PROVIDES ''14:06
manderkethen it just says my target has no buildable providers14:07
manderkeand that's it14:07
manderkesomehow, somebody drags in the initramfs14:07
manderkehow can I debug that kind of dependency?14:07
*** vmeson <vmeson!> has quit IRC14:07
*** vmeson <vmeson!> has joined #yocto14:10
*** madisox <madisox!> has joined #yocto14:10
*** marekb <marekb!> has quit IRC14:18
rburtonmanderke: define "normal install".  the default image type for x86 is live, so change that instead of trying to hack it.  ie make it build a ext3 file system that you can put in a partition you created, or instead use wic to create a disk image from the ext314:18
manderkerburton, I've changed IMAGE_FSTYPES, it is not live anymore14:19
*** ant_work <ant_work!> has quit IRC14:19
manderkemy problem is happening when IMAGE_FSTYPES is set to my own class14:20
manderkebut only on x86 device14:20
manderkeI've no idea why live is even considered14:22
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-zbydnwntehqerzmn> has joined #yocto14:22
raykinsella78folks - tricky one14:23
raykinsella78I need to pull multiple git repos inorder to build a project.14:23
*** Nilesh_1 <Nilesh_1!~nilesh@> has quit IRC14:23
raykinsella78I need to pull repo into A14:23
raykinsella78I then need to pull repo B in A/B14:23
raykinsella78I then do a make inside A/14:24
raykinsella78make sense?14:24
raykinsella78These are two seperate git repos - not branches on the same repo.14:24
*** behanw <behanw!~behanw@2001:470:b26c:0:58c5:e8bf:b165:9cf2> has quit IRC14:25
rburtonso far so usual14:25
manderkerburton, just gave a try with IMAGE_FSTYPES set to ext3 and I get the same error14:25
rburtonmanderke: don't force initrd_image to ''14:25
rburtonthat's unrelated to "i dont' want a live image"14:26
rburtonraykinsella78: what's the problem?14:26
manderkerburton, if I don't do that, the initramfs ends up embedded in the kernel14:26
raykinsella78rburton - I well I specify two git:// in my SRC_URI, it just ignores the second one.14:26
raykinsella78RC_URI = " \14:27
raykinsella78    git://;protocol=https;branch=svn/branches/UDK2014.SP1;name=UDK2014 \14:27
raykinsella78    git://;protocol=https;branch=master;name=FatPkg \14:27
rburtonmanderke: i thought you wanted a non-live image?  why is using a initramfs so bad?14:28
*** stiandre <stiandre!~stiandre@> has quit IRC14:28
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has quit IRC14:28
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC14:29
rburtonraykinsella78: see recipes-multimedia/gstreamer/ for an example of pulling multiple git repos14:29
raykinsella78legend thanks14:29
rburton(basiscally set destsuffix so it doesn't want to unpack them both to git/14:29
manderkerburton, because the provided initramfs does some things I don't need; for starters I want the rootfs to be mounted from one of the usb's key partition while the init script from the initramfs tries to loop mount a rootfs image file14:30
*** dgm816 <dgm816!> has joined #yocto14:30
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has joined #yocto14:30
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto14:33
*** timsche <timsche!> has quit IRC14:38
*** wrock <wrock!4d5006dc@gateway/web/freenode/ip.> has quit IRC14:39
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto14:44
lpappbluelightning_: hey14:44
bluelightning_I'm not really here btw ;)14:44
lpappah, ok. I will not ask then.14:45
rburtonask the channel, not the GUY WHO SHOULD NOT BE ON IRC14:45
rburtonbluelightning_: don't make me find an op to kick you14:46
zedd_DO IT!!14:46
bluelightning_rburton: I wasn't paying any attention until I was pinged14:46
*** zedd_ is now known as zeddii14:46
lpappbut it is related to our last conversation14:46
lpappbtw, I asked the channel afterwards and no one knew :)14:46
lpappit is about the sdk generation (stripping).14:46
bluelightning_I'm dropping now ;)14:46
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:46
lpappfor some reason I cannot get the files-in-sdk.txt generated14:46
lpappeven though the buildhistory variable looks correct to me.14:46
lpappI am using
Crofton|workwhat is the name for 1.6.3?14:47
lpappand I am not sure how to pin this issue down.14:47
Crofton|workdizzy daisy etc?14:47
Crofton|workhmm, I do not have a build for that to check, sorry14:48
lpappit is probably about my environment, yet I am not sure what to check.14:48
_4urele_rburton, what a leadership!14:48
lpappbased on the manual, it ought to be generated when the SDK is generated.14:48
*** sjolley <sjolley!~sjolley@> has quit IRC14:48
lpappgiven that the buildhistory variable is set up properly.14:48
lpappI can be sure about that with bitbake -e -c populate_sdk myimage | grep ^BUILDHISTORY14:49
lpappBUILDHISTORY_FEATURES="image package sdk"14:50
*** roric_ <roric_!~roric@> has quit IRC14:52
lpappperhaps it is better to ask on the mailing list as it seems to be a bit specific knowledge? :)14:52
lpappand also, it is summer time.14:53
Crofton|workyeah, you need to find someone with a daisy build and compare notes, also, tst on a later build to see if it works as you expect.14:55
Crofton|workI see the file in my master build14:55
manderkeso any idea on how I can get rid off of the initramfs?14:57
lpappCrofton|work: hmm, I can try that with the latest poky, but I cannot test it with my layer :)14:57
lpappbut even that is a good start, indeed.14:57
*** adelcast <adelcast!~adelcast@> has left #yocto14:59
*** ddalex1 <ddalex1!> has joined #yocto15:07
*** benjamirc <benjamirc!~besquive@> has joined #yocto15:17
raykinsella78how do I override the SRCREV of a named branch in local.conf15:19
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC15:20
raykinsella78SRCREV_pn-edk2[branch] isn't working15:21
*** nerdboy <nerdboy!> has joined #yocto15:21
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto15:22
*** behanw <behanw!> has joined #yocto15:25
*** nicolas_ <nicolas_!58a61e6b@gateway/web/freenode/ip.> has joined #yocto15:28
nicolas_Hi guys !15:28
nicolas_I have a question, regarding the use of an external toolchain in yocto15:29
lpappraykinsella78: ?15:29
lpappraykinsella78: SRCREV means some hash, which is available only in one branch15:29
lpappyou will not get the same hash for a commit in a different branch.15:29
lpappso I am not getting your question.15:29
lpappnicolas_: ok15:29
nicolas_I'm currently trying to produce an armhf image for an iMX6 board15:29
nicolas_Using an external toolchain from linaro (2013.10), and it seems to be alsmot working15:30
rburtonraykinsella78: it uses overrides not flags, try SRCREV_branch_pn-edk215:30
nicolas_System boots, but I notice that some of my binaries got prefixed with "arm-linux-gnueabihf-"15:31
rburtonnicolas_: by "some" do you mean "the toolchain"15:31
nicolas_Nope, I mean the package nano for example15:32
rburtonnow that's special15:32
nicolas_Yes ! I started digging, but I am now a little bit hopeless as I can't ssem to find where this would happend15:33
nicolas_And I also can't figre out with some packages would be prefixed and others not15:35
nicolas_I should probably mention that I am using deb packages format15:35
nicolas_rburton: And this is probably all connected, but ldconfig is not found on the target15:37
*** zwerch <zwerch!> has quit IRC15:39
nicolas_Any ideas :) ?15:40
*** sjolley <sjolley!~sjolley@> has joined #yocto15:44
raykinsella78thanks .. rburtion15:47
hellerbardeis there a way to mark a bb as permanently dirty, to force a re-download and a rebuild on every run?15:48
hellerbardeuse -c clean maybe?15:48
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto15:50
hellerbardeso does bitbake -c cleanall delete all the things only for the specified recipe or for _all_ dependencies as well?15:53
rburtoncleanall will remove work tree, sstate, and downloads for the recipe15:55
*** behanw <behanw!> has quit IRC15:58
*** adelcast <adelcast!~adelcast@> has joined #yocto16:01
*** nicolas_ <nicolas_!58a61e6b@gateway/web/freenode/ip.> has quit IRC16:03
*** frsc <frsc!> has quit IRC16:05
kergothheh, that is confusing, since fetchall runs fetch against the recipe and its deps :)16:06
*** TobSnyder <TobSnyder!> has quit IRC16:06
rburtonyeah, i guess16:06
*** ddalex <ddalex!~ddalex@> has quit IRC16:06
*** arfoll <arfoll!arfoll@nat/intel/x-fgxmihzquyidautt> has joined #yocto16:11
*** berton <berton!~fabio@> has joined #yocto16:11
kergothinconsistent, i should say16:15
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto16:22
hellerbardethanks guys.16:23
rburtonkergoth: i had a custom class that caused that too16:24
rburtonkergoth: you've event handlers that cause events to be fired16:24
rburtoni added an event mask to make my handler work, not sure if that's a good enough fix for you16:25
kergothrburton: sanity.bbclass fires events from its handler :P16:26
rburtonalternatively, we basically reference count the assignment of d in execute_handler16:26
rburtoni added a mask and it stopped happening, which is when i stopped caring about the problem...16:26
kergothsanity has eventmask already :)16:26
rburtonkergoth: throw a debug statement before it executes the handler so you know what is causing the problem16:27
RPkergoth: I think its events which trigger other events that do that16:28
kergothyep, see above16:28
RPkergoth: I'm just a bit puzzled why some cases hit it and others generally dont16:28
kergothnone of my sanity tests failed, so i'm assuming its the success event in this case16:29
rburtonkergoth: well my timer class caused that exact error, until i gave it event masks16:30
kergothi don't fire events anywhere in any of my local layers16:30
RPkergoth: log messages are events (e.g. bb.note)16:31
kergothi currently have poky, meta-oe, meta-virtualization, meta-oe, and meta-mentor & meta-sourcery.16:31
kergothi expect we should revert this until the kinks are worked out, if we can't print messages from event handlers, that's a serious problem :)16:31
kergothHmm, it's kind of too bad that event handlers are run immediately in caller context, rather than queued up for execution in an event loop or something16:32
kergothoh well16:32
RPkergoth: well, what puzzles me is the autobuilder works, all my builds work etc16:32
RPkergoth: I'd like to understand how to trigger this16:33
kergothcurrently all i have configured is the poky layers, meta-oe, meta-sourcery, and the meta-mentor layers.16:33
kergothi'll try to pare down to a test case16:33
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-zbydnwntehqerzmn> has quit IRC16:33
kergothit's happening on every bitbake execution in this configuration16:33
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-fyiyyifkkgvchemf> has joined #yocto16:35
RPkergoth: I did comment on earlier btw. If we remove the predefined function capability of register we could implement this like you suggest instead16:35
yoctiBug 7668: enhancement, Medium, 1.9 M1, richard.purdie, IN PROGRESS REVIEW , Feature request: inject 'd' as well as 'e' into event handlers16:35
kergothsaw that, i'd forgotten about the direct function handling..16:35
kergothafaik no one is using that, but i guess some external layer could be16:35
RPkergoth: I'm not aware of anything either fwiw16:36
RPkergoth: the other way is to only remove d from builtins if we added it16:36
* kergoth nods16:37
kergothi wish there was a cleaner way to do this.. can't just inject something into the context of a function object other than through builtins :\16:37
kergothhuh, is rather interesting16:40
kergothalways wondered about that16:40
kergothI always rather liked being able to pass a function into bb.event, as it made it more general purpose, but our event handling is pretty specific to use with our metadata anyway in most cases, so..16:41
*** limbrik <limbrik!~textual@> has quit IRC16:47
tripzerohmm... python3 in poky seems... incomplete16:48
kergothRP: i think rburton is right, it seems related to event handlers with no eventmask (i didn't think i had any left, but i was wrong, should have paid closer attention), so the same event is fired from both the outer and inner events when events are fired from other events.. but i'm not sure why that would cause this failure offhand16:49
kergothhaven't verified that adding eventmasks fixes it yet though, testing further16:49
rburtontripzero: did you just install python3-core and none of the modules (python3-modules will pull them all in)?16:49
kergothspecifically, in this case, if i print messages before and after the event function call, i'm seeing multiple events fired after check_sanity_eventhandler starts but before check_sanity_eventhandler exits16:50
tripzerorburton: probably!16:50
tripzerorburton: is there a way to get bitbake to spit out a list of packages for a recipe?16:50
kergothyep, rburton called it, fixing those resolved the problem16:51
rburtonkergoth: now you can figure out *why*16:51
rburtontripzero: oe-pkgdata-util can do that i think16:52
kergothits possible i had no event handlers that catch the sanity success or failure messages16:52
kergothso nothing was run in the nested event handling16:52
kergothbut ahving a non-eventmasked event handler changed that16:52
kergothi expect adding a handler for the sanity success or failure message would exhibit the same behavior, but that's just a theory16:52
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC16:53
*** sameo <sameo!~samuel@> has quit IRC16:54
*** berton <berton!~fabio@> has quit IRC16:56
*** berton <berton!~fabio@> has joined #yocto16:57
*** sameo <sameo!~samuel@> has joined #yocto17:00
manderkeso did anybody ever ran a yocto kernel on x86 without the initramfs?17:05
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto17:08
*** jku <jku!> has joined #yocto17:12
*** sameo <sameo!~samuel@> has quit IRC17:13
manderkeor to put it differently, did anybody try running a regular (installed) usb yocto os? (as opposed to a live usb yocto image?)17:13
Crofton|workzeddii, awake?17:18
Crofton|work| /home/balister/src/oe-core/build/tmp-glibc/work-shared/ettus-e1xx/kernel-source/arch/arm/include/asm/irqflags.h:11:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef]17:18
Crofton|work|  #if __LINUX_ARM_ARCH__ >= 617:18
Crofton|workany tips on that, with linux-yocto-custom17:19
zeddiiCrofton|work, hmm. was just building lots of random kernels yesterday. that's with an older kernel or 4.1 ?17:20
Crofton|workolder 3.0 era17:21
Crofton|work3.5 era builds, just doesn't work :(17:21
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-fyiyyifkkgvchemf> has left #yocto17:25
*** hitlin37 <hitlin37!uid16371@gateway/web/> has quit IRC17:32
Crofton|workzeddii, might be self inflicted ....17:36
Crofton|workno ....17:36
kergothhmm, wonder how difficult it'd be to make recipetool more extensible by pulling plugins from lib/recipetool/* from all entries in BBPATH17:38
*** Biliogadafr <Biliogadafr!> has quit IRC17:54
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto17:56
*** aswin <aswin!~aswin@> has joined #yocto17:59
*** tsramos <tsramos!tsramos@nat/intel/x-ohxzwuxohdraxpce> has quit IRC17:59
*** dfaught <dfaught!> has joined #yocto18:01
*** husanu7 <husanu7!> has joined #yocto18:02
*** SoylentYellow <SoylentYellow!> has quit IRC18:03
*** ntl <ntl!> has quit IRC18:05
*** husanu7 <husanu7!> has quit IRC18:14
*** ntl <ntl!> has joined #yocto18:18
*** SoylentYellow <SoylentYellow!> has joined #yocto18:19
*** phantoneD <phantoneD!> has quit IRC18:21
*** phantoxeD <phantoxeD!> has joined #yocto18:21
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC18:26
*** sjolley <sjolley!~sjolley@> has quit IRC18:26
*** kw01f <kw01f!> has joined #yocto18:29
*** sjolley <sjolley!sjolley@nat/intel/x-nmvqngfksvviadsb> has joined #yocto18:31
*** kscherer__ <kscherer__!~kscherer@> has quit IRC18:32
*** SoylentYellow <SoylentYellow!> has quit IRC18:32
tripzerogrr.  even with python3-modules I still don't have "imp": ImportError: No module named 'imp'18:34
tripzerowhich means I can't run ""18:34
tripzerorburton: are there any other essential python3 packages besides python3-modules?18:35
*** SoylentYellow <SoylentYellow!> has joined #yocto18:35
*** Mohican <Mohican!~Doug@> has joined #yocto18:36
*** kw01f <kw01f!> has quit IRC18:42
kergothsounds like somebody forgot to include it in the for somer eason18:44
*** paulg_ <paulg_!~paulg@> has joined #yocto18:44
*** tripzero <tripzero!~tripzero@> has quit IRC18:45
*** tripzero <tripzero!~tripzero@> has joined #yocto18:53
rburtontripzero: what kergoth said - please fix the manifest19:03
*** glfernando <glfernando!glfernando@nat/intel/x-hhmkpneorwgvmlxe> has joined #yocto19:07
*** ddalex <ddalex!> has joined #yocto19:23
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto19:23
tripzerorburton: I missed what kergoth said.  which manifest?19:31
tripzerokergoth: can repeat directive?19:32
*** benjamirc <benjamirc!~besquive@> has quit IRC19:32
*** benjamirc <benjamirc!besquive@nat/intel/x-aggbqfisrproahui> has joined #yocto19:34
*** benjamirc <benjamirc!besquive@nat/intel/x-aggbqfisrproahui> has quit IRC19:36
kergothsee scripts/contrib/python/ and meta/recipes-devtools/python/ which is generated by it19:41
kergothimp must be missing from the former, add it19:41
*** [Sno] <[Sno]!> has quit IRC19:45
*** nighty^ <nighty^!> has quit IRC19:49
*** seebs <seebs!> has quit IRC19:54
*** vmeson <vmeson!> has quit IRC19:56
*** berton <berton!~fabio@> has quit IRC19:56
*** vmeson <vmeson!> has joined #yocto19:56
*** berton <berton!~fabio@> has joined #yocto19:56
*** nighty^ <nighty^!> has joined #yocto19:59
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC20:01
*** seebs <seebs!> has joined #yocto20:02
tripzerokergoth: thx20:05
*** jku <jku!> has quit IRC20:20
*** staylor <staylor!> has joined #yocto20:23
*** pohly <pohly!> has quit IRC20:29
*** berton <berton!~fabio@> has quit IRC20:33
*** ddalex <ddalex!> has quit IRC20:35
*** paulg_ <paulg_!~paulg@> has quit IRC20:36
*** tsramos <tsramos!~tsramos@> has joined #yocto20:41
*** tsramos__ <tsramos__!~tsramos@> has joined #yocto20:42
*** tsramos_ <tsramos_!~tsramos@> has quit IRC20:44
*** tsramos <tsramos!~tsramos@> has quit IRC20:45
*** ddalex <ddalex!> has joined #yocto20:47
*** lamego <lamego!~lamego@> has joined #yocto20:49
*** ddalex <ddalex!> has quit IRC20:51
*** sjolley <sjolley!sjolley@nat/intel/x-nmvqngfksvviadsb> has quit IRC20:56
*** sjolley <sjolley!sjolley@nat/intel/x-tzmytegckcvnutwr> has joined #yocto21:03
*** jimBaxter <jimBaxter!> has quit IRC21:03
*** [Sno] <[Sno]!> has joined #yocto21:04
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC21:10
*** dfaught <dfaught!> has joined #yocto21:12
*** davez <davez!43b812c0@gateway/web/freenode/ip.> has joined #yocto21:12
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto21:13
RPCrofton|work: someone should see if we could share a test framework ;-)21:15
*** dfaught <dfaught!> has quit IRC21:21
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC21:32
-YoctoAutoBuilder- build #347 of nightly-fsl-ppc is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1 UploadToasterEventlog] Build details are at
-YoctoAutoBuilder- build #355 of nightly-fsl-ppc-lsb is complete: Failure [failed BuildImages UploadToasterEventlog] Build details are at
*** JaMa <JaMa!> has quit IRC21:36
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC21:36
Crofton|workRP, everyone should write their own21:38
*** paul_ <paul_!> has joined #yocto21:39
*** tsramos__ <tsramos__!~tsramos@> has quit IRC21:45
*** paul__ <paul__!> has joined #yocto21:45
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has quit IRC21:47
*** paul_ <paul_!> has quit IRC21:50
*** tsramos <tsramos!~tsramos@> has joined #yocto21:52
RPkergoth: I quickly wrote up a patch to fix that event handler issue, at least in theory21:54
RPkergoth: whether we should do something different remains to be seen21:54
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto21:57
*** dbozec <dbozec!~dbozec@2001:41d0:fe78:1700:3c2c:2840:cb01:45b3> has quit IRC21:59
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
* kergoth nods, he doesn't have a very strong opinion on it either way, though modifying __builtins__ feels slightly uglier22:03
-YoctoAutoBuilder- build #346 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at
*** madisox <madisox!> has quit IRC22:07
-YoctoAutoBuilder- build #349 of nightly-ppc-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #358 of nightly-non-gpl3 is complete: Failure [failed BuildImages] Build details are at
*** dbozec <dbozec!~dbozec@2001:41d0:fe78:1700:407d:1d03:e91f:784e> has joined #yocto22:11
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto22:12
*** hugovs <hugovs!~hugo@> has quit IRC22:13
-YoctoAutoBuilder- build #351 of nightly-qa-pam is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** clsulliv1 <clsulliv1!~clsulliv@> has left #yocto22:15
*** rburton <rburton!> has quit IRC22:19
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has joined #yocto22:23
-YoctoAutoBuilder- build #348 of nightly-qa-extras is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1] Build details are at
*** madisox <madisox!> has joined #yocto22:25
*** tripzero <tripzero!~tripzero@> has quit IRC22:25
-YoctoAutoBuilder- build #353 of nightly-multilib is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at
-YoctoAutoBuilder- build #357 of nightly-world is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC22:31
-YoctoAutoBuilder- build #351 of nightly-qa-logrotate is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC22:32
-YoctoAutoBuilder- build #6 of ptest-x86-64 is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #348 of buildtools is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #346 of nightly-intel-gpl is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #364 of poky-tiny is complete: Failure [failed BuildImages] Build details are at
*** phantoneD <phantoneD!> has joined #yocto22:44
*** phantoxeD <phantoxeD!> has quit IRC22:47
-YoctoAutoBuilder- build #348 of build-appliance is complete: Failure [failed BuildImages BuildImages_1] Build details are at
*** lamego <lamego!~lamego@> has quit IRC22:50
*** madisox <madisox!> has quit IRC22:51
-YoctoAutoBuilder- build #351 of nightly-qa-systemd is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2] Build details are at
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC22:58
*** tsramos <tsramos!~tsramos@> has quit IRC22:59
*** tsramos <tsramos!~tsramos@> has joined #yocto22:59
*** tsramos <tsramos!~tsramos@> has quit IRC23:04
-YoctoAutoBuilder- build #351 of nightly-oecore is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** madisox <madisox!> has joined #yocto23:06
*** paul__ <paul__!> has quit IRC23:07
*** vdehors_ <vdehors_!> has quit IRC23:09
*** vdehors_ <vdehors_!> has joined #yocto23:10
*** Crofton|work <Crofton|work!> has quit IRC23:14
*** Crofton <Crofton!> has quit IRC23:15
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has quit IRC23:17
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has joined #yocto23:26
*** Crofton|work <Crofton|work!~balister@> has joined #yocto23:28
*** Crofton <Crofton!~balister@> has joined #yocto23:28
*** sjolley <sjolley!sjolley@nat/intel/x-tzmytegckcvnutwr> has quit IRC23:33
*** behanw <behanw!~behanw@2001:470:b26c:0:8915:1977:5054:4e69> has joined #yocto23:33
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto23:43
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC23:48
*** seebs <seebs!> has quit IRC23:51
*** seebs_ <seebs_!> has joined #yocto23:51

Generated by 2.11.0 by Marius Gedminas - find it at!