| 00:01.33 | *** join/#oe phdeswer (~phdeswer@ip-80-236-210-98.dsl.scarlet.be) |
| 01:30.38 | *** join/#oe JaMa (~martin@ip-89-176-104-107.net.upcbroadband.cz) |
| 01:38.37 | *** join/#oe slapin (~slapin@slapinbuild.ihdev.net) |
| 01:40.25 | *** join/#oe n13z (~iosick@unaffiliated/n13z) |
| 01:48.43 | *** join/#oe khem` (~khem@99-57-140-30.lightspeed.sntcca.sbcglobal.net) |
| 01:58.00 | *** join/#oe kuldeepdhaka (~kuldeepdh@unaffiliated/kuldeepdhaka) |
| 02:01.02 | *** join/#oe kuldeepdhaka (~kuldeepdh@unaffiliated/kuldeepdhaka) |
| 02:58.00 | *** join/#oe slonsiki (~slonsiki@69-12-177-67.dsl.static.sonic.net) |
| 03:02.05 | *** join/#oe silviof1 (~silviof@unaffiliated/silviof) |
| 03:11.13 | *** join/#oe nerdboy (~sarnold@dsl-66-59-252-223.static.linkline.com) |
| 03:11.43 | *** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy) |
| 03:36.09 | *** join/#oe nitink1 (nitink@nat/intel/x-kfxybjzvuptwiyzc) |
| 04:31.07 | *** join/#oe phdeswer_ (~phdeswer@ip-80-236-209-102.dsl.scarlet.be) |
| 05:04.12 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 06:11.10 | *** join/#oe clio (~andrej@85.159.109.222) |
| 06:31.05 | *** join/#oe jkridner|work (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
| 06:31.15 | *** join/#oe Gaston|Home1 (~jonma@ua-83-227-239-139.cust.bredbandsbolaget.se) |
| 06:31.18 | *** join/#oe mario-go` (~user@email.parenteses.org) |
| 06:32.01 | *** join/#oe dv__ (~quassel@chello080108009040.14.11.vie.surfer.at) |
| 06:33.55 | *** join/#oe ericben (~ebenard@pac33-3-88-170-243-169.fbx.proxad.net) |
| 06:33.59 | *** join/#oe vmeson (~quassel@128.224.252.2) |
| 06:34.09 | *** join/#oe CruX| (~jozo@mcw.student.utc.sk) |
| 06:34.39 | *** join/#oe erbo (~erik@host.62.65.125.245.bitcom.se) |
| 06:37.50 | *** join/#oe Rootert_ (~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl) |
| 06:38.14 | *** join/#oe tasslehoff (~tasslehof@77.40.182.98) |
| 06:39.19 | *** join/#oe kbart (~KBart@213.197.143.19) |
| 06:45.30 | *** join/#oe Crofton (~balister@pool-71-171-41-155.ronkva.east.verizon.net) |
| 06:54.20 | *** join/#oe NightMonkey (~NightrMon@173-164-139-193-SFBA.hfc.comcastbusiness.net) |
| 06:54.20 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 07:00.24 | *** join/#oe uwe_mobile (~uwe@static.88-198-8-117.clients.your-server.de) |
| 07:04.13 | *** join/#oe g1zer0 (~gizero@host168-65-static.12-87-b.business.telecomitalia.it) |
| 07:26.34 | *** join/#oe scot (~scot@130.164.62.126) |
| 07:34.49 | *** join/#oe SorenHolm (~quassel@cpe.ge-0-2-0-950.faaqnqu1.dk.customer.tdc.net) |
| 07:37.35 | *** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029) |
| 07:40.14 | *** join/#oe diego_r (~diego@host65-246-static.10-188-b.business.telecomitalia.it) |
| 07:54.33 | *** join/#oe ChrisD1_Away (~ChrisD@merak.alcor.co.uk) |
| 07:56.10 | *** join/#oe SorenHolm (~quassel@cpe.ge-0-2-0-950.faaqnqu1.dk.customer.tdc.net) |
| 08:00.34 | *** join/#oe ant_work (~ant__@host54-128-static.10-188-b.business.telecomitalia.it) |
| 08:01.54 | *** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029) |
| 08:02.13 | *** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net) |
| 08:08.37 | mckoan | good morning |
| 08:10.51 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
| 08:20.06 | tasslehoff | trying to move from 1.4 to 1.5 today and thought I'd clean up a bit in the process. for a !X11-image with qt5-embedded support, which image would you start from? |
| 08:20.11 | tasslehoff | (morning) :) |
| 08:22.23 | woglinde | gm tasslehoff |
| 08:23.39 | tasslehoff | hi woglinde. today is "upgrade and hope musb issues go away"-day :) |
| 08:26.30 | khem` | tasslehoff: add meta-qt5 and then bitbake cinematicexperience |
| 08:27.53 | tasslehoff | khem`: cool. thanks. |
| 08:29.14 | tasslehoff | I've had DISTRO set to angstrom-* earlier, but now I want to make my image as lightweight as possible. Can I just leave it blank, perhaps? |
| 08:39.34 | mckoan | gm tasslehoff, woglinde, all |
| 08:41.19 | *** join/#oe blitz00 (~stefans@unaffiliated/blitz00) |
| 08:50.51 | *** join/#oe mihai (~mihai@80.97.15.150) |
| 08:52.11 | *** join/#oe florian_kc (~fuchs@port-217-146-132-69.static.qsc.de) |
| 08:52.11 | *** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 08:57.15 | woglinde | tasslehoff hm there should minimal flying around |
| 08:57.20 | woglinde | for distro |
| 08:57.26 | woglinde | but did not used it lately |
| 09:00.00 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 09:10.10 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 09:10.55 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
| 09:14.32 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
| 09:16.49 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 09:24.16 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 09:32.03 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 09:38.00 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 09:39.55 | *** join/#oe shoragan (~jlu@2001:6f8:1178:2:219:99ff:fe56:8d7) |
| 09:39.55 | *** join/#oe shoragan (~jlu@debian/developer/shoragan) |
| 09:46.11 | bluelightning | morning all |
| 09:46.18 | *** join/#oe ao2 (~ao2@host20-141-dynamic.6-87-r.retail.telecomitalia.it) |
| 09:50.09 | woglinde | hi bluelightning |
| 09:50.56 | bluelightning | hi woglinde |
| 09:51.50 | apelete | good morning all |
| 09:52.35 | mckoan | hi bluelightning, apelete, all |
| 09:53.06 | bluelightning | hi apelete, mckoan |
| 09:53.49 | *** join/#oe mihai (~mihai@80.97.15.150) |
| 09:57.04 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 10:01.25 | *** join/#oe fcambus (~fred@host-89-230-80-95.rzeszow.mm.pl) |
| 10:04.12 | *** join/#oe jackmitchell (~Thunderbi@cbnluk-gw0.cambridgebroadband.com) |
| 10:13.48 | pwgen | hi all. |
| 10:16.19 | bluelightning | hi pwgen |
| 10:22.35 | *** join/#oe ohama (ohama@cicolina.org) |
| 11:09.43 | *** join/#oe rsalveti (~rsalveti@unaffiliated/rsalveti) |
| 11:27.24 | *** join/#oe Vutral (ss@mirbsd/special/Vutral) |
| 11:48.44 | *** join/#oe nicolauz (nicolauz@83.133.126.252) |
| 11:58.25 | ndec | hi. what's the recommended method to ensure an image will autoload a kernel module at boot? |
| 11:59.41 | ndec | i have added "module_autoload_snd-intel8x0 = "snd-intel8x0"" in a linux-yocto .bbappend, and that doesn't seem to be doing what i thought it should.. |
| 12:01.36 | bluelightning | ndec: hmm, that should work as far as I can tell... |
| 12:01.51 | bluelightning | provided of course that you're building the kernel recipe you're bbappending |
| 12:02.18 | ndec | bluelightning: could it be possible that module_autoload vars aren't in ssate signature? i feel something weird here.. |
| 12:02.44 | bluelightning | ndec: looking at how they are read, I think that's quite likely |
| 12:03.20 | bluelightning | i.e. they aren't being read in a way that bitbake can easily determine that the dependency exists |
| 12:03.31 | ndec | so, that might be the problem... i had made a build without it, so it's probably using from sstate |
| 12:04.03 | ndec | can i dump the 'signature' content to see what's inside? |
| 12:04.12 | *** join/#oe CMoH (~cipi@78.96.95.186) |
| 12:04.13 | *** join/#oe CMoH (~cipi@unaffiliated/c-moh) |
| 12:05.36 | bluelightning | ndec: you can indeed - bitbake-dumpsig <siginfo or sigdata file> |
| 12:05.48 | ndec | yeah, right. if i change the variable content, it just does the rootFS again without rebuilding the kernel.. |
| 12:08.00 | ndec | bluelightning: so all the tracked variables are in "Task dependencies", right? |
| 12:09.33 | bluelightning | ndec: yes |
| 12:09.42 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
| 12:10.16 | ndec | ok. i guess that's a bug then ;) is that something that can be fixed, or is it like this 'by design'? i am on dora,btw. |
| 12:11.48 | ndec | also, i think these variables impact only the 'packaging', not the build. |
| 12:12.47 | bluelightning | ndec: I'd say it's a bug really |
| 12:12.59 | bluelightning | we should probably figure out a way to add the dependencies |
| 12:13.51 | ndec | in fact the variables are dynamic, they might not exist. |
| 12:15.43 | ndec | sounds like vardepvalue can help here. |
| 12:15.55 | bluelightning | yes, it's a bit tricky |
| 12:16.22 | bluelightning | I've never been particularly keen on the module_autoload syntax, so maybe we would change that at the same time, not sure |
| 12:16.34 | bluelightning | it's worth filing a bug about the general problem at any rate if you wouldn't mind |
| 12:16.44 | ndec | ok. will do that now. |
| 12:19.50 | bluelightning | thanks |
| 12:27.03 | *** join/#oe Vutral (ss@mirbsd/special/Vutral) |
| 12:27.08 | ndec | bluelightning: fyi. https://bugzilla.yoctoproject.org/show_bug.cgi?id=5786 |
| 12:32.26 | woglinde | ndec why udev do not help here? |
| 12:34.49 | ndec | woglinde: i am using busybox mdev. |
| 12:36.29 | woglinde | ah okay |
| 12:37.04 | woglinde | ndec or build in the driver |
| 12:39.07 | ndec | right.. |
| 13:31.32 | *** join/#oe afournier (~admin@46.255.181.29) |
| 13:31.36 | *** join/#oe othmar (~othmar@chello212017108125.6.11.vie.surfer.at) |
| 13:55.37 | *** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029) |
| 14:31.53 | *** join/#oe oneQubit (~oneQubit@c-98-231-154-140.hsd1.md.comcast.net) |
| 14:45.36 | *** join/#oe paulbarker (~pbarker@94-192-12-83.zone6.bethere.co.uk) |
| 15:02.21 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 15:20.11 | *** join/#oe CMoH (~cipi@78.96.95.186) |
| 15:20.12 | *** join/#oe CMoH (~cipi@unaffiliated/c-moh) |
| 15:27.30 | *** join/#oe woglinde (~henning@p5099b351.dip0.t-ipconnect.de) |
| 15:37.01 | *** join/#oe dlan (~dennis@gentoo/developer/dlan) |
| 15:38.10 | *** join/#oe CMoH (~cipi@unaffiliated/c-moh) |
| 15:55.49 | *** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk) |
| 16:05.13 | *** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk) |
| 16:10.03 | *** join/#oe dijenerate (~dijenerat@host86-146-144-253.range86-146.btcentralplus.com) |
| 16:19.43 | *** join/#oe bluelightning (~paul@83.217.123.106) |
| 16:19.43 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 16:19.58 | *** join/#oe _chase_ (~a0271661@nat/ti/x-hosptmxhmphcfirw) |
| 16:20.09 | *** join/#oe dlan (~dennis@116.228.88.131) |
| 16:20.09 | *** join/#oe dlan (~dennis@gentoo/developer/dlan) |
| 16:25.28 | *** join/#oe apelete (~apelete@176-26-190-109.dsl.ovh.fr) |
| 16:29.05 | *** join/#oe ftonello (~felipe@wsip-70-183-20-162.oc.oc.cox.net) |
| 16:33.41 | *** join/#oe apelete (~apelete@176-26-190-109.dsl.ovh.fr) |
| 16:38.00 | *** join/#oe bricke (~bricke@12.250.117.106) |
| 16:38.15 | *** join/#oe apelete_ (~apelete@176-26-190-109.dsl.ovh.fr) |
| 16:39.11 | *** join/#oe khem` (~khem@99-57-140-30.lightspeed.sntcca.sbcglobal.net) |
| 16:39.32 | mckoan | git/IMAW |
| 16:39.36 | mckoan | oops |
| 16:43.31 | *** join/#oe RP1 (~richard@212.121.127.42) |
| 16:47.31 | *** join/#oe msm (~msm@cpe-173-174-124-130.austin.res.rr.com) |
| 16:48.59 | *** join/#oe msm (~msm@cpe-173-174-124-130.austin.res.rr.com) |
| 16:51.24 | *** join/#oe dos1 (~dos@unaffiliated/dos1) |
| 16:55.12 | bluelightning | hi folks, FYI there's a public OpenEmbedded TSC/workgroup meeting in here in about 5 minutes |
| 16:55.27 | bluelightning | sorry about not announcing it earlier |
| 16:55.39 | bluelightning | all welcome |
| 16:57.51 | khem` | hello bluelightning |
| 16:57.56 | bluelightning | hi khem` |
| 16:59.45 | khem` | anyone has new topics ? |
| 17:02.04 | bluelightning | koen: are you here? |
| 17:02.09 | khem` | bluelightning: lets wait for some more minutes |
| 17:02.16 | bluelightning | sure |
| 17:02.33 | fray | is here as well... |
| 17:02.51 | Crofton|road | hmm |
| 17:02.55 | Crofton|road | shall I slap the bot |
| 17:03.04 | bluelightning | Crofton|road: if you can, please |
| 17:03.44 | *** join/#oe Crofton-bot (~supybot@pool-71-171-41-155.ronkva.east.verizon.net) |
| 17:03.59 | bluelightning | #startmeeting |
| 17:04.03 | bluelightning | !startmeeting |
| 17:04.04 | Crofton|road | generally cursing evil vendor tools atm |
| 17:04.08 | Crofton-bot | Meeting started Tue Feb 4 17:03:59 2014 UTC. The chair is bluelightning. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 17:04.09 | Crofton-bot | Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 17:04.43 | bluelightning | #chair khem` koen fray |
| 17:04.43 | Crofton-bot | Current chairs: bluelightning fray khem` koen |
| 17:04.47 | *** join/#oe Jefro (~jefro@50-0-152-82.dedicated.static.sonic.net) |
| 17:05.00 | bluelightning | hi Jefro |
| 17:05.17 | Jefro | bluelightning hi - sorry I'm late, caught up in a different meeting |
| 17:05.42 | bluelightning | Jefro: no worries, we're just waiting a bit for new topics and to see if koen is around |
| 17:07.10 | fray | bluelightning I've got a topic.. oe website.. |
| 17:07.20 | bluelightning | fray: good idea |
| 17:07.26 | fray | (just curious if any progress has gone forward on working on it, or planning the day for people to help) |
| 17:07.43 | bluelightning | I was thinking it would be worth touching on the bug fixing weekend |
| 17:07.49 | fray | ya.. |
| 17:08.01 | Crofton|road | ka6sox: and jackmitchell have fidured out they need to use email |
| 17:08.15 | khem` | is the wesite available to view on alternative url |
| 17:08.23 | khem` | of some sort |
| 17:08.39 | Crofton|road | we do ahve a staging Ip, but setup just before FOSDEM |
| 17:08.47 | bluelightning | ok, so before we dive in, who wants to chair? |
| 17:09.15 | bluelightning | I guess I can do it if nobody else wants to |
| 17:09.21 | khem` | go ahead |
| 17:09.26 | bluelightning | ok, done |
| 17:09.40 | bluelightning | so let's go straight into the oe website |
| 17:09.44 | bluelightning | #topic new OE website |
| 17:10.00 | bluelightning | do we know what the test URL is, for reference? |
| 17:10.06 | jackmitchell | yes |
| 17:10.11 | jackmitchell | http://frontpage.openembedded.com/ |
| 17:10.12 | bluelightning | aha, welcome jack ;) |
| 17:10.17 | jackmitchell | sorry |
| 17:10.20 | jackmitchell | http://frontpage.openembedded.org/ |
| 17:10.55 | jackmitchell | so I need to speak to ka6sox and get that subdomain pointing to the git repo that I pushed the new oe-site code to |
| 17:11.07 | bluelightning | ah, right, I was wondering why I was seeing a dir listing :) |
| 17:11.11 | fray | :) Ya, all I get right now is a dir listing |
| 17:11.29 | jackmitchell | but it's moving along :) |
| 17:11.35 | bluelightning | jackmitchell: thanks :) |
| 17:11.41 | fray | good to hear.. I was just worried the work got stalled waiting for something |
| 17:11.44 | khem` | jackmitchell: is website code repo hosted on git.oe.org |
| 17:11.48 | khem` | or not |
| 17:11.50 | fray | as long as it's progressing, I'm happy.. |
| 17:12.14 | Crofton|road | jackmitchell: and ka6sox have bad TZ diff and ka6sox has been traveling |
| 17:12.20 | bluelightning | khem`: I guess the repo needs to be listed in OE cgit - is that you or ka6sox? |
| 17:12.23 | jackmitchell | khem`: "openembedded-web-frontpages" on git@git.openembedded.org |
| 17:12.35 | jackmitchell | so I believe that it will need adding to cgit |
| 17:12.49 | jackmitchell | but it is on oe infrastructure |
| 17:13.14 | khem` | jackmitchell: renaming it to openembedded-website would be nice |
| 17:13.22 | khem` | I can add it to cgit |
| 17:13.41 | jackmitchell | sure, I don't care what it's named; RP created it quickly for me the other day |
| 17:14.03 | jackmitchell | I was thinking oe-site to save my fingers ;) |
| 17:14.23 | khem` | ok |
| 17:14.56 | *** join/#oe kristoffer (~kristoffe@c-45dbe555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 17:14.57 | bluelightning | ok, so I guess we're just waiting on a few things on the admin side for the moment |
| 17:15.28 | bluelightning | shall we move on? |
| 17:15.59 | woglinde | hi khem |
| 17:16.08 | fray | sounds good |
| 17:16.12 | bluelightning | #topic bug fixing weekend |
| 17:16.30 | bluelightning | so tlwoerner kindly sent out the announcement |
| 17:17.12 | bluelightning | I know some bug fixes were sent, but honestly I couldn't tell that there was any higher level of activity from Friday to Monday on bugfixes |
| 17:17.25 | fray | I was online the whole time, but got sucked into work stuff instead.. :( |
| 17:17.32 | bluelightning | it could have just been the short notice I guess |
| 17:17.32 | fray | I agree, unfortunately I didn't see additional activity |
| 17:17.47 | Crofton|road | I would suggest doing a one day thing |
| 17:17.47 | khem` | where is bug list tracked |
| 17:17.54 | Crofton|road | to get everyone focused at the same time |
| 17:17.58 | bluelightning | also I think maybe people weren't sure where to dive in |
| 17:18.10 | fray | I didn't see anyone ask though.. :( |
| 17:18.15 | bluelightning | no... |
| 17:18.21 | bluelightning | khem`: well, bugzilla.yoctoproject.org nominally |
| 17:18.32 | fray | I'm hoping it was just teh short notice.. and we can try to do this again.. |
| 17:18.36 | bluelightning | perhaps constructing a query or two would help |
| 17:18.44 | bluelightning | yes I think the idea is still a good one |
| 17:19.11 | Jefro | out of curiosity, where was this announced? I see the announcement for Jan 17-20 but not for this past weekend. |
| 17:19.25 | fray | ya.. it was the 17-20 I'm referring to |
| 17:19.32 | bluelightning | I think we need to get the message out that it's not just janitor bugs, people can potentially pick up any bug that's in NEW status |
| 17:19.51 | bluelightning | Jefro: right, we're talking about the earlier announced weekend |
| 17:20.06 | Jefro | ok |
| 17:20.34 | khem` | I see ok |
| 17:21.09 | khem` | other layers than OE-Core will miss out ? |
| 17:22.10 | bluelightning | khem`: well, people are of course free to work on whatever they wish, but we know we have problems with the rising bug count relating to OE-Core |
| 17:22.25 | khem` | sure, yes |
| 17:22.28 | bluelightning | so the main aim is to try to address that |
| 17:22.58 | fray | the bugzilla was simply to get people started.. but meta-oe would be encouraged as well as bitbake or any other layers |
| 17:23.27 | kergoth | I think the lack of notice was a definite factor, I know that's why I didn't find the time to do much |
| 17:23.33 | Crofton|road | part of the goal is to engage people and help them work trhough bugs |
| 17:24.11 | fray | yup.. thats why i was online, even thought I couldn't help |
| 17:24.26 | bluelightning | ok, so would it make sense to choose a date for the next one and announce it? |
| 17:24.39 | khem` | may be we should annouce next one |
| 17:25.06 | fray | same weekend? Fri 14, Sat 15, Sun 16, Mon 17 |
| 17:25.13 | fray | (17th is a holiday for some in the US) |
| 17:25.29 | fray | the weekend after that could be good as well.. |
| 17:25.35 | fray | 21, 22, 23 |
| 17:25.39 | khem` | may be have it fixed to say last week of a month |
| 17:25.43 | khem` | or bimonthly |
| 17:25.45 | khem` | whatever |
| 17:26.03 | fray | Ya.. I'm fine with last weekend of the month (just have to define that) ;) |
| 17:26.06 | bluelightning | well 14th is valentine's day, so that might not be the best choice ;) |
| 17:26.15 | fray | Ohh crap.. ya, I forgot about that |
| 17:26.15 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 17:26.56 | bluelightning | last weekend of the month kind of works, although that means the actual date will move a bit |
| 17:27.10 | khem` | yeah |
| 17:27.11 | fray | yup.. |
| 17:27.18 | khem` | announcements should still be made |
| 17:27.27 | fray | the advantage is the following week is when we have this meeting |
| 17:27.43 | bluelightning | khem`: well naturally if we've settled on a date ;) |
| 17:28.12 | fray | I'd say then.. last 'full' weekend of the month.. (i.e. all of the dates are in that month) |
| 17:28.18 | khem` | fray has a good point, where we can review them in this meeting a week later |
| 17:28.30 | bluelightning | fray: ok, so that would be 21-24th |
| 17:28.34 | bluelightning | this month that is |
| 17:28.36 | fray | the most we'll be off w/ the last full weekend is two weeks vs one.. |
| 17:28.38 | fray | yup |
| 17:29.34 | *** join/#oe JoFo (~Jean-Fran@85.234.199.20) |
| 17:29.37 | bluelightning | ok, so can someone do the announcement? |
| 17:30.03 | bluelightning | I don't want to volunteer tlwoerner unless he doesn't mind ;) |
| 17:30.26 | bluelightning | someone else perhaps? |
| 17:30.34 | khem` | I can do that |
| 17:30.54 | bluelightning | khem`: ok, thanks |
| 17:31.14 | bluelightning | do we need to prepare a wiki page / bugzilla queries ahead of that? |
| 17:31.25 | bluelightning | (I think we probably should) |
| 17:31.28 | khem` | bluelightning: yes that would be very nice |
| 17:31.36 | bluelightning | ok I can do that |
| 17:31.37 | khem` | so we can include that in annoucement |
| 17:31.40 | khem` | cool |
| 17:32.05 | khem` | so folks can assign the bugs to themselves on ones they intend to work |
| 17:32.11 | bluelightning | #action paul to produce wiki page / bugzilla queries for bug weekend and send to khem |
| 17:32.32 | bluelightning | #action khem to send out bug weekend announcement once info available |
| 17:32.40 | bluelightning | ok, great |
| 17:33.01 | bluelightning | so I think that brings us to the end of suggested topics |
| 17:33.25 | bluelightning | anything else people would like to discuss? |
| 17:34.18 | khem` | I have a general information that eglibc will cease to maintain its head as all merges has happened |
| 17:34.25 | *** join/#oe apelete (~apelete@176-26-190-109.dsl.ovh.fr) |
| 17:34.27 | bluelightning | #topic eglibc |
| 17:34.30 | khem` | we will have to plan the move to use glibc |
| 17:34.35 | khem` | in 1.7 time frame |
| 17:34.45 | bluelightning | ok, so will there be any loss of functionality? |
| 17:35.07 | khem` | not thus far |
| 17:35.14 | *** join/#oe mr_science (~sarnold@net-cf9a4e93.cst.impulse.net) |
| 17:35.15 | *** join/#oe mr_science (~sarnold@gentoo/developer/nerdboy) |
| 17:35.17 | bluelightning | ok, that's great |
| 17:35.20 | fray | if we decide to keep the functionality, we will need the 'configuration' stuff ported.. |
| 17:35.21 | khem` | however distro maintainers should bring their patches |
| 17:35.23 | fray | or was that merged? |
| 17:35.35 | khem` | no its not merged yet |
| 17:35.39 | fray | for us that would be the distro flags 'libc-...' |
| 17:35.50 | bluelightning | khem`: good point... we probably need to send an announcement about that too |
| 17:36.12 | bluelightning | fray: khem`: right, that was kind of what I was asking about |
| 17:36.29 | fray | AFAIK, that is the only piece that (last I heard) likely won't go into glibc proper.. |
| 17:36.33 | bluelightning | so what do we do about that? |
| 17:36.39 | fray | which means we'll have to maintain it ourselves -if- we feel it necessary.. |
| 17:36.48 | bluelightning | I know we've been over it a lot, but I thought the plan was to try to get it in upstream |
| 17:36.51 | fray | it's not used a lot, but I did have a question or two on it the other day.. |
| 17:37.03 | bluelightning | poky-tiny relies upon it as noted before |
| 17:37.08 | khem` | its about maintenance if we maintain it upstream it should be acceptable |
| 17:37.13 | fray | bluelightning correct.. but it needs a maintainer.. and I havn't heard of anyoen stepping up |
| 17:37.28 | bluelightning | fray: I thought khem` did unless I misunderstood |
| 17:37.32 | khem` | I had plans to propose to glibc |
| 17:37.44 | khem` | just need to bring glibc git recipes to OE firs t |
| 17:38.01 | fray | ok |
| 17:39.04 | bluelightning | alright... so what I'd propose is to start a thread on the OE-core mailing list just letting people know that we're starting along this path, the issue with the configurability and what the implications are for distro maintainers who have eglibc customisations |
| 17:39.23 | khem` | yes, that makes sense |
| 17:39.34 | khem` | I was planning on something on these lines |
| 17:39.46 | bluelightning | khem`: ok, I hate to load you up with another task but you're probably the best person to do that ;) |
| 17:39.59 | khem` | this one is ok |
| 17:40.03 | bluelightning | #action khem start eglibc -> glibc thread on OE-Core list |
| 17:40.24 | bluelightning | ok.. anything else on that? |
| 17:40.36 | bluelightning | I have another topic if not |
| 17:41.08 | khem` | I think we are done |
| 17:41.10 | bluelightning | ok |
| 17:41.12 | bluelightning | #topic layer index |
| 17:41.39 | bluelightning | so the layer index is still broken unfortunately, due to the previously mentioned problem with the python version installed on the machine hosting it |
| 17:41.49 | bluelightning | halstead is still working on bringing up a new machine |
| 17:41.58 | fray | d'oh |
| 17:42.03 | bluelightning | for now that means that updates aren't happening |
| 17:42.47 | *** join/#oe hbeck (~hbeck@69.41.94.157) |
| 17:42.49 | halstead | Sorry about that. |
| 17:42.55 | bluelightning | halstead: no worries |
| 17:43.16 | bluelightning | we did the breakage ultimately ;) |
| 17:43.36 | bluelightning | i.e. in the metadata, by depending on new bitbake features |
| 17:43.53 | bluelightning | anyway just a heads up for folks |
| 17:44.12 | bluelightning | we can still take new layer submissions and other things that are just edits to the database |
| 17:44.41 | bluelightning | another general reminder - if you have a layer not in the index and you would like people to know about it, please submit it |
| 17:44.53 | bluelightning | at http://layers.openembedded.org |
| 17:45.25 | bluelightning | there are still loads of unindexed layers on github, with more being added on a regular basis |
| 17:45.32 | bluelightning | </soapbox> |
| 17:45.44 | *** join/#oe Daemon405 (~who_knows@cpc50-newt31-2-0-cust38.19-3.cable.virginm.net) |
| 17:46.11 | khem` | bluelightning: curious how does it depend on python |
| 17:46.53 | *** join/#oe Jay7x (jay@176.15.149.233) |
| 17:47.02 | bluelightning | khem`: it the update script makes use of bitbake to parse recipes, and bitbake depends on python 2.7 now |
| 17:47.06 | *** join/#oe abelloni (~piout@128-79-216-6.hfc.dyn.abo.bbox.fr) |
| 17:47.18 | *** join/#oe tobiash (~quassel@mail.bmw-carit.de) |
| 17:47.59 | *** join/#oe khem (~khem@99-57-140-30.lightspeed.sntcca.sbcglobal.net) |
| 17:48.05 | *** join/#oe jamestunnicliffe (~quassel@cpc14-oxfd20-2-0-cust80.4-3.cable.virginm.net) |
| 17:48.05 | *** join/#oe jamestunnicliffe (~quassel@linaro/jamestunnicliffe) |
| 17:48.36 | bluelightning | ok so I guess that's enough on that topic |
| 17:48.37 | khem` | I see |
| 17:48.41 | *** join/#oe mckoan|away (~marco@host56-7-static.30-87-b.business.telecomitalia.it) |
| 17:49.00 | *** join/#oe amaury_d (~pi@79.246.97.84.rev.sfr.net) |
| 17:49.05 | bluelightning | let's quickly talk about OE-Core statis |
| 17:49.10 | bluelightning | #topic OE-Core status |
| 17:49.22 | bluelightning | so Richard isn't here to talk about this, so this won't be complete |
| 17:49.27 | khem` | btw. I was also wondering if we could have a file index |
| 17:49.29 | fray | RP had mentioned to me some concerns about 'green' builds.. |
| 17:49.40 | fray | but my experience has been really good recently.. what I've been using from master has worked |
| 17:50.02 | bluelightning | he's been trying to get things under control, both with respect to build failures on the Yocto Project autobuilder and outstanding patches on the mailing list |
| 17:50.27 | bluelightning | a bunch of failures have been fixed, I believe we're in reasonable shape at the moment |
| 17:50.31 | khem` | how can we help ? |
| 17:51.02 | bluelightning | khem`: I'm sure RP would have something useful to say at this point |
| 17:51.09 | *** join/#oe NightMonkey (~NightrMon@173-164-139-193-SFBA.hfc.comcastbusiness.net) |
| 17:51.10 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 17:51.19 | bluelightning | khem`: probably, test your patches as much as possible ;) |
| 17:51.59 | bluelightning | it's probably worth mentioning since it has been discussed at a number of previous meetings that the python 3 patchset from khem` has been merged into master now |
| 17:52.32 | bluelightning | (so, to explain, that gives us support for building python 3 itself, not building on top of a host that uses python 3) |
| 17:52.52 | *** join/#oe XorA (~XorA@www.xora.org.uk) |
| 17:53.18 | khem` | may be autobuilders should send emails to mailing list on failures |
| 17:53.22 | khem` | claps |
| 17:53.54 | *** join/#oe Crofton-bot` (~supybot@pool-71-171-41-155.ronkva.east.verizon.net) |
| 17:53.58 | tlwoerner | just notices the already-in-progress meeting :-( |
| 17:54.04 | bluelightning | khem`: the yocto project one does, to https://lists.yoctoproject.org/listinfo/yocto-builds |
| 17:54.26 | bluelightning | although it also sends success messages there (which I filter out to a separate folder, myself) |
| 17:54.37 | bluelightning | tlwoerner: sorry for the lack of notice |
| 17:54.49 | khem` | additionally now we have angstrom regressing on jenkins daily |
| 17:54.52 | khem` | for 5 different machines |
| 17:54.52 | khem` | right now its post-commit |
| 17:54.59 | khem` | eventually, I would like to turn into pre-commit |
| 17:55.01 | khem` | that should help too |
| 17:55.07 | bluelightning | khem`: nice... can that be viewed somewhere? |
| 17:55.08 | tlwoerner | bluelightning: no problem, is there a regular schedule? |
| 17:55.23 | bluelightning | tlwoerner: first tuesday of the month I think |
| 17:55.32 | tlwoerner | bluelightning: okay, thanks |
| 17:55.47 | bluelightning | khem`: fray: is that right? |
| 17:55.51 | khem` | bluelightning: the jenkins is under some firewall ka6sox would know more |
| 17:56.04 | fray | bluelightning yes.. |
| 17:56.09 | bluelightning | ok great |
| 17:56.14 | khem` | but if that can not be opened I plan to send emails to relevant mailing thread |
| 17:56.17 | Jefro | yes, first tuesday of each month |
| 17:56.21 | bluelightning | khem`: that would be nice |
| 17:56.58 | khem` | I am working with ka6sox to make sure if its ok to get it viewable |
| 17:57.07 | khem` | but there might be spam concerns |
| 17:57.22 | bluelightning | ok, I've not dealt with jenkins at all myself |
| 17:57.41 | khem` | just another autobuilder |
| 17:57.43 | khem` | :) |
| 17:57.43 | bluelightning | so we have 3 mins left, anything final to talk about? |
| 17:58.05 | tlwoerner | is there any interest in moving to a standard MAINTAINERS system? |
| 17:58.15 | bluelightning | #topic MAINTAINERS files |
| 17:58.20 | khem` | tlwoerner: I saw your patch |
| 17:58.26 | bluelightning | as did I |
| 17:58.27 | fray | I think we should get RPs opinion on that... |
| 17:58.43 | tlwoerner | i've got a roughly 4000 line MAINTAINERS file almost ready for openembedded-core |
| 17:58.45 | khem` | it looks good but since we have a bit different process |
| 17:59.00 | bluelightning | it's a nice idea; personally I find the file's syntax a bit cryptic myself, but it is kind of standard w.r.t the kernel |
| 17:59.01 | tlwoerner | mostly generated from the automated package email |
| 17:59.02 | fray | I like maintainer files myself.. but there is some concern that it may be viewed as a 'rigid' "this person must OK it".. |
| 17:59.14 | khem` | tlwoerner: it has to provide relevant info |
| 17:59.49 | khem` | fray: atleast, CCing people can get their attention |
| 17:59.54 | bluelightning | tlwoerner: as you may be aware we've been tracking OE-Core per-recipe maintainership using a different file in meta-yocto |
| 17:59.56 | khem` | it can help with that |
| 18:00.22 | bluelightning | most other layers don't split things out to that level |
| 18:00.23 | *** join/#oe darkschneider (~gab@93-32-41-18.ip31.fastwebnet.it) |
| 18:00.33 | *** join/#oe soltys (soltys@soltys.info) |
| 18:00.36 | bluelightning | but I know some do have at least some subdivision of maintainership |
| 18:00.47 | khem` | bluelightning: I think what would be good is that patches can get right folks in CC list |
| 18:00.55 | khem` | when creating pull requests |
| 18:01.05 | khem` | it could use that MAINTAINERS info |
| 18:01.12 | khem` | or last commit whatever |
| 18:01.12 | *** join/#oe ensc|w (~ensc@fedora/ensc) |
| 18:01.13 | fray | khem, yes |
| 18:01.15 | *** join/#oe Daemon404 (~who_knows@pdpc/supporter/student/Daemon404) |
| 18:01.17 | khem` | but that I see value |
| 18:01.48 | khem` | oh well we are overtime |
| 18:01.51 | fray | I do see value in the CC... but there needs to be some way to be clear that lack of a response won't prevent the flexibility from the patch going in.. |
| 18:01.55 | tlwoerner | i basically took the monthly (?) email that comes around "[yocto] Warning! Some failures happened on pkg-report system!" and wrote some scripts to parse out the relevant information |
| 18:02.21 | bluelightning | FYI for reference the Yocto Project tracks OE-Core per-recipe maintainership in meta-yocto/conf/distro/include/maintainers.inc |
| 18:02.39 | tlwoerner | and put that into a MAINTAINERS file i'm preparing |
| 18:02.50 | tlwoerner | bluelightning: thanks :-) i was looking for that |
| 18:02.56 | bluelightning | that maintainers.inc is what feeds into the system that produces the emails |
| 18:03.30 | bluelightning | I've talked to Saul about potentially moving to a database for that |
| 18:03.34 | tlwoerner | the MAINTAINERS syntax certainly allows for per-file ownership |
| 18:03.52 | bluelightning | we could keep it in a MAINTAINERS file instead if that was more helpful to people |
| 18:03.55 | *** join/#oe Jefro1 (~jefro@50-0-152-82.dedicated.static.sonic.net) |
| 18:04.08 | bluelightning | yeah we're over time now |
| 18:04.12 | bluelightning | #endmeeting |
| 18:04.12 | Crofton-bot` | Meeting ended Tue Feb 4 18:04:12 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 18:04.12 | Crofton-bot` | Minutes: oe/2014/oe.2014-02-04-17.03.html |
| 18:04.12 | Crofton-bot` | Minutes (text): oe/2014/oe.2014-02-04-17.03.txt |
| 18:04.12 | Crofton-bot` | Log: oe/2014/oe.2014-02-04-17.03.log.html |
| 18:04.18 | bluelightning | thanks everyone! |
| 18:04.26 | khem` | thanks all |
| 18:04.36 | tlwoerner | bluelightning: what i like about a MAINTAINERS file is it is standardized and can work with the get_maintainer.pl script to generate a list of CC's for git-email |
| 18:05.05 | khem` | bluelightning: have you see this http://www.electric-cloud.com/blog/2013/05/10/yoctoopenembedded-bitbake-build-visualization/ |
| 18:05.06 | tlwoerner | and you can just adjust your ~/.gitconfig to automatically run get_maintainer.pl when you invoke "git email" |
| 18:05.33 | Jefro1 | The file itself can be a net positive as long as it doesn't introduce blockers. I have seen it work well, and I have seen it work terribly. |
| 18:05.43 | bluelightning | tlwoerner: ah, interesting, I didn't know that |
| 18:06.05 | tlwoerner | and "get_maintainer.pl" is smart enough to also use git history to look for people who have made relevant changes to the code adjusted by a patch |
| 18:06.10 | khem` | yep its the kernel version isnt it ? |
| 18:06.54 | tlwoerner | so even if there is no MAINTAINERS file, it can still make decent suggestions of people to CC |
| 18:08.25 | khem` | who is maintaining meta-mono |
| 18:08.35 | khem` | I have sent patches few months ago |
| 18:09.22 | Jefro1 | tlwoerner that part does sound very useful - the benefit of the file without the policy restrictions |
| 18:11.57 | tlwoerner | Jefro1: that's an interesting point. i guess i've been lucky, i've only ever seen a MAINTAINERS file used to generate CC suggestions for patches |
| 18:12.07 | tlwoerner | Jefro1: i guess it all depends on how it's policed |
| 18:13.15 | Jefro1 | tlwoerner exactly so. The existence of the file itself implies a hierarchy that is different from the way OE works, which is why I am a little bit concerned |
| 18:13.43 | Jefro1 | Cc suggestions and identifying responsible people is a great use for that information |
| 18:15.52 | tlwoerner | Jefro1: okay, i see your concern. what is the OE hierarchy? i'm unclear how it differs from other projects |
| 18:17.30 | Jefro1 | tlwoerner The linux kernel, for example, has a pretty strict hierarchy that Linus maintains. Unless you are part of the inner circle it is somewhat difficult to talk to maintainers - a necessity with such a large, distributed project, otherwise Linus would spend all day talking with people instead of reviewing code. |
| 18:17.57 | tlwoerner | the whole "lieutenant" thing |
| 18:18.03 | Jefro1 | OE is much more open, and the maintainer structure is looser. We don't have a big spider at the middle of the web :) |
| 18:18.24 | Jefro1 | nor will OE need one for many years yet, I hope |
| 18:18.56 | tlwoerner | but there are a select few with commit authority |
| 18:19.18 | Jefro1 | true, out of necessity |
| 18:19.34 | Jefro1 | but many people review patches |
| 18:20.11 | bluelightning | khem`: FYI, Alex Lennon is taking over meta-mono maintainership, but he hasn't had time to submit his patches |
| 18:20.23 | bluelightning | khem`: did you already post yours? |
| 18:20.37 | bluelightning | khem`: do you have patchwork links? |
| 18:20.56 | tlwoerner | Jefro1: okay, i see. on the one hand it would be good to alert people of patches to things they have worked on since they're in a better position to comment |
| 18:21.15 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 18:21.34 | tlwoerner | Jefro1: but on the other hand, this file suggests there are lieutenants |
| 18:22.21 | Jefro1 | yes, exactly so |
| 18:22.41 | Jefro1 | I can see a lot of value as well in giving credit to people who have worked on patches, for recognition |
| 18:23.50 | Jefro1 | Maybe instead of MAINTAINERS it could be called PARTICIPANTS or EXPERTS or something like that |
| 18:24.30 | tlwoerner | sure, that would be an easy change. although MAINTAINERS is standard (to some degree) |
| 18:24.57 | bluelightning | Jefro1: MAINTAINERS is the standard name for that |
| 18:25.11 | bluelightning | I think at this point RP needs to weigh in, so we should give him the opportunity to do that |
| 18:25.32 | Jefro1 | I understand that it is standard - in fact, that is part of the issue, as standards have implications that aren't necessarily true here. Agreed that RP will need to weigh in. |
| 18:25.38 | khem` | bluelightning: they were posted long time aho |
| 18:26.07 | khem` | bluelightning: https://lists.yoctoproject.org/pipermail/yocto/2013-November/016983.html |
| 18:26.22 | khem` | https://lists.yoctoproject.org/pipermail/yocto/2013-November/016982.html |
| 18:28.20 | bluelightning | khem`: they don't show up in patchwork :/ |
| 18:28.35 | khem` | since they were sent to yp ml they were not groked by pw |
| 18:28.43 | bluelightning | oh, silly me |
| 18:28.44 | bluelightning | of course |
| 18:29.36 | bluelightning | khem`: unfortunately that means if Alex doesn't have those in his mail client it's rather difficult for him to apply them |
| 18:29.53 | bluelightning | khem`: could you please re-send with him on CC ? |
| 18:29.57 | khem` | ok |
| 18:30.25 | bluelightning | khem`: he's listed as the maintainer in the layer index entry for meta-mono FYI, in case you need his address |
| 18:30.58 | tlwoerner | in any case, we don't need an actual MAINTAINERS file for the script i submitted to work, it can work by using "git history" alone, but it is much slower and would miss people who are the maintainers of certain areas |
| 18:32.16 | *** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se) |
| 18:33.04 | *** join/#oe lumag_ (~lumag@pppoe.178-66-16-242.dynamic.avangarddsl.ru) |
| 18:47.36 | pb_ | evening all |
| 18:47.50 | bluelightning | hi pb_ |
| 18:47.57 | pb_ | hi bluelightning |
| 18:51.15 | *** join/#oe onoffon (~khem@66.129.239.13) |
| 18:54.13 | *** join/#oe nitink (~nitink@134.134.137.73) |
| 19:11.21 | *** join/#oe zerus (~powerpm@81-229-90-163-no67.tbcn.telia.com) |
| 19:13.22 | *** join/#oe pvanhoof (~philip@62.205.76.11) |
| 19:18.32 | *** join/#oe rob_w (~rob@unaffiliated/rob-w/x-1112029) |
| 19:21.03 | *** join/#oe galak_pb (~galak@99-51-185-173.lightspeed.austtx.sbcglobal.net) |
| 19:25.52 | *** join/#oe joel_ (~joel@cpe-192-136-210-250.tx.res.rr.com) |
| 20:05.43 | *** join/#oe W1N9Zr0 (~W1N9Zr0@24-246-63-23.cable.teksavvy.com) |
| 20:08.36 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
| 20:11.20 | *** join/#oe kscherer (~kscherer@128.224.252.2) |
| 20:21.25 | *** join/#oe JoFo (~Jean-Fran@host-213-213-229-139.brutele.be) |
| 20:27.10 | ndec | hi JaMa, are you aware of anyone who might have started to look at building qtwebengine? |
| 20:54.42 | JaMa | ndec: hi, I don't know about anyone actually working on it, but I guess morphis would be interested |
| 20:55.35 | ndec | ok. i has chromium has a submodule in the git tree. i don't think we have a similar case in qt5 already, right? |
| 20:57.26 | JaMa | all I've seen about it that there are some plans for it in 5.3 |
| 20:57.31 | morphis | ndec: I talked with one of the authors of it recently |
| 20:57.36 | morphis | he said it's not yet ready for arm |
| 20:57.55 | morphis | they need another month to get it into a good shape and really working on arm |
| 20:58.00 | ndec | morphis: do you know what 'not ready for arm' means? |
| 20:58.21 | morphis | ndec: that was the part where I was running out of time to go any further in the discussion :) |
| 20:58.41 | morphis | ndec: but having a look into how building it would be a good start right now |
| 20:59.00 | ndec | that was the interesting part that you missed ;-) |
| 20:59.04 | morphis | as from what I saw they are using some qmake-combination-with-gyp stuff |
| 20:59.09 | morphis | ndec: yeah sadly |
| 20:59.21 | morphis | ndec: but feel free to join #qtwebengine and ask on your own :) |
| 20:59.23 | ndec | yes, + git + submodule with a custom 'repo init' script |
| 21:11.06 | ndec | JaMa: another one... what's missing to get -c populate_sdk to work with qt5 (e.g. add qmake and tools in the SDK). |
| 21:15.33 | JaMa | ndec: I don't use SDK or follow it very closely |
| 21:16.08 | JaMa | I was a bit surprised to see http://patchwork.openembedded.org/patch/66277/ again, because I think we shouldn't need it now |
| 21:17.40 | *** join/#oe lumag_ (~lumag@pppoe.178-66-65-246.dynamic.avangarddsl.ru) |
| 21:21.10 | ndec | JaMa: i don't get that either |
| 21:23.51 | *** join/#oe JoFo (~Jean-Fran@host-213-213-229-139.brutele.be) |
| 21:31.45 | mr_science | okay, i have another oe-classic question |
| 21:32.39 | mr_science | the kernel uevent helper (used to be /sbin/hotplug on gentoo) has been gone for a while now |
| 21:33.12 | mr_science | but i have 2.6.37psp and udev 1.4 in our oe-classic build |
| 21:33.45 | mr_science | sorry, udev-141 |
| 21:34.35 | mr_science | so my question is, should we be using one of the oe hotplug recipes? if so, which one? |
| 21:36.19 | mr_science | looks like the only one installed in the runtime is mdev |
| 21:40.06 | *** join/#oe woglinde (~henning@g225072008.adsl.alicedsl.de) |
| 21:42.34 | *** join/#oe zenlinux (zenlinux@2600:3c00::f03c:91ff:fedb:c91) |
| 21:46.02 | *** join/#oe zenlinux (zenlinux@2600:3c00::f03c:91ff:fedb:c91) |
| 21:48.51 | *** join/#oe zenlinux (zenlinux@2600:3c00::f03c:91ff:fedb:c91) |
| 22:16.15 | JaMa | ndec: thanks for confirmation, I've replied on the patch now |
| 22:25.34 | kroon | ndec, what are you missing from -c populate_sdk ? |
| 22:25.44 | ndec | qmake |
| 22:26.31 | kroon | ah I see |
| 22:27.05 | ndec | maybe i didn't test properly.. have you tried that? |
| 22:27.09 | kroon | i use autotools.. |
| 22:27.19 | ndec | for qt applications? |
| 22:27.31 | kroon | i dint have any qmake in the sdk at least |
| 22:27.37 | kroon | yeah |
| 22:27.50 | ndec | ok. it's in the nativesdk package if you build it. |
| 22:28.26 | ndec | but i am not familiar enough with populate_sdk. i would expect it should include qmake (e.g. nativesdk-qtbase) if qtbase is in the image.. but i am not sure about that. |
| 22:28.38 | kroon | ah |
| 22:29.03 | ndec | to me that was the definition of populate sdk... but the more i think about it, the more i believe that is not correct. |
| 22:29.32 | kroon | maybe you just need to add it to TOOLCHAIN_HOST_TASK ? |
| 22:30.17 | kergoth | populate_sdk just installs the same packages into the sdk as go into the image the task is run against, with a couple specific exceptions, no? |
| 22:31.14 | ndec | i thought populate sdk would generate an SDK that can be used to compile any application against <image>. so if <image> has qt5 i was under the impression the SDK would have the qt tools. |
| 22:31.44 | woglinde | I thought qt5 stuff is not finished yet |
| 22:32.26 | *** join/#oe pvanhoof (~philip@d54C3A074.access.telenet.be) |
| 22:32.32 | ndec | well, some support for nativesdk recipes has landed. |
| 22:32.54 | ndec | i just can't relate nativesdk-xxx recipes with populate_sdk task. |
| 22:33.36 | ndec | maybe i should go back and build a qt4 image with populate_sdk to see what happens there. |
| 22:35.47 | woglinde | yes |
| 22:35.53 | woglinde | that I tought too |
| 22:36.07 | woglinde | but than I thought there is a reason you need qt5 |
| 22:36.14 | woglinde | and did not mention it |
| 22:36.44 | ndec | sure, i need qt5.. but building an image with qt4 would tell if what to expect from the SDK1 |
| 22:37.08 | ndec | who needs qt4, now ;-) |
| 22:37.20 | mr_science | no thoughts on kernel uevent helper? |
| 22:37.37 | woglinde | mr_science wrong channel? |
| 22:38.04 | mr_science | i was asking about kernel config and oe recipe support for hotplug |
| 22:38.15 | mr_science | is there a better channel? |
| 22:38.18 | RP1 | It would be nice if nativesdk could figure out the qt tools were needed for a qt image. I think right now that is manual though |
| 22:39.09 | mr_science | if that's too tough, i have a WD usb drive that doesn't spin up right when plugged into my OE ti machine |
| 22:39.28 | mr_science | anybody remember the workaround for that one? |
| 22:41.44 | ndec | RP1: hmm. maybe that's because i don't have qttools in my image, that they i don't get them in the SDK? |
| 22:44.50 | RP1 | ndec: no, there simply is no magic mapping |
| 22:45.14 | ndec | what's the magic mapping? does that exist in qt4? i don't seem to see it. |
| 22:45.22 | *** join/#oe dos1 (~dos@unaffiliated/dos1) |
| 22:45.28 | RP1 | ndec: we could certainly add some logic to make this work, its just that it doesn't exist |
| 22:45.36 | RP1 | there is no magic for qt4 either afaik |
| 22:46.15 | ndec | so, it is the normal current behaviour that -c populate_sdk <image> on an <image> with qt4/5 does not produce a 'valid' SDK. |
| 22:46.32 | mr_science | woglinde: the whole question is moot on current x86 and has been for a while (the uevent thing) |
| 22:47.58 | RP1 | ndec: you have to manually hint to get a valid "SDK" |
| 22:48.13 | ndec | ok, i need a dedicate image, then. thanks. |
| 22:48.37 | RP1 | ndec: I'd love to see it work better, its just not something someone has sat down and made work |
| 22:49.11 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 22:50.28 | ndec | RP1: so the idea would be to provide a mechanism for any recipe to 'add extra stuff' when building SDK (e.g. when task is populate_sdk) |
| 22:53.00 | kroon | ndec, in my image recipe I have added "TOOLCHAIN_HOST_TASK += nativesdk-qtbase-tools". Thats gets "moc" in the SDK, but not in the target image I *think*, havent actually checked that now that I think of it |
| 22:53.36 | kroon | but yeah, some logic for automatically adding sdk packages would be nice |
| 22:53.43 | ndec | kroon: ok. i don't know about TOOLCHAIN_HOST_TASK, i will check that |
| 22:54.08 | RP1 | right, you just add the tools you need to the list |
| 22:54.11 | ndec | well, it can't really be 'automatic'. it has to come from the recipe that knows what's needed. |
| 22:54.22 | RP1 | the question is how to automatically 'know' that needs to be added |
| 22:54.41 | RP1 | adding such things in the image recipe might be the best way |
| 22:54.56 | *** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk) |
| 22:55.07 | ndec | hmm. it should be in the component recipe that 'creates' the dependency, no? |
| 22:55.29 | ndec | in this case in qtbase, i guess. |
| 22:55.52 | ndec | to indicate that whenever qtbase is in <image> , an SDK based on <image> will need these tools. |
| 22:57.10 | ndec | well, of course.. it cannot work this way.. what's in the component recipe won't be 'seen' when building the image. |
| 22:59.11 | *** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk) |
| 23:00.57 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 23:04.49 | ndec | kroon: right, so at least adding TOOLCHAIN_HOST_TASK didn't 'touch' my normal image, i am not building the SDK.. that will take some time |
| 23:04.53 | kroon | SDKDEPENDS ? |
| 23:06.32 | ndec | yeah ;-) |
| 23:07.16 | kroon | or SDK_DEPENDS.. which seems to already exist.. |
| 23:07.30 | ndec | but that needs to be stored in the package, then. |
| 23:08.25 | ndec | SDK_DEPENDS doesn't seem to be doing that, though. |
| 23:08.37 | ndec | it's more about what's needed when starting a SDK build. |
| 23:08.45 | ndec | SDKRDEPENDS, maybe |
| 23:09.02 | kroon | aha |
| 23:10.30 | ndec | in fact SDKRDEPENDS is really more appropriate, since we are talking about packages that get into images, not recipes. |
| 23:11.26 | *** join/#oe apelete (~apelete@176-26-190-109.dsl.ovh.fr) |
| 23:18.20 | kroon | 'night folks |
| 23:24.51 | *** join/#oe erbo (~erik@host.62.65.125.245.bitcom.se) |
| 23:40.07 | *** join/#oe nitink1 (~nitink@134.134.139.76) |