Friday, 2014-10-03

*** sjolley <sjolley!sjolley@nat/intel/x-epphaycqqyzknytd> has quit IRC00:01
*** auke- <auke-!~auke@> has quit IRC00:02
*** Fivefootseven <Fivefootseven!~fivefoots@> has joined #yocto00:10
seebsFWIW, it looks like there's a lot of path mismatch messages from pseudo which are harmless, because they apply to the case where a file is created before a previous unlink is processed, *but*, the database actually does the right thing.00:23
seebsTesting out a patch which doesn't produce that message when it's a did_unlink message.00:23
*** seebs <seebs!> has quit IRC00:24
*** auke- <auke-!~auke@> has joined #yocto00:26
*** seebs <seebs!> has joined #yocto00:27
*** Fivefootseven <Fivefootseven!~fivefoots@> has quit IRC00:28
*** Fivefootseven <Fivefootseven!~fivefoots@> has joined #yocto00:28
*** Fivefootseven <Fivefootseven!~fivefoots@> has quit IRC00:33
*** Fivefootseven <Fivefootseven!~fivefoots@> has joined #yocto00:39
*** Fivefootseven <Fivefootseven!~fivefoots@> has quit IRC00:44
*** sarahsharp <sarahsharp!~sarah@> has quit IRC01:06
*** davisroman <davisroman!42ce7843@gateway/web/freenode/ip.> has joined #yocto01:24
*** jkridner|work <jkridner|work!> has joined #yocto01:25
*** pev <pev!~pev@> has joined #yocto01:26
pevAnyone having GCC 4.6 issues? I have a setup that was working before that now fails gcc-cross-initial with "internal compiler error: Segmentation fault". I'm assuming this is to do with me now running under ubuntu 14.04 where I was using 12.04 before...01:28
*** blloyd__ is now known as Prowell01:29
*** Fivefootseven <Fivefootseven!~fivefoots@> has joined #yocto01:36
*** Fivefootseven <Fivefootseven!~fivefoots@> has quit IRC01:41
*** Fivefoot_ <Fivefoot_!~fivefoots@> has joined #yocto01:42
-YoctoAutoBuilder- build #59 of nightly-ipk is complete: Success [build successful] Build details are at
*** sjolley <sjolley!sjolley@nat/intel/x-pggagsdjpqqumxpn> has joined #yocto02:44
*** victhor_ <victhor_!~victhor@> has quit IRC03:08
*** Fivefootseven <Fivefootseven!> has joined #yocto03:30
*** Fivefoot_ <Fivefoot_!~fivefoots@> has quit IRC03:34
*** Fivefootseven <Fivefootseven!> has quit IRC03:43
*** Fivefootseven <Fivefootseven!> has joined #yocto03:44
*** Fivefootseven <Fivefootseven!> has quit IRC03:48
*** jkridner|work <jkridner|work!> has quit IRC04:04
*** staylor <staylor!> has joined #yocto04:21
*** dvhart <dvhart!dvhart@nat/intel/x-uaxvtyzyhrpjjyol> has joined #yocto04:25
*** dvhart <dvhart!dvhart@nat/intel/x-uaxvtyzyhrpjjyol> has quit IRC04:25
*** e8johan <e8johan!~quassel@> has joined #yocto04:34
-YoctoAutoBuilder- build #59 of nightly-qa-systemd is complete: Failure [failed Running Sanity Tests] Build details are at
*** staylor <staylor!> has quit IRC04:48
*** AndersD <AndersD!> has joined #yocto05:29
*** _dv_ <_dv_!> has joined #yocto05:38
*** dv_ <dv_!> has quit IRC05:39
*** gebreselaisi <gebreselaisi!~florin@> has quit IRC05:40
*** gebreselaisi <gebreselaisi!~florin@> has joined #yocto05:43
*** AndersD <AndersD!> has quit IRC06:00
*** AndersD <AndersD!> has joined #yocto06:01
KevinZAhi all. sorry, real new-user question: i've modified the splash picture, and i can see bitbake knows about the bbappend, but if i simply rerun "bitbake rpi-hwup-image" i don't get a new image built.06:02
*** zecke <zecke!~ich@> has joined #yocto06:06
*** g1zer0 <g1zer0!> has joined #yocto06:08
KevinZAah found it - bitbake psplash -c clean06:12
*** bboozzoo_away is now known as bboozzoo06:24
*** SorenHolm <SorenHolm!~quassel@> has joined #yocto06:25
*** e8johan <e8johan!~quassel@> has quit IRC06:35
*** e8johan_ <e8johan_!~quassel@> has joined #yocto06:35
*** ant_work <ant_work!> has joined #yocto06:46
*** Jefro <Jefro!~jefro@> has joined #yocto06:51
*** Jefro <Jefro!~jefro@> has quit IRC06:52
*** Jefro <Jefro!~jefro@> has joined #yocto06:53
*** mckoan|away is now known as mckoan06:59
mckoangood morning06:59
*** AndersD <AndersD!> has quit IRC07:03
*** AndersD <AndersD!> has joined #yocto07:04
*** agust <agust!> has joined #yocto07:05
*** kroon <kroon!> has joined #yocto07:06
*** tasslehoff <tasslehoff!> has joined #yocto07:14
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto07:25
*** jbrianceau_away is now known as jbrianceau07:27
xerentgood morning07:34
xerentI can't find CONFIG_REGMAP in the kernel config for 3.10.31-yocto-generic, nor in the menuconfig07:35
xerentif I set it anyway, I get a check kernelconfig error from bitbake07:35
xerentbut according to the Internet, the kernel config option DOES exist07:36
xerentso the question is - why me?07:36
*** blitz00 <blitz00!~stefans@> has joined #yocto07:37
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto07:37
*** sameo <sameo!~samuel@> has joined #yocto07:39
*** sameo <sameo!~samuel@> has quit IRC07:42
*** sameo <sameo!~samuel@> has joined #yocto07:43
*** roric <roric!> has quit IRC07:44
erboxerent: doesn't look like it's supposed to show up in menuconfig,
erboxerent: I think it's supposed to be pulled in by the thing that needs it07:45
xerentwhich in my case is a stand-alone driver07:45
xerentso I need it anyway07:45
*** dvorkbjel <dvorkbjel!> has quit IRC07:46
erbodo you have any of those enabled as well?07:47
xerentyes, I set all of them to appropriate y or m07:47
*** dvorkbjel <dvorkbjel!> has joined #yocto07:47
xerentexcept, SPMI - that isn't in 3.1007:48
erbono clues from the error msg?07:49
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC08:01
erbohmm, I have no good ideas :(08:03
*** Jefro <Jefro!~jefro@> has quit IRC08:04
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto08:07
KevinZAwhat causes a package to be listed in PACKAGES multiple times?08:19
KevinZAi have one .bb file for psplash, and in the layers i am using, there are only .bbappend files08:19
KevinZAi copied the psplash files from the meta-raspberrypi layer into mine, but bitbake gives that error when i include my psplash-git.bbappend in the build08:21
*** olani` <olani`!user@nat/axis/x-gamdbqyyxcotkskc> has joined #yocto08:23
*** olani <olani!user@nat/axis/x-okitsacxnjmzidly> has quit IRC08:26
gebreselaisihi guys08:33
gebreselaisianybody else missing the dbus service for the session bus?08:33
gebreselaisiI'm on dbus 1.8.208:33
gebreselaisifrom poky08:33
*** jimBaxter <jimBaxter!> has joined #yocto08:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:40
*** roric <roric!~roric@> has joined #yocto08:42
bluelightningmorning all08:47
gebreselaisibluelightning, quick question08:48
mckoanhi bluelightning, all08:48
gebreselaisiisn't dbus supposed to have a session bus systemd service?08:48
gebreselaisican't find it when building from poky08:48
bluelightninggebreselaisi: I'm not sure to be honest... rburton?08:48
*** belen <belen!Adium@nat/intel/x-wzgathcicstpyyas> has joined #yocto08:49
*** belen <belen!Adium@nat/intel/x-wzgathcicstpyyas> has quit IRC08:58
*** phantoxe <phantoxe!> has joined #yocto09:13
*** frsc <frsc!> has joined #yocto09:14
*** e8johan_ <e8johan_!~quassel@> has quit IRC09:15
*** Noor <Noor!~quassel@> has joined #yocto09:16
*** e8johan <e8johan!~quassel@> has joined #yocto09:16
rburtoniirc, it doesn't have a session bus out of the box.    if you're trying to do a user session managed by systemd, then you should know that they're currently a bit broken.09:22
gebreselaisia bit? in what sense?09:34
xerenta 1 should be a 0 somewhere09:35
xerenterbo: I'm still clueless about CONFIG_REGMAP09:36
xerentit gets unset by bitbake/scripts no matter what I do09:36
rburtongebreselaisi: "doesnt work"09:38
rburtongebreselaisi: the tizen guys made it somewhat work with patches to everything, we've patches on the list to do wayland in a user session, but vt switching is messed up09:39
rburtongebreselaisi: if you want to do a user session in dbus, be prepared to patch systemd upwards09:39
*** victhor_ <victhor_!~victhor@> has joined #yocto09:42
frscHi. Im trying to build meta-toolchain-qt5, but I can't relove the error I'm getting during do_populate_sdk: error: file /lib/ conflicts between attempted installs of libc6-thread-db-2.20-r0.cortexa9hf_vfp_neon and libthread-db1-2.19-r0.cortexa9hf_vfp_neon09:54
frscCan anyone help?09:54
*** bboozzoo is now known as bboozzoo_away10:17
*** gvy <gvy!~mike@altlinux/developer/mike> has joined #yocto10:21
*** victhor_ <victhor_!~victhor@> has quit IRC10:25
mckoanfrsc: which branch and machine?10:28
KevinZAhi. is it possible to automatically detect the kernel version that (e.g.) linux-raspberrypi is using, then download the right realtime patch and apply it?10:29
KevinZA^ i mean in my new layer for a realtime raspberry pi image10:30
bluelightningKevinZA: in theory you could do a bbappend that used a wildcard for the version (e.g. linux-raspberrypi_%.bbappend) and in there you could use ${PV} as a substitute for the actual version, provided that that version only ever represents the kernel version10:32
bluelightningwoah, there are way too many kernel versions in meta-raspberrypi...10:33
KevinZAthanks bluelightning. so "best practice" might be for my layer to specify a kernel version by git, and i will actually manually download the appropriate patch in the files directory?10:34
KevinZAhaha yes10:34
frscmckoan: it's a custom imx6 board and I tried with the fsl-release repo. I'm now trying with the community meta-qt5 layer (master) and see if that works.10:35
bluelightningKevinZA: that would be harder because then you don't know what version of the kernel you are building until you unpack the source, which happens after fetching...10:36
bluelightningKevinZA: honestly I would poke the meta-raspberrypi maintainer to drop the outdated kernel versions, I can't believe all of those are needed10:36
KevinZAwill do - btw when an irc has a "name:", is that a private reply? I don't want to spam the channel... but i've never used irc...10:38
rburtonKevinZA: no, it's just a message aimed at someone else, that everyone else can see10:40
rburtonKevinZA: is the publicly archived log.  everyone sees what is in this room.10:41
*** belen <belen!Adium@nat/intel/x-fmkmybxmytxxlvmq> has joined #yocto10:41
bluelightningKevinZA: in most IRC clients mentioning a person's name causes that line to be highlighted by that person's IRC client, so it's a way of getting their attention10:41
KevinZAok thanks10:42
*** roric <roric!~roric@> has quit IRC10:42
*** roric <roric!~roric@> has joined #yocto10:48
*** g1zer0 <g1zer0!> has quit IRC10:56
*** KevinZA <KevinZA!> has quit IRC11:00
*** KevinZA <KevinZA!> has joined #yocto11:03
*** systmkor <systmkor!~systmkor@unaffiliated/systmkor> has joined #yocto11:24
*** systmkor4 <systmkor4!~systmkor@unaffiliated/systmkor> has quit IRC11:24
*** jluisn <jluisn!~quassel@> has joined #yocto11:35
*** mike7b4_on_x230 <mike7b4_on_x230!> has joined #yocto11:54
*** _dv_ is now known as dv_11:59
xerentbluelightning: have you any experience with kernel configurations gone berserk in Yocto? I'm trying to build with CONFIG_REGMAP, but it gets unset in do.log_kernel_checkconfig11:59
*** ant_work <ant_work!> has quit IRC11:59
mckoanfrsc: using the community  meta-qt5 layer (12:01
RPJaMa|Off: we've found a pseudo bug which might explain those pseudo permissions issues you reported, particularly if it was on xfs with 64 bit inodes12:01
mckoanfrsc: using the community meta-qt5 layer (daisy) works12:01
*** KevinZA <KevinZA!> has quit IRC12:04
*** e8johan <e8johan!~quassel@> has quit IRC12:04
*** KevinZA <KevinZA!> has joined #yocto12:05
*** KevinZA <KevinZA!> has quit IRC12:09
*** KevinZA <KevinZA!> has joined #yocto12:09
gebreselaisirburton, can you point me to the patches in the mailing list for the wayland user dbus session?12:21
*** eballetbo <eballetbo!> has quit IRC12:25
*** marka <marka!~marka@> has joined #yocto12:29
*** ddalex1 <ddalex1!~ddalex@> has quit IRC12:32
*** ddalex <ddalex!> has joined #yocto12:47
*** TRoGd0R <TRoGd0R!> has joined #yocto12:53
*** SorenHolm <SorenHolm!~quassel@> has quit IRC12:54
*** j6V6t <j6V6t!> has joined #yocto12:55
rburtongebreselaisi: search for patches by valentin, the oe-core patchworks has a search button12:56
TRoGd0RHow do I enable eglfs support for Qt 5.2.1 (Yocto version Daisy) from my local.conf?  When I look in my config.summary it says QPA  backend EGLFS no.  I have disabled x11 and wayland and added qtbase-plugins to IMAGE_INSTALL_append.  What else am I missing?12:56
*** ddalex <ddalex!> has quit IRC13:02
*** SorenHolm <SorenHolm!~quassel@> has joined #yocto13:07
ndecTRoGd0R: have a look at this layer: i use that to build an image with qt5/eglfs for x86 and arm targets.13:08
ndecthe 2 important files are, and
mckoanndec: interesting, but which image are you building here?13:13
ndeci have a test image in recipes-core13:14
ndecthe image has enough to play html5 video on youtube for example. that was my use case..13:14
*** rwoolley <rwoolley!~rwoolley@> has joined #yocto13:14
mckoanndec: probably would be interesting to see which qt packages you are using too13:15
ndecwhat do you mean/13:15
mckoanndec: I mean that your meta-qt5-emulator is not enough to understand how to properly build qt513:16
ndecwell, it should be enough. what's missing?13:16
mckoanndec: would be useful to see your image13:16
mckoanndec: for examlpe what thete is in IMAGE_INSTALL_append =13:17
*** ddalex <ddalex!~ddalex@> has joined #yocto13:17
mckoanndec: qtbase, etc13:18
ndecqtbase is in qt5-example-image.bb13:18
TRoGd0Rso there is no way to add the eglfs support option into my IMAGE_INSTALL_append var in my local.conf?13:18
mckoanndec: fine so you are using qt5-example-image, thx13:18
*** g1zer0 <g1zer0!> has joined #yocto13:18
ndecTRoGd0R: no. i don't think.13:19
mckoanndec: and where is located?13:19
ndecyou need to bbappend qtbase13:19
ndecrecipes-core/images in the layer above13:20
mckoanndec: uh, I've missed that sorry13:20
mckoanndec: as far as you know would be possible to enable Qsqlite ?13:21
ndecmckoan: how is it normally enabled?13:21
mckoanndec: ./configure13:22
TRoGd0RThe weird thing is this all worked before I upgraded to Daisy. I had eglfs by default, anyone know what changed?13:22
ndecmckoan: qtbase has 2 PACKAGECONFIG: sql-sqlite and sql-sqlite2, you can enable easily in bbappend the one you want.13:23
mckoanndec: I expected it was PACKAGECONFIG_append = "sqlite" that may be the reason of my failure13:24
ndecTRoGd0R: i think the default in qtbase has always been gl, not gles2 in PACKAGECONFIG. so i don't see how eglfs could have been enabled by default13:25
TRoGd0ROk so I have a qtbase_5.2.1.bbappend file created.  What do I need to add into again.  Sorry I'm a noob13:25
TRoGd0RPACKAGECONFIG_GL = "gles2"13:25
TRoGd0Rcool, I'll try it now13:26
*** SorenHolm <SorenHolm!~quassel@> has quit IRC13:26
ndecmckoan: check for the exact PACKAGECONFIG names.13:26
ndecand mckoan don't forget the " " when using _append13:26
mckoanndec: indeed! incredible, it was an oversight13:27
mckoanndec: thanks13:27
ndecTRoGd0R: if you set PACKAGECONFIG to gles2, then qtbase will be built with "-opengl es2 -eglfs"13:27
TRoGd0RIs that what I want?13:27
mckoanndec: maybe do you mean PACKAGECONFIG_GL = "gles2" ?13:28
mckoanndec: ;-)13:28
*** Fivefootseven <Fivefootseven!> has joined #yocto13:28
ndeceventually it's used to set PACKAGECONFIG ;-)13:28
ndecTRoGd0R: which platform/target are you building for?13:29
TRoGd0RI made the change in my bbappends file and tried to bitbake but it said there was nothing needed to be rerun.  Do I have to force it to build?13:29
TRoGd0RI am building for a custom board that has an am335x13:30
ndechmm. i would expect it to detect the change... can you check with "bitbake -e qtbase | grep ^PACKAGECONFIG"13:30
mckoanTRoGd0R: I added sql-sqlite to my PACKAGECONFIG_append and it was rebuilding13:30
ndecto ensure you've set the value correctly.13:30
mckoanndec: I've noticed you have may projects in github, I wonder if you have ever been able to run Qt5 on AM355x-EK using YP daisy13:33
ndeci have had qt5/eglfs on many other arm soc/boards, but not this one ;-)13:34
mckoanndec: it's the only one I have not working :-(13:35
mckoanndec: however you gave me the idea to test qemux86 with vmdk, just for fun in the weekend13:36
ndechehe.. that's actually quite nice, we did that for a project based on qt5/eglfs so that we could develop/test on emulator..13:36
ndecactually the whole idea and most of the implementation details were based on JaMa|Off's stuff..13:37
TRoGd0RIt's weird, it won't notice the change and rebuild just that part.  I guess I am going to have to do a clean build unless there is a way to just force the qt part to build13:42
mckoanndec: of course JaMa|Off stuff rocks!13:43
TRoGd0RWould this work bitbake -c cleanall base-files qt5 core-image-base?13:44
ndecTRoGd0R: have you tried the bitbake -e command above? you need to make sure you did the .bbappend right first.13:47
TRoGd0RI just kicked off a clean build13:49
*** Siecje <Siecje!~Siecje@> has joined #yocto13:50
*** tasslehoff <tasslehoff!> has quit IRC13:58
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC14:11
*** SorenHolm <SorenHolm!> has joined #yocto14:12
otavioIs someone looking at 1.7 toolchain issues? We managed to reproduce same error in 1.6 and 1.7 SDKs14:20
*** Fivefoot_ <Fivefoot_!~fivefoots@> has joined #yocto14:24
*** Fivefootseven <Fivefootseven!> has quit IRC14:27
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto14:35
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto14:35
*** SorenHolm <SorenHolm!> has quit IRC14:38
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto14:45
*** staylor <staylor!> has joined #yocto14:56
*** Fivefootseven <Fivefootseven!> has joined #yocto14:56
*** ddalex <ddalex!~ddalex@> has quit IRC14:58
*** sarahsharp <sarahsharp!~sarah@> has quit IRC14:59
*** Fivefoot_ <Fivefoot_!~fivefoots@> has quit IRC15:00
*** gabrbedd <gabrbedd!> has quit IRC15:05
JaMa|OffRP: yes I was reading your chat with seebs, unfortunately in my case it was on ext4, but I'll re-check with the pseudo changes as well15:06
*** gabrbedd <gabrbedd!> has joined #yocto15:07
*** munch <munch!> has joined #yocto15:08
JaMa|Offndec: you don't need .bbappend, you can just use _pn-qtbase in your local.conf15:09
ndecJaMa|Off: right. he wanted to be able to do it with IMAGE_INSTALL, actually.15:10
*** sarahsharp <sarahsharp!sarah@nat/intel/x-hlrmlrlqhfxpyvjr> has joined #yocto15:13
*** munch <munch!> has quit IRC15:14
*** munch <munch!~mark@> has joined #yocto15:14
TRoGd0RWhat do I add to _pn-qtbase in my local.conf?15:14
*** Fivefoot_ <Fivefoot_!~fivefoots@> has joined #yocto15:14
*** ddalex <ddalex!~ddalex@> has joined #yocto15:16
*** kscherer <kscherer!~kscherer@> has joined #yocto15:17
*** Fivefootseven <Fivefootseven!> has quit IRC15:18
RPJaMa|Off: its possible on large filesystems you could have hit 64 bit inodes15:18
*** roric <roric!~roric@> has quit IRC15:26
mckoanndec: despite I see /usr/lib/ in my rootfs I can't find any libqsqlite*15:30
mckoanhow can be generated libqsqlite with qt5 ?15:31
mckoanPACKAGECONFIG_append = " sql-sqlite" seems doesn't have any effect15:33
ndecmckoan: well, it has the effect to add "-sql-sqlite" to qtbase configure options...15:34
*** SorenHolm <SorenHolm!> has joined #yocto15:40
ndecmckoan: i am not familiar with that part.. but looking at, it seems that -sql-xxx has been rename -qt-sql-xxx...15:41
*** sarahsharp <sarahsharp!sarah@nat/intel/x-hlrmlrlqhfxpyvjr> has quit IRC15:41
*** g1zer0 <g1zer0!> has quit IRC15:41
otaviorburton: I am debugging the mesa failure in fsl-arm15:42
mckoanndec: thx, I am not familiar with qt :-)15:42
otavioand it looks to be a bug in pkgdata. It is generating the files for 'empty' packages. In the mesa case, openvg is already disabled in mesa and it outputs the pkgdata anyway15:42
*** blloyd <blloyd!> has joined #yocto15:43
otaviorburton: i will have lunch and be back in 1h or so15:43
mckoanndec: BTW in meta-qt5 we are still using 5.2.115:44
*** sarahsharp <sarahsharp!sarah@nat/intel/x-lbuvbqrymufdmiwj> has joined #yocto15:44
rburtonotavio: interesting and easy to replicate. can you file a bug?15:44
*** challinan <challinan!> has quit IRC15:44
blloydis there an easy way to see why postinst scripts are not working as expected?  I have a custom bitbake package.  I have an image that installs two rpm packages from it, both with postinst scripts.  But neither appear to fire at all.15:44
blloydanother postinst from the same custom package works just fine in another image that only installs one rpm package from the problem bitbake package.15:45
rburtonblloyd: the rootfs log should have the output of them when executed at rootfs time, and if they're delayed then there should be something in /var/log with the output there15:45
mckoanndec: looks like qtbase-opensource-src-5.2.1 uses -qt-sql-<driver> ... Enable a SQL <driver> in the Qt SQL module15:46
mckoanso the recipe in meta-qt5 needs a patch15:46
*** kroon <kroon!> has quit IRC15:46
mckoanI'm trying PACKAGECONFIG[qt-sql-sqlite] = "-qt-sql-sqlite,-no-sql-sqlite,sqlite3"15:48
blloydwhere is the rootfs log at?15:48
otaviorburton: #679515:49
blloydnm, found it.15:51
*** SorenHolm <SorenHolm!> has quit IRC15:55
*** munch <munch!~mark@> has quit IRC16:00
*** sarahsharp1 <sarahsharp1!~sarah@> has joined #yocto16:04
*** sarahsharp <sarahsharp!sarah@nat/intel/x-lbuvbqrymufdmiwj> has quit IRC16:05
*** mkeeter <mkeeter!~mkeeter@> has quit IRC16:15
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto16:16
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto16:16
ndecmckoan: you don't need to change the packageconfig name, just need to configure options. otherwise you are breaking existing recipes..16:20
mckoanndec: ok16:24
rburtonotavio: so RP has a hunch, can you make a patch :)16:26
RPwell, testing it would be good too!16:26
rburtonyeah that too :)16:27
RPseebs: could we have a release of pseudo please? :)16:29
RPhalstead: around?16:29
*** gvy <gvy!~mike@altlinux/developer/mike> has quit IRC16:30
RPhalstead: I'd like to wipe sstate and run a build from scratch of master-next on the abs16:31
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC16:34
mckoanhave a nice rest of the day16:35
*** mckoan is now known as mckoan|away16:35
kergothhuh, just got an OSError traceback from a setscene16:37
kergoththats new16:37
*** roric <roric!> has joined #yocto16:39
*** mkeeter <mkeeter!~mkeeter@> has quit IRC16:43
*** roric <roric!> has quit IRC16:47
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC16:47
kergothand using sstate locked sigs just gave me a traceback too16:48
kergothalso looks like you can't use -S printdiff to figure out why the locked sigs aren't being used when you're including the locked sigs file, it checks them even though I'm not trying to build anything16:49
*** sameo <sameo!~samuel@> has quit IRC16:50
edsiperhi, anyone here is creating or implementing certain web services for their projects ?, if so, please ping me back as I am collecting some information as we as open source organization have some plans for a generic Yocto Web Service so your input would be valuable.16:53
*** mike7b4_on_x230 <mike7b4_on_x230!> has quit IRC16:54
*** seebs <seebs!> has quit IRC16:58
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC16:58
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto16:59
rburtonedsiper: what's a generic yocto web service?17:00
*** seebs <seebs!> has joined #yocto17:00
*** phantoxe <phantoxe!> has quit IRC17:00
edsiperrburton, specific web service exposing certain interfaces and information. For a generic case: CPU, Memory Storage, plus something more specific (that I am trying to discover) like: metrics, serial input, HW stuff, etc17:02
halsteadRP, I'll clear sstate now.17:03
edsiperrburton, so anyone building a OS using Yocto, be able to install this package and have those informational features enabled17:03
seebsI'm still studying some other diagnostics I'm getting from pseudo, but I *think* the huge spam of filesystem name changes I was seeing may have been a diagnostics issue. Specifically, the speculative-unlink code is working perfectly, I think, except that the path name mismatch reports are useless if the operation is did_unlink.17:03
seebsBecause then it's sort of expected.17:04
RPseebs: makes sense17:04
rburtonedsiper: system stats over http, basically?17:04
seebsAnyway, I have a patch to suppress those errors in that case, and my plan is to rerun the build that generated those messages with that change and see what happens.17:04
seebsIt may well be that there's still issues.17:04
RPseebs: the tricky issue is that we're now in release mode and at the very least I'd like to fix the 64 bit truncation issue17:05
CroftonRP, While I am thinking, should ASSUME_PROVIDED_remove = "git-ntive" work?17:05
CroftonI need to try it17:05
seebsI just want to make sure I'm not missing something else horrible. And actually, I have a suspicion that there may be a way to break things with did_unlink still.17:05
RPseebs: we have a little time but not much until the next rc so its really just a headsup that we will need to do it17:05
seebsHow much time is "not much"?17:06
RPCrofton: in theory, its not well tested17:06
RPCrofton: git from a buildtools-tarball is the other alternative17:06
edsiperrburton, more than stats, but yes.17:06
RPseebs: next rc is Tuesday17:06
CroftonRP, my problem is the uhd cmake detects a git binary so it can bury a git hash in the binary17:08
Croftonand the cmake setup is grreat at preventing cmake from finding the host git17:08
seebsOkay. The error message fix removes several of the problems, although I am very curious about one of the remaining messages.17:08
Croftonwhich is in general a good thing17:08
Croftonand trying to run git-native fails since it is provided17:09
seebsBecause I'm getting create messages about a thing which somehow came into the database with no path.17:09
*** systmkor1 <systmkor1!~systmkor@unaffiliated/systmkor> has joined #yocto17:09
CroftonI checked that removing git-native from AP solves my "problem"17:09
RPseebs: meanwhile, halstead has wiped out our sstate, we'll retry a complete build from scratch17:09
CroftonI am looking for a good way to do this without hand modifying oe-core conf files17:09
RPCrofton: hang on, what are you trying to do here17:10
* Crofton also has a low opinion of people who freak out over not having the git hash in the binary :)17:10
seebsThere is an actual bug to be had involving DID_UNLINK.17:10
RPCrofton: do you want git-native or not?17:10
*** systmkor <systmkor!~systmkor@unaffiliated/systmkor> has quit IRC17:10
RPCrofton: right, ok17:10
Croftonand it needs to be in the oe space, not build system17:10
seebsThe sanity-checks that do things like unconditionally wipe out a database entry if we get a file/directory mismatch aren't conditional on that.17:10
Croftoncmake will not find it on the build system (which is good)17:10
RPCrofton: right, makes sense17:12
RPCrofton: I suddenly wondered if you were trying to do something else17:12
RPhalstead: do we need to wait for a while for the sstate removal to happen?17:13
seebsActually they may be adequately conditional already, because this applies only when we find a match by path.17:13
halsteadRP Just finished.17:13
Croftonbasically, I'd like a proper way of overriding ASSUME_PROVIDED for cases like this17:13
CroftonI'll test the AP_remove way17:13
CroftonI jsut want to make sure this doesn't lead to subtle breakage17:14
halsteadRP, We're ready to build again.17:14
RPhalstead: great, thanks17:14
RPhalstead: I wasn't sure of the best way to clear it, I guessed from one of the builders over NFS would be nasty17:14
RPhalstead: I've set a master-next away thanks17:15
halsteadRP, That works but takes awhile. I have sstate on it's own partition so I remake the filesystem instead.17:15
-YoctoAutoBuilder- build #61 of nightly-qa-logrotate is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
halsteadRP, And then check the NFS is happy on all the builders.17:16
seebsThere is an actual failure mode that isn't the inode thing.17:16
-YoctoAutoBuilder- build #62 of nightly-x86-64 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #61 of minnow is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #60 of nightly-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #60 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at
-YoctoAutoBuilder- build #62 of minnow-lsb is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #62 of nightly-x86-64-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #62 of nightly-world is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #61 of buildtools is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #60 of nightly-ppc-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #61 of nightly-qa-extras is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1] Build details are at
-YoctoAutoBuilder- build #61 of nightly-x32 is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1] Build details are at
-YoctoAutoBuilder- build #60 of nightly-mips-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #63 of nightly-ppc is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #60 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at
-YoctoAutoBuilder- build #61 of nightly-fsl-ppc-lsb is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #61 of nightly-oecore is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #63 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at
*** jbrianceau is now known as jbrianceau_away17:16
-YoctoAutoBuilder- build #60 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #67 of poky-tiny is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #62 of nightly-x86-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #61 of nightly-fsl-ppc is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #59 of build-appliance is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #60 of nightly-arm-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
RPhalstead: small permissions issue ;-)17:17
-YoctoAutoBuilder- build #62 of nightly-arm is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #63 of nightly-non-gpl3 is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #61 of nightly-qa-skeleton is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #62 of nightly-qa-pam is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
seebsSo if you delete a symlink or directory, and around the time you're doing this you create an executable file...17:17
RPhalstead: I've killed the builds17:17
seebsIf the DID_UNLINK for the symlink or directory comes in after the executable file is created, it can nuke the database entry for the file.17:17
RPhalstead: but I like the reformat, that is nicer17:18
RPseebs: I can see how that could be problematic17:18
*** roric <roric!> has joined #yocto17:18
halsteadRP, Permissions are fixed.17:19
RPhalstead: thanks, I'll retry17:19
* halstead carefully checked nfs state but not directory ownership. 17:19
*** Jefro <Jefro!> has joined #yocto17:19
seebsWoot. Okay, the failure case where I was getting hundreds of errors does appear fixed.17:19
RPhalstead: when I saw the failures I was fully expecting it to be my fault on the branch :)17:20
halstead:) At least that was a quick failure and recovery.17:21
seebsThere's something else I'd like to figure out but it doesn't look as significant.17:22
RPhalstead: yes, could be worse :)17:22
* RP needs to head afk17:23
*** roric <roric!> has quit IRC17:24
seebsOkay, so. Retesting a couple of things, but I think this will turn into pseudo 1.6.2, with two fixes, one of which is just for xfs.17:27
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:33
*** belen <belen!Adium@nat/intel/x-fmkmybxmytxxlvmq> has quit IRC17:37
*** jimBaxter <jimBaxter!> has quit IRC17:43
*** sarahsharp1 <sarahsharp1!~sarah@> has quit IRC17:46
*** AndersD <AndersD!> has quit IRC18:10
*** TRoGd0R <TRoGd0R!> has left #yocto18:12
seebsI lose, there's still an actual bug producing real problems.18:13
seebsNot sure what's happening, but at least I now have a patched-up pseudo that won't generate the errors I *don't* care about.18:14
seebsIt appears that rerunning "bitbake -f -c package util-linux" a couple of times produces the errors.18:14
kergothsounds like a step in the right direction, at least. make it easier to diagnose18:14
seebsThis is interesting.18:17
seebsSo, every time I get one of these, it seems to involve a no-path entry for an inode which was the inode of a previous did-unlink.18:18
*** Fivefootseven <Fivefootseven!> has joined #yocto18:28
*** Fivefootseven <Fivefootseven!> has joined #yocto18:29
*** Fivefoo__ <Fivefoo__!> has joined #yocto18:30
*** Fivefoot_ <Fivefoot_!~fivefoots@> has quit IRC18:31
*** Fivefootseven <Fivefootseven!> has quit IRC18:33
*** SorenHolm <SorenHolm!> has joined #yocto18:35
-YoctoAutoBuilder- build #62 of nightly-qa-extras is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #68 of poky-tiny is complete: Success [build successful] Build details are at
*** Fivefootseven <Fivefootseven!~fivefoots@> has joined #yocto18:37
seebs... silly question, is there a way I can point bitbake at a local git repo that isn't a git:// directory?18:40
*** ddom <ddom!~ddom@> has joined #yocto18:40
kergoththe url scheme in bitbake just controls what fetcher is used, not necessarily what the underlying protocol used to fetch is18:40
*** Fivefoo__ <Fivefoo__!> has quit IRC18:40
seebsLike, I can git clone /home/seebs/pseudo, but I can't put it in SRC_URI.18:40
kergothgit:// .... ;protocol=file will clone file:///home/seebs/pseudo18:40
kergothit might've been nice for that to be opposite. e.g. file://${HOME}/foo;fetcher=git or something, but its a bit late for that now :)18:41
kergothwhat i'd really like to see is support for schemes that combine the two, which seems to be showing up as a convention amongst upstreams18:43
kergothe.g. git+ssh for git, so <fetcher>+<underlying protocol>://18:43
* kergoth shrugs, minor cosmetic thing18:44
*** RP2 <RP2!> has joined #yocto18:45
seebsSo I can't tell whether what I have now is purely cosmetic or an actual database corruption problem.18:45
seebsBut *something* is happening that's causing diagnostics which may be harmless or may indicate a serious problem.18:46
seebsmkdir requests are complaining because they have a pathless DB entry with the same inode, which is the inode of a recently-deleted file.18:47
RP2halstead, could you check the git server logs and see if the cause of is obvious if you have a moment please?18:47
* RP2 isn't really here18:47
halsteadGladly RP2.18:49
*** smartin_ <smartin_!> has joined #yocto18:50
*** SorenHolm <SorenHolm!> has quit IRC18:54
-YoctoAutoBuilder- build #62 of buildtools is complete: Success [build successful] Build details are at
*** Fivefoot_ <Fivefoot_!> has joined #yocto19:13
*** Fivefootseven <Fivefootseven!~fivefoots@> has quit IRC19:17
*** Fivefootseven <Fivefootseven!~fivefoots@> has joined #yocto19:20
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC19:22
*** Fivefoot_ <Fivefoot_!> has quit IRC19:23
*** Jefro <Jefro!> has quit IRC19:25
*** victhor_ <victhor_!~victhor@> has joined #yocto19:26
*** SorenHolm <SorenHolm!> has joined #yocto19:28
seebsOkay, no promises, but I *think* I found the source of a whole bunch of "how did that file get into the database with no name" problems.19:30
seebsI feel really clever, because I am a pretty sharp programmer, but apparently I totally outsmarted myself.19:30
seebsWhen processing a link, I was using the existing data from the database for a given inode, and then creating a link with the new path. Sensible, right?19:31
seebsOnly. The actual link creation uses a test on msg->pathlen to determine whether to link with msg->path or the fixed string 'NAMELESS FILE'.19:31
-YoctoAutoBuilder- build #62 of nightly-x32 is complete: Success [build successful] Build details are at
seebsAnd the "existing data from the database" entry had no pathlen.19:31
seebs(There's some weirdness because 'msg' is of a type with a flexible array member on the end, so *msg = by_ino doesn't actually change msg->path.)19:32
*** marka <marka!~marka@> has quit IRC19:43
-YoctoAutoBuilder- build #62 of nightly-qa-logrotate is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #63 of minnow-lsb is complete: Success [build successful] Build details are at
*** sameo <sameo!~samuel@> has joined #yocto20:05
*** Siecje <Siecje!~Siecje@> has left #yocto20:13
*** rwoolley <rwoolley!~rwoolley@> has quit IRC20:14
*** Jefro <Jefro!~jefro@> has joined #yocto20:15
kergothHmm, not sure it's still possible to share target (but not native/cross) sstate between distros. i have target recipes being rebuilt even though bitbake-whatchagned and bitbake -S printdiff both show no differences20:17
*** sameo <sameo!~samuel@> has quit IRC20:17
* kergoth digs20:17
*** Jefro <Jefro!~jefro@> has quit IRC20:23
-YoctoAutoBuilder- build #63 of nightly-qa-pam is complete: Success [build successful] Build details are at
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto20:32
*** sameo <sameo!~samuel@> has joined #yocto20:34
*** Jefro <Jefro!~jefro@> has joined #yocto20:34
*** jluisn <jluisn!~quassel@> has quit IRC20:38
-YoctoAutoBuilder- build #61 of nightly-deb is complete: Success [build successful] Build details are at
*** g1zer0 <g1zer0!> has joined #yocto20:57
*** ant__ <ant__!> has joined #yocto20:58
FivefootsevenHi everyone, Can any explain how I install just a set of shared libraries? The recipe only outputs dev & staticdev rpms. When try and build the image I keep getting: Computing transaction...error: Can't install SuiteSparse-dev-4.3.1-r0@cortexa9hf_vfp_neon: no package provides SuiteSparse = 4.3.1-r0. Does do I create a base SuiteSparse RPM?21:03
kergothsounds like its recipe isn't installing anything in its do_install21:07
*** davisroman <davisroman!42ce7843@gateway/web/freenode/ip.> has quit IRC21:08
*** belen <belen!> has joined #yocto21:08
FivefootsevenSo the recipe inherits from autotools and so I haven't added a do_install method. Looking at the log and inspecting the created RPMs it build the libraries I need I just can't get it to build a rootfs or sdk without the above error.21:10
seebsWell, I've definitely made progress.21:13
seebsI've now established that I was wrong about what I thought was wrong with my fix for what I thought was wrong.21:13
seebsIt turns out my initial belief that the "by_ino" lookup wouldn't have the right path length was in fact incorrect.21:14
seebsSo I'm back to not being sure how the files are getting in as nameless files. But I have reversed the thing that made them MORE common.21:14
-YoctoAutoBuilder- build #61 of nightly-ipk is complete: Success [build successful] Build details are at
*** belen <belen!> has quit IRC21:18
FivefootsevenIs it a correct assumption that no SuiteSparse-4.3.1-r0@cortexa9hf_vfp_neon RPM would be created as no binary files were produced and the lib and includes files were just included into in the dev RPMs?21:20
-YoctoAutoBuilder- build #61 of nightly-rpm is complete: Success [build successful] Build details are at
*** zecke <zecke!~ich@> has quit IRC21:22
kergothFivefootseven: the dev rpm is always created, empty or not. its far more likely that nothing was installed, though that is possible, yes21:24
*** belen <belen!> has joined #yocto21:26
FivefootsevenSo you would expect not to see a base RPM if nothing was installed. As this is a shared library I assume I would expect to see the same contents in the dev and then base RPM?21:26
*** belen <belen!> has quit IRC21:33
FivefootsevenI just added a do_install and touched the file image/usr/bin/AHH.txt and included it in the FILES_${PV} variable. This then created the missing base RPM and populated the SDK without error. This is clearly not the right approach. How to force the empty creation of the base RPM. Any suggestions?21:34
*** systmkor1 <systmkor1!~systmkor@unaffiliated/systmkor> has quit IRC21:37
*** g1zer0 <g1zer0!> has quit IRC21:38
*** smartin_ <smartin_!> has quit IRC21:39
*** zecke <zecke!~ich@> has joined #yocto21:40
-YoctoAutoBuilder- build #62 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at
*** zecke <zecke!~ich@> has quit IRC21:45
-YoctoAutoBuilder- build #62 of minnow is complete: Success [build successful] Build details are at
seebsI think I found the actual underlying problems.21:57
seebsThere were two things that were conspiring to create a problem.21:57
seebsFirst, if we found something in the database by inode, but not by path, I was creating a second database entry for it in some cases, which broke future attempts to unlink it.21:57
seebsSecond, when file renames got made smarter with the MAY_UNLINK stuff... The test for whether to create a dummy database entry to be the root of a rename operation was wrong.21:58
seebsSo it would request that a link be made for a thing which was already in the database, right before renaming it, and this was causing some of the strange behaviors like link requests for already-existing files.21:58
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** RP2 <RP2!> has quit IRC22:02
*** frsc <frsc!> has quit IRC22:03
*** cbzx <cbzx!> has joined #yocto22:04
*** cbzx <cbzx!> has quit IRC22:08
*** Jefro <Jefro!~jefro@> has quit IRC22:11
*** Jefro <Jefro!~jefro@> has joined #yocto22:11
*** staylor <staylor!> has quit IRC22:11
*** Fivefootseven <Fivefootseven!~fivefoots@> has quit IRC22:13
*** sjolley <sjolley!sjolley@nat/intel/x-pggagsdjpqqumxpn> has quit IRC22:17
RPseebs: glad its making sense :)22:21
seebsFixing the links made most of the stuff I cared about go away, but I was still seeing suspicious messages.22:21
*** sjolley <sjolley!~sjolley@> has joined #yocto22:22
seebsI think the issue is that the only times when it would come up would be when a rename operation was overwriting an existing object, and that's actually a rare use case; normally people explicitly unlink before calling rename.22:23
RPhalstead: is nfs ok on the autobuilders?22:24
seebsAwesome. With the new changes, I see only one of those "hey wait that's suspicious" messages, and it's specifically the reuse of a recently-may-be-deleted inode.22:26
* RP doesn't know why the autobuilder is showing new interesting failures22:29
* JaMa|Off is seeing couple new issues from last systemd upgrade22:37
*** roric <roric!> has joined #yocto22:44
*** SorenHolm <SorenHolm!> has quit IRC22:45
RPJaMa|Off: :(22:51
seebsSent out patch for pseudo
seebsFor Sound Technical Reasons (read: "too lazy to investigate another thing right now") I wasn't able to put the tarball on the WRS server, so it's on Sent email to pidge, but I don't know who's still around this late on a Friday.22:53
seebsafk a bit, back around in a while.22:54
*** seebs <seebs!> has quit IRC22:54
*** seebs <seebs!> has joined #yocto23:01
*** nitink <nitink!~nitink@> has joined #yocto23:01
RPseebs:can you mention this to halstead, pidge is out of action for a bit :(23:02
ant__RP: hi there. It's weird, I'm seeing a very old -native failing strangely...
ant__I have to comment out COMPATIBLE_MACHINE to unbreak23:04
seebsahh, 'k23:04
seebs... Remind me of halstead's email?23:05
halsteadMhalstead along c foundation.org23:05
halsteadDarn auto correct.23:06
halsteadseebs: mhalstead@linuxfoundation.org23:07
halsteadRP looks like no23:07
halsteadRP I'll check it out.23:07
ant__RP: another way is setting COMPATIBLE_MACHINE_class-native = ""23:09
-YoctoAutoBuilder- build #63 of nightly-world is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #63 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at
*** systmkor1 <systmkor1!~systmkor@unaffiliated/systmkor> has joined #yocto23:23
*** systmkor1 <systmkor1!~systmkor@unaffiliated/systmkor> has quit IRC23:33
*** sullical_ <sullical_!~sullical@> has quit IRC23:37
*** agust <agust!> has quit IRC23:39
*** Jefro <Jefro!~jefro@> has quit IRC23:44
*** sarahsharp <sarahsharp!~sarah@> has quit IRC23:45
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC23:45
*** mranostay <mranostay!> has joined #yocto23:46
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto23:46
*** Jefro <Jefro!~jefro@> has joined #yocto23:49
*** Jefro <Jefro!~jefro@> has quit IRC23:54
halsteadRP, Major problems with the NAS are repaired. It looked like kernel issues so I installed the newest supported HWE and we're back online.23:57
*** sameo <sameo!~samuel@> has quit IRC23:58

Generated by 2.11.0 by Marius Gedminas - find it at!