**** BEGIN LOGGING AT Tue Apr 02 02:59:58 2013 Apr 02 08:02:38 morning all Apr 02 08:18:01 good morning Apr 02 14:58:52 YPTM: I'm here Apr 02 14:59:17 YTPM: Saul's joined Apr 02 14:59:25 YPTM: davest here Apr 02 14:59:55 YPTM: Björn is here Apr 02 15:00:00 YPTM: Tom here Apr 02 15:01:07 YPTM: RP is here Apr 02 15:01:18 YPTM: Kevin Strasser is dialing in Apr 02 15:01:30 YPTM: Scott Rifenbark joined the call Apr 02 15:01:42 YPTM: Nitin joined the bridge Apr 02 15:01:49 YPTM: Bruce Ashfield is here. Apr 02 15:02:00 YPTM: Belen joined the call Apr 02 15:02:49 YPTM: Bruce Ashfield is here Apr 02 15:03:00 first post! Apr 02 15:03:10 YPTM: I'm still here Apr 02 15:03:12 YPTM: welcome to the technical team meeting, please let me know who's on the bridge. Apr 02 15:03:31 YPTM: Scott Rifenbark is here. Apr 02 15:03:35 YPTM: davest here (again) Apr 02 15:03:35 YPTM: Björn is here Apr 02 15:03:42 YPTM: Kevin Strasser is here Apr 02 15:03:48 YPTM: Tom Apr 02 15:03:48 YPTM: Saul's here Apr 02 15:03:56 YPTM: Belen's here Apr 02 15:04:35 YPTM: Richard is here Apr 02 15:05:40 YPTM: Richard rejoined Apr 02 15:05:40 YPTM: dialing in now Apr 02 15:06:01 YPTM: Any opens? Apr 02 15:06:20 Song_liu: LSB Apr 02 15:06:47 Song_liu: Mark was talking about LSB :) Apr 02 15:06:56 LSB - Linux Standard Base ;) Apr 02 15:06:57 sorry Apr 02 15:09:58 multilib in world is a useful test IMHO.. it finds the PN/BPN problems Apr 02 15:15:54 fray: agreed, I just want to understand why we have "new" failures on the release build Apr 02 15:16:28 I'll mention it on the call, my concern is the Python runtime tests Apr 02 15:16:52 fray: for lsb? Apr 02 15:16:56 ya Apr 02 15:17:08 it's only three items, but python is something we really do need to ensure is working properly on the target Apr 02 15:17:31 fray: build appliance does that quite well, at least for one arch :) Apr 02 15:18:07 ya.. my concern is that the three failures could be indicating a problem we haven't found in python.. I don't remember python failures in 1.3 (but my memory could be wrong).. Apr 02 15:18:32 my concern is that we compare results against 1.3 where applicable.. since that would indicate a regression.. (where 1.4 has new tests, we just need to make a determination) Apr 02 15:19:06 Song_liu: YPTM: Sean just joined. Apr 02 15:19:43 YPTM: Paul Eggleton joined a bit earlier as well FYI Apr 02 15:29:27 Song_liu: I think that you need to skip Constantin Apr 02 15:29:41 bluelightning: what was the URL? Apr 02 15:29:48 fyi: https://bugs.launchpad.net/linaro-oe/+bug/1154930 Apr 02 15:29:57 http://layers.openembedded.org/ Apr 02 15:30:20 ^ Apr 02 15:31:20 and: https://launchpad.net/linaro-oe Apr 02 15:31:27 bluelightning: I reference openembedded.org/wiki/LayerIndex as a place to look for existing layers. This wiki page still up-to-date? Apr 02 15:31:27 bluelightning: we may need to put a redirect for http://www.openembedded.org/wiki/LayerIndex Apr 02 15:34:31 how does this index work? I searched for recipe "expect" and got a hit for busybox? Apr 02 15:35:07 oh, it matches the description. "the expected functionality" Apr 02 15:35:40 Zagor: yep, it searches name, summary, description and filename Apr 02 15:35:48 halstead: 20 whole minutes?!?!? unacceptable! Apr 02 15:39:00 Thanks darknighte :) Apr 02 15:39:17 halstead: np. way to keep us running! Apr 02 15:39:40 halstead: nice work in getting things back up despite the challenges :) Apr 02 15:39:58 YPTM: thank you all for joining the meeting. Have a nice day or evening Apr 02 15:49:55 scottrif, darknighte The plan is to replace the layer index with the tool, but the tool just went live :) Apr 02 15:58:50 bluelightning: halstead: belen: alexandru: the new index rocks. thanks for putting it together Apr 02 16:00:47 darknighte: you're welcome :) Apr 02 16:35:55 If I change DISTRO_FEATURES (e.g., to remove x11) and rerun bitbake, why doesn't anything happen? AFAICT libX11 is still included in the rootfs... Apr 02 16:48:44 Saur: are you sure the value is being used? bitbake -e | grep ^DISTRO_FEATURES= Apr 02 16:49:21 bluelightning: Yea, I have checked with bitbake -e, and the resulting DISTRO_FEATURES matches what I wanted... Apr 02 16:50:11 Saur: so nothing happened at all? or some things rebuilt? Apr 02 16:53:41 bluelightning: It only reruns the do_rootfs step (which always happens when rerunning bitbake) Apr 02 16:59:03 Saur: try removing the cache. I think we might have a cache bug Apr 02 17:00:56 RP2: What cache? Apr 02 17:05:54 RP2: If you meant the cache directory in ${TOPDIR}, removing it made no difference. Apr 02 17:18:25 Saur: ok, was worth a try :/ Apr 02 17:19:18 RP2: Any other ideas+ Apr 02 17:21:01 RP2: I would have thought changing DISTRO_FEATURES would affect quite a number of packages... Apr 02 17:21:37 Given how many look at the variable... Apr 02 17:24:51 Saur: indeed, that is what I would expect as well Apr 02 17:25:18 Saur: what version of the build system are you using? Apr 02 17:25:34 bluelightning: master of poky Apr 02 17:25:42 ok Apr 02 17:40:13 RP2: I've noticed that you merged some of my changes, there is one older pending for util-linux http://patchwork.openembedded.org/patch/46565/ There was discussion with Bernhard, but only about possible improvements for lsb, in the end he agreed that patch is OK to go in Apr 02 19:27:22 JaMa: I noticed that also as I was going back though the queue trying to gather items up, RP and I will look at it again Apr 02 19:31:16 sgw_: ok, thanks Apr 02 19:34:34 help me plz. udev_182.bb provide libudev and libgudev, but when i build qt4e-demo-image , only libudev installed. what i should to do to install libgudev ? Apr 02 19:40:26 halstead: ping. List of autobuilder distros? Apr 02 19:41:38 ? Apr 02 19:41:56 alex_kag: add it to IMAGE_INSTALL Apr 02 19:45:25 is in IMAGE_INSTALL - i should wrought name of "rpm" package? I think there are written the names of "bb" packages :( Apr 02 19:45:50 package names Apr 02 19:48:47 full? I have libgudev-1.0-0-182-r6.armv7a_vfp_neon.rpm , i must write "libgudev" or "libgudev-1.0-0-182-r6" ? Apr 02 19:50:47 just libgudev Apr 02 19:52:24 thanks Apr 02 20:50:37 RP2: Finally figured out my mistake with DISTRO_FEATURES. It helps to put the assignment in the correct file... I had put it in recipe file for the image. It worked a lot better once I put it in local.conf... Apr 02 21:24:55 Saur: that would make a big difference! :) **** ENDING LOGGING AT Wed Apr 03 02:59:57 2013