**** BEGIN LOGGING AT Tue Apr 01 02:59:59 2014 Apr 01 04:01:52 *reminder*: OE monthly in roughly 12 hours (?) Apr 01 06:42:06 morning Apr 01 08:10:34 I'd like to fix open-vcdiff recipe (bitbake world, Failed task), but I'm unable to reproduce the aclocal error, works fine here with different MACHINE. Apr 01 08:10:59 For now I'm using: DISTRO=nodistro MACHINE=qemuarm bitbake open-vcdiff Apr 01 08:51:47 morning all Apr 01 08:54:06 hi! Apr 01 09:04:00 hi matt10 Apr 01 09:20:05 bluelightning, could you highlight me of how automatic test build is made? Apr 01 09:49:58 matt10: which part of that? Apr 01 09:52:19 I'm trying to understand what's wrong in my open-vcdiff (in master-next) recipe Apr 01 09:53:04 The recipie is reported in "State of bitbake world" Apr 01 09:53:50 matt10: ah ok, JaMa runs those builds Apr 01 09:54:24 aclocal: error: non-option arguments are not accepted: '\'. Apr 01 09:54:38 I'm unable to get the same error Apr 01 10:27:28 matt10: are you testing it with latest oe-core? Apr 01 10:34:32 hi Jama yes, I'm up to date to master + my recipe patch Apr 01 10:50:44 http://cgit.openembedded.org/meta-openembedded/commit/?h=master-next&id=7720023d0e69215746753cb3dea2ec9e61408a15 Apr 01 10:50:55 Jama: can you reproduce the error ? Apr 01 10:52:07 obviously yes as I've reported it :) Apr 01 10:53:38 Hehe :) I trying to have this error since yesterday, works fine here, tested with qemuarm/x86/x86_64 nodistro Apr 01 10:53:49 There must be something different Apr 01 11:37:56 koen: where would you put dracut if we delete the meta-initramfs layer? Apr 01 11:38:54 ideally oe-core Apr 01 11:38:57 alternatively it could remain but almost empty, with only dracut Apr 01 11:38:57 otherwise meta-oe Apr 01 11:39:33 you see, nobody seems using it (apart you) so I'd merge klibc & kexecboot back to meta-handheld Apr 01 11:41:02 it seems all initramfs stuff is being grouped in oe-core under initrdscripts Apr 01 12:12:52 Jama, I'ven't still reproduced but I've found an "old autotools" issue Apr 01 14:40:28 hi Apr 01 14:40:43 is it possible and recommended to bbappend a recipe? Apr 01 14:40:57 hm okay Apr 01 14:40:59 seems so Apr 01 14:46:51 woglinde: not sure I understand the question... ? Apr 01 14:52:54 bluelightning I did my old error asking before reading two lines deeper at google Apr 01 14:53:17 woglinde: ok, well, as long as you got your answer everyone's happy I guess :) Apr 01 14:55:23 args I meant image recipe Apr 01 14:55:26 by the way Apr 01 14:58:07 ah right, that makes more sense as a question Apr 01 14:58:17 I would say no, myself Apr 01 14:58:27 I mean there's nothing technically to stop you Apr 01 14:59:14 but my opinion regarding image recipes has always been that they're normally so trivial that it's not worth trying to append the existing one; just add your own new custom one that contains what you want Apr 01 14:59:59 what about the core-image recipe? Apr 01 15:05:33 dv_ *g* Apr 01 15:07:52 dv_: there isn't one "core-image" recipe Apr 01 15:08:20 and the same applies to those as any other image, IMO Apr 01 15:35:30 hi pb Apr 01 15:37:17 hi woglinde Apr 01 15:59:02 OE/TSC meeting in 1 minute Apr 01 16:00:14 someone is really eager... :) Apr 01 16:00:16 * fray is on hour 3 of meetings w/o a break.. so I might be a few minutes late to the start.. ;) Apr 01 16:00:28 denix: :-D Apr 01 16:00:39 I'm here, just finishing up another meeting Apr 01 16:01:02 will the meetingbot be running? Apr 01 16:01:15 Crofton: Crofton|work: ^ Apr 01 16:01:26 if not, I'm sure we can wing it Apr 01 16:02:45 moin Apr 01 16:03:00 * RP is here Apr 01 16:03:45 * tlwoerner is looking forward to OEDAM, it'll be nice meeting many of you :-) Apr 01 16:04:19 ok let's make a start Apr 01 16:04:26 tlwoerner: haven't you been to any of the previous ones? Apr 01 16:04:38 denix: it'll be my first Apr 01 16:04:56 i've met Crofton and Khem at a Connect last year, but that's all Apr 01 16:04:57 khem: koen: ping Apr 01 16:05:04 I'll be back in a ouple minutes Apr 01 16:05:05 oh yea, and Koen :-) Apr 01 16:05:11 bluelightning: agenda? Apr 01 16:05:23 tlwoerner: you with linaro now, IIRC? Apr 01 16:05:28 yes :-D Apr 01 16:05:28 denix: there isn't one, but I'm hoping not to be the chair yet again FWIW ;) Apr 01 16:05:47 bluelightning suggested an agenda list: - Upcoming release Apr 01 16:05:48 - World build status Apr 01 16:05:48 - Website and other infrastructure issues Apr 01 16:06:01 I can only be here for the next 30 mins Apr 01 16:06:02 right, I did have those suggestions Apr 01 16:06:02 Jefro: thanks! Apr 01 16:06:27 Well, I can talk about the upcoming release Apr 01 16:06:34 so who wants to chair? Apr 01 16:06:47 * nerdboy already has a chair Apr 01 16:06:55 bluelightning: I can help for the first half... Apr 01 16:06:59 what's involved? Apr 01 16:07:22 tlwoerner: keeping the discussion on track and to time Apr 01 16:07:27 * tlwoerner can chair Apr 01 16:07:34 tlwoerner: thanks :) Apr 01 16:07:35 tlwoerner: it's like musical chairs game... :) Apr 01 16:07:39 1/2 hour or full? Apr 01 16:07:40 tlwoerner: thanks! Apr 01 16:07:54 tlwoerner: I think you just signed up for the hour Apr 01 16:08:00 tlwoerner: I will just be less vocal in the second half as I'll be distracted Apr 01 16:08:16 bluelightning: ok, i was wondering if the meeting lasted the full or half hour :-) Apr 01 16:08:32 we usually get to an hour with these things Apr 01 16:08:32 okay let's start, first topic "upcoming release" Apr 01 16:08:43 everything's green and ready to ship? Apr 01 16:08:57 As per the status email I sent out, we merged 3.14 in Apr 01 16:09:05 the kernel, that is Apr 01 16:09:10 builds are green, test report for -rc1 is available Apr 01 16:09:22 we've been in much worse shape for releases so I'm optimistic Apr 01 16:09:23 RP: you are still accepting enhancements, like README update, right? :) Apr 01 16:09:40 denix: Yes, I am going to take that one Apr 01 16:09:44 * fray is back sorry Apr 01 16:10:00 denix: in general no, but a change to the README is low risk Apr 01 16:10:14 http://article.gmane.org/gmane.comp.handhelds.openembedded.core/50181 Apr 01 16:10:21 status update email ^ Apr 01 16:10:27 RP: thanks! and sorry for delay - documentation is not my strongest side... :) Apr 01 16:10:49 denix: Nobody likes doing it but here we do really need it ;-) Apr 01 16:11:07 indeed Apr 01 16:11:08 How is meta-openembedded coming along? I havn't been tracking that recently and just want to make sure there isn't anything causing signficiant issue Apr 01 16:11:12 our bug metrics have shown a downward trend too which is nice Apr 01 16:11:22 fray: that's kind of the topic of the next item Apr 01 16:11:22 fray: Martin has asked for help there Apr 01 16:11:31 denix: do you have additions to the README to make? Apr 01 16:11:36 bluelightning sorry I missed that.. ok I'll wait Apr 01 16:11:54 Bug Trend charts: https://wiki.yoctoproject.org/charts/combo.html Apr 01 16:12:10 tlwoerner: yes Apr 01 16:12:15 tlwoerner: denix owes me a readme for meta-yocto ;-) Apr 01 16:12:32 :) Apr 01 16:12:40 I took the other patches on trust that one would be forthcoming :) Apr 01 16:13:02 ha! it is forthcoming :) Apr 01 16:13:13 RP: and after the README updates the release is ready to go out? Apr 01 16:13:35 tlwoerner: I'm expecting a couple of -rcs of bug fixes Apr 01 16:13:48 does anyone have a link to the release schedule? Apr 01 16:13:59 we've still got some documentation stuff to tidy up and I know there are some open toaster bugs to be addressed in particular Apr 01 16:14:18 There are also issues on the -rc1 test report Apr 01 16:14:34 https://wiki.yoctoproject.org/wiki/Yocto_1.6_Schedule Apr 01 16:14:44 top of the page has the time scales.. Apr 01 16:15:09 bluelightning: thanks Apr 01 16:16:24 okay... moving on Apr 01 16:16:35 new topic: world build status Apr 01 16:16:39 i guess we've already covered this one Apr 01 16:17:10 anything else to say about world build status? Apr 01 16:17:27 This is probably more about meta-oe Apr 01 16:17:41 yes Apr 01 16:17:43 is JaMa around? Apr 01 16:17:45 I think Martin's email covers it well, there are challenges there Apr 01 16:18:06 basically it's about getting more people involved in fixing the failures highlighted by his builds Apr 01 16:18:11 are patches to SOBBW (state of bb world) still being accepted for 1.6? Apr 01 16:18:29 tlwoerner: they're bugs so I would assume yes Apr 01 16:18:43 bluelightning: okay Apr 01 16:18:49 yocto bugs? Apr 01 16:19:06 right, the point we're at is feature freeze, no new features or package upgrades Apr 01 16:19:15 bug fixes are very much still going in Apr 01 16:19:17 nerdboy: these are bugs mostly in recipes in meta-oe and other layers within the meta-openembedded repo Apr 01 16:19:21 both for oe-core and meta-oe Apr 01 16:19:39 so the email is the "bug" list? Apr 01 16:20:25 the basic problem, just like we had in OE-Classic, is that people contribute recipes and then aren't available to keep them up-to-date and help fix them if they break in future Apr 01 16:21:34 Andreas just pushed a bunch of gnome stuff Apr 01 16:22:02 I expect the couple meta-networking items to be fix soon as well Apr 01 16:22:11 * RP wishes he had more time to help with meta-oe :/ Apr 01 16:22:31 the email is here FYI: http://lists.openembedded.org/pipermail/openembedded-devel/2014-March/094893.html Apr 01 16:22:50 nerdboy: yes and you can consult http://www.openembedded.org/wiki/Bitbake_World_Status Apr 01 16:23:29 I can't think of any magic solutions, beyond getting more maintainers for individual recipes engaged Apr 01 16:23:35 i do appreciate the work JaMa puts into the SOBBW and hope he continues with that Apr 01 16:23:55 absolutely, he's doing a great job Apr 01 16:24:06 yup i agree Apr 01 16:24:08 bluelightning: come projects have a requirement to not accept "dump and run" patches Apr 01 16:24:14 s/come/some Apr 01 16:24:39 tlwoerner: how to enforce it? Apr 01 16:24:44 tlwoerner: it's kind of hard to know when that'll happen though; people commit to things in good faith and then have other commitments come up Apr 01 16:24:45 JaMa is doing a great job there Apr 01 16:24:53 denix: not apply them Apr 01 16:25:38 I do agree with Martin's current mode where he's not accepting patches that throw up issues in his tests Apr 01 16:25:50 at least we won't introduce breakage from the first time the recipe lands Apr 01 16:25:58 tlwoerner: in order to not apply them, you need to know they will become abandoned in the future. w/o crystal ball you won't know that Apr 01 16:26:05 it probably comes down to a calculation of how important the package is for the overall ecosystem Apr 01 16:26:13 * bluelightning wants a crystal ball Apr 01 16:26:47 tlwoerner: this is a really tricky problem unfortunately Apr 01 16:26:47 bluelightning: how big? Apr 01 16:26:56 denix: for example if someone wanted to submit a new recipe, they'd have to have a track record of N fixes Apr 01 16:27:06 The idea was to have layers with maintainers who care about their specific parts Apr 01 16:27:17 denix: needs to be small, I need to be able to take it to conferences ;) Apr 01 16:27:20 the pressure on the catchall is still there though Apr 01 16:27:39 what do people think of the proposal to have "meta-notworking" Apr 01 16:27:41 YUP Apr 01 16:27:55 I hate to say it but it might be time to think about the size of meta-oe and whether there are parts that can reasonably be carved off Apr 01 16:28:06 tlwoerner: you require upfront reputation Apr 01 16:28:12 bluelightning: good point :) Apr 01 16:28:25 its a reasonable way to ensure green builds.. but perhaps a blacklist disable would be better w/ a timeout period? Apr 01 16:29:06 bluelightning: I'd agree Apr 01 16:29:32 well opensource is generally a meritocracy.. to getting things in requiring reputation is reasonable Apr 01 16:29:36 denix: if someone comes along and wants to contribute some huge recipe that requires lots of additional supporting recipes, maybe some consideration should be given to future maintenance? Apr 01 16:29:42 there's only a point to doing that if categories can be carved out *and* there is a maintainer for each one willing to step up Apr 01 16:29:46 fray: we've done things like this before, we still have the BROKEN = "1" in places :/ Apr 01 16:30:00 * RP should really remember to kill the remnants of that Apr 01 16:30:04 RP, I was thinking actually using the blacklist class and some automation... Apr 01 16:30:09 bluelightning: maybe more refactoring than carving... Apr 01 16:30:23 that way if someone wants the thing they're informed hey this doesn't work, if you get it to work tell us or we'll remove it Apr 01 16:30:34 nerdboy: right, could be that kind of thing Apr 01 16:30:37 then prune after a certain amount of time.. Apr 01 16:30:47 fray: that sounds like an interesting idea; it would save all of us from having to keep our conf/local.conf's in sync Apr 01 16:30:49 fray, tlwoerner: agree Apr 01 16:30:53 We really need Martin's input here Apr 01 16:31:02 RP: agreed Apr 01 16:31:03 yes, I wouldn't think of implementing it without his opinion Apr 01 16:31:12 since i'm already adding several layers to meta-oe just to get my "lightweight" build to complete... Apr 01 16:31:30 fray: would you like to take a work item to propose this on the mailing list? Apr 01 16:31:41 ya.. I'll respond to his email.. Apr 01 16:32:15 a meeting isn't a meeting without action items... Apr 01 16:32:20 I have a reply drafted but not sent yet... nothing earth shattering but replies to the layer index comment Apr 01 16:32:51 what's the email subject line? Apr 01 16:33:29 so back to the current bugs, how soon does the "world" build get run again? Apr 01 16:33:31 bitbake world domination? Apr 01 16:35:06 i'd like to fix something without spinning on something Andreas just fixed... Apr 01 16:35:29 nerdboy: yes, there needs to be more coordination Apr 01 16:35:37 for the SOBBW fixes Apr 01 16:35:57 what woudl work best for people? mailing list, IRC, wiki? Apr 01 16:36:08 that was one of my topics for oedam Apr 01 16:36:22 nerdboy: okay, we can discuss it then Apr 01 16:36:43 this topic seems to be winding down Apr 01 16:36:51 for now i would just like to kill a few bugs ... Apr 01 16:36:57 new topic: website infrastructure and updates Apr 01 16:38:23 jackmitchell: do you have an update? Apr 01 16:39:54 fray: do you mean the patches Otavio has been sending? Apr 01 16:40:00 fray: (blacklist) Apr 01 16:40:12 I havn't seen them.. so perhaps Apr 01 16:40:52 bluelightning: are you aware of any ongoing/planned infrastructure updates Apr 01 16:41:03 Which ones, I'm not finding them? Apr 01 16:41:35 whoops, those are from August 2013 Apr 01 16:42:08 tlwoerner: the plan is to do a new front page for the website; I've lost track of what the status of it is though Apr 01 16:42:51 bluelightning: okay thanks. it doesn't look like jackmitchell is around Apr 01 16:43:06 bluelightning: this is for http://www.openembedded.org/wiki/Main_Page? Apr 01 16:43:42 tlwoerner: it would take the place of that yes (the wiki will remain for other content though) Apr 01 16:44:13 bluelightning: are there any plans to re-organize the wiki? Apr 01 16:44:19 the idea is to give a much clearer introduction to the project Apr 01 16:44:28 I think we should do that as part of the same effort, yes Apr 01 16:44:41 RP and I did some cleanup a while ago, but there's still junk in there Apr 01 16:44:42 and jackmitchell is the person doing the work? Apr 01 16:45:09 tlwoerner: the frontpage part of it yes, I think he is getting help from ka6sox on setting things up Apr 01 16:45:20 tlwoerner: he presented his mockup at last ELCE Apr 01 16:45:26 I don't think anyone's volunteered to clean up the wiki yet Apr 01 16:46:28 okay, ka6sox is scheduled to attend OEDAM so maybe there will be an update at that time Apr 01 16:46:48 that appears to finish the proposed schedule items Apr 01 16:47:00 does anyone have any additional items/topics? Apr 01 16:47:14 - is it too early to talk about 1.7 features, or should we wait? Apr 01 16:47:32 1.7 features are something we are certainly interested in.. Apr 01 16:47:56 if people have things they're planning to contribute, or think would make the overall oe experience better this is a good time to get that information known Apr 01 16:48:24 fray: and put them in bugzilla Apr 01 16:48:25 using the Yocto Project bugzilla is a good way to do this. The oe-core mailing list can also be used. Apr 01 16:48:30 yup Apr 01 16:49:23 - any thoughts on the differences between OE and Yocto recipe variable ordering (specifically the placement of the R* variables)? Apr 01 16:49:44 would it be possible to align the styles? Apr 01 16:50:01 sounds like a janitor type thing.. Apr 01 16:50:19 I'm not against it.. but a general project style should be generated (if it doesn't already exist in the wiki) Apr 01 16:50:22 http://openembedded.org/wiki/StyleGuide versus https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide Apr 01 16:50:40 fray: the issue is there are two :-) Apr 01 16:50:56 tlwoerner: I don't think there is contention on that one point Apr 01 16:51:15 the tabs vs spaces thing is contentious however Apr 01 16:51:42 bluelightning: so which guide is correct wrt placement of R* variables? high in recipe, or low? Apr 01 16:51:59 tlwoerner: with other packaging specific stuff so lower down Apr 01 16:52:15 if the two guides really can't be one yet, we should at least be able to get to the point where one is a "see the other + these one or two minor things" Apr 01 16:52:20 I'm used to seeing the R's grouped near the FILES myself.. Apr 01 16:52:28 fray: right, that's what I mean Apr 01 16:52:30 yup Apr 01 16:52:45 okay, so... Apr 01 16:52:54 DESCRIPTION Apr 01 16:52:54 AUTHOR Apr 01 16:52:54 HOMEPAGE Apr 01 16:52:54 SECTION Apr 01 16:52:54 LICENSE Apr 01 16:52:57 DEPENDS Apr 01 16:52:59 RDEPENDS Apr 01 16:53:01 RRECOMMENDS Apr 01 16:53:03 RSUGGESTS Apr 01 16:53:05 PROVIDES Apr 01 16:53:07 RPROVIDES Apr 01 16:53:09 RCONFLICTS Apr 01 16:53:11 SRCDATE Apr 01 16:53:13 PV Apr 01 16:53:15 PR Apr 01 16:53:17 ... Apr 01 16:53:20 no Apr 01 16:53:34 bluelightning: okay, thanks Apr 01 16:53:35 ya my preference is DEPENDS and PROVIDES at the top, since they describe the recipe.. Apr 01 16:53:39 * tlwoerner takes an action to update OE wiki Apr 01 16:53:44 tlwoerner: that's still putting R* before non-packaging fields Apr 01 16:53:51 and R*_package at the bottom near the FILES_ since they refer to the 'packages' Apr 01 16:53:58 fray: yep, me too Apr 01 16:54:11 okay, then: Apr 01 16:54:14 DESCRIPTION Apr 01 16:54:14 AUTHOR Apr 01 16:54:14 HOMEPAGE Apr 01 16:54:14 SECTION Apr 01 16:54:14 PRIORITY Apr 01 16:54:16 LICENSE Apr 01 16:54:17 if it helps, I came up with an ordering that I use within the layer index Apr 01 16:54:18 DEPENDS Apr 01 16:54:20 SRCDATE Apr 01 16:54:22 SRCREV Apr 01 16:54:26 PV Apr 01 16:54:28 PR Apr 01 16:54:30 SRC_URI Apr 01 16:54:32 S Apr 01 16:54:34 inherit ... Apr 01 16:54:36 build class specific variables, i.e. EXTRA_QMAKEVARS_POST Apr 01 16:54:38 task overrides, i.e. do_configure Apr 01 16:54:40 PACKAGE_ARCH Apr 01 16:54:42 PACKAGES Apr 01 16:54:44 i don't think repeatedly spaming the channel is the best method to work things like that out, personally Apr 01 16:54:44 FILES Apr 01 16:54:46 RDEPENDS Apr 01 16:54:48 RRECOMMENDS Apr 01 16:54:50 RSUGGESTS Apr 01 16:54:52 PROVIDES Apr 01 16:54:56 RPROVIDES Apr 01 16:54:58 RCONFLICTS Apr 01 16:55:06 something like that yes.. (don't forget summary at the top) ;) Apr 01 16:55:18 kergoth: sorry Apr 01 16:55:22 http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/tree/layerindex/bulkchange.py#n24 Apr 01 16:55:57 not sure if that lines up with everyone else's expectations, but it should be mostly acceptable I think Apr 01 16:56:08 it's pretty close.... Apr 01 16:56:32 okay i'll take an action to align the various places this shows up for consistency Apr 01 16:56:40 I'm missing S in there I think Apr 01 16:56:41 and these are just guidelines.. there may be reasons to deviate.. but having a more unified style makes sense to me.. and could be an easy janitorial project Apr 01 16:56:48 i would prefer to see more effort in other areas rather than style wars... Apr 01 16:56:53 (and B... which is rarely set) Apr 01 16:57:00 oe-stylize.py, OE wiki, yocto wiki Apr 01 16:57:25 if someone is going to go further with this oe-stylize is the thing to fix so it matches everyone's expectations (I don't use it myself, but I'm told it doesn't quite atm) Apr 01 16:57:36 nerdboy, I don't disagree.. I just consider this pretty easy to resolve.. and if there are places where there isn't a clear answer.. we document it and move on Apr 01 16:57:50 oe-stylize has often failed to handle certain variables, making it of limited usefulness. it'd need a little tlc, i think Apr 01 16:58:03 fray: yes i agree, but my issues is the information that is out there is contradictory Apr 01 16:58:13 fray: stop reading my thoughts Apr 01 16:58:41 any new topics? Apr 01 16:58:52 (2 minutes remaining) Apr 01 16:58:54 * nerdboy makes a new foil hat Apr 01 16:59:17 nothing here Apr 01 16:59:32 thank you everyone for attending Apr 01 16:59:43 next monthly meeting will be May 6th Apr 01 16:59:44 tlwoerner: great job chairing, thanks very much :) Apr 01 17:00:00 and inbetween now and then is the OEDAM Apr 01 17:00:12 bluelightning: thank you :-) Apr 01 17:01:04 * nerdboy smells a tasty beverage brewing Apr 01 17:03:18 lemme get another coffee and i'll look at fixing some of the things not listed in Andreas' patch email Apr 01 17:03:55 * nerdboy starts a fresh arm build Apr 01 17:21:47 nerdboy: i just noticed your question which went unanswered (i think) Apr 01 17:22:01 nerdboy: i think JaMa runs his world build every week Apr 01 17:22:59 http://openembedded.org/wiki/Bitbake_World_Status Apr 01 17:26:21 yup, found the wiki page Apr 01 17:26:52 building gnuplot... Apr 01 17:27:14 crap, sorry about the bot Apr 01 17:27:19 I am traveling so just got in Apr 01 17:28:31 is the meeting over? Apr 01 17:28:59 Crofton: woglinde: meeting finished 30 minutes ago, no problem Apr 01 17:29:06 okay Apr 01 17:29:06 i'm typing up notes for the mailing list now Apr 01 17:29:11 thanks Apr 01 17:29:14 hi crofton Apr 01 17:29:33 Crofton... Apr 01 17:31:53 hm what option in local.conf deletes the opkg meta data? Apr 01 17:31:57 I need to disable it Apr 01 17:32:19 or is it an image option? Apr 01 17:33:15 I guess IMAGE_FEATURES += " package-management " Apr 01 17:33:18 it is Apr 01 17:33:24 yup Apr 01 17:33:45 lack of package-management in either the local.conf or the recipes is what clears the package db and does NOT install the package tools Apr 01 17:34:05 if you add that, you don't need to individually list the package components. (for rpm that would be 'rpm smart') Apr 01 17:35:48 yay, a straggling pr include change... Apr 01 17:53:12 RP_: bluelightning, tlwoerner, nerdboy, fray, all: sorry I had conflicting meeting for whole time Apr 01 17:53:54 JaMa: np, I know the feeling :/ Apr 01 17:54:09 I think we should discuss it on OEDAM, it seems that last e-mail motivated few more people to send patches, so maybe my next status will be more possitive and we'll just discuss how to maintain it that way :) Apr 01 17:55:19 JaMa: lets hope so :) Apr 01 18:09:41 looks like gnuplot needs a license correction Apr 01 18:10:10 hm in which package resize2fs ends up? Apr 01 18:13:18 okay e2fsprogs Apr 01 18:14:01 nerdboy: please notice that there is upgrade for gnuplot on ml, but without license change Apr 01 18:14:09 so it would be good as follow-up Apr 01 18:16:59 recently? Apr 01 18:17:24 yes Apr 01 18:17:39 found it Apr 01 18:32:13 JaMa: i'm applying the patch from Tim Apr 01 18:35:24 nerdboy: tlwoerner: the builds are triggered manually and build for all 3 archs takes around 3 days Apr 01 18:36:14 so usually less than twice per week, sometimes less often or without sending the report, depending on metadata changes Apr 01 18:36:34 if there is something terribly broken (and most issues are hidden by that) I won't send the report Apr 01 18:47:50 also adding the gd license file Apr 01 18:54:30 cool, thanks! Apr 01 18:59:05 crap, i didn't see the gnuplot-4.4.4 fail here either Apr 01 19:38:20 JaMa: are build logs accessible? Apr 01 19:38:30 can i see the gnuplot errors? Apr 01 19:39:23 yes, there is link to them in each report Apr 01 19:39:31 otherwise gd and gnuplot upgrade looks clean here... Apr 01 19:39:53 they are quite big sometimes, so better to wget them and read locally Apr 01 19:40:09 at least chromium doesn't search that well in big files Apr 01 19:42:31 woglinde: is there a mirror for jamvm? I'm getting connection refused when trying to build Apr 01 19:47:32 JaMa: your world builds are branched from master? Apr 01 19:49:11 Do someone knows why alsamixer is like this: http://pastebin.com/7Hq00X35 ? Apr 01 19:54:48 i'm going to say the lua packageconfig setting and newer version should take care of the error in your build log Apr 01 19:55:20 but 4.4.4 built fine for me too... Apr 01 19:57:28 otavio: are any other curses apps goofy? Apr 01 19:58:02 not sure if you can force ascii but it looks like a charset problem... Apr 01 19:58:20 mc has a -a switch for that Apr 01 19:59:55 nerdboy: see wiki, it's described there Apr 01 20:00:30 what exactly? i saw the build error i can't reproduce Apr 01 20:02:38 http://www.openembedded.org/wiki/Bitbake_World_Status at the top describes how they are built and from what Apr 01 20:02:52 oh, that Apr 01 20:05:25 nerdboy: charset. Humm Apr 01 20:05:45 alsamixer needs ncurses and nls support Apr 01 20:05:54 are you building against uclibc? Apr 01 20:06:17 if so, that disables nls Apr 01 20:07:29 nerdboy: no; this is default poky setup Apr 01 20:07:43 inherit pkgconfig might not be a bad idea for alsa-utils... Apr 01 20:08:11 otavio: can you check another ncurses app in your build? Apr 01 20:08:24 I need to figure out any other Apr 01 20:10:02 mc, vim, nano... Apr 01 20:10:36 links? Apr 01 20:14:04 JaMa: would it be easier if i forked your github repos and make a pull request? Apr 01 20:15:34 nerdboy: no, please send patches to ML Apr 01 20:16:35 the previous patch didn't apply so i replicated it Apr 01 20:17:11 that will be one patch for meta-oe and one patch for poky/core for the licenses Apr 01 20:25:38 as far as the libimobiledevice fail, it's mostly broken against iOS 7 anyway Apr 01 20:26:43 really need new recipes for all 5 libimobiledevice pieces and build from their git repos until upstream does a new release Apr 01 20:27:37 the newer stuff needs cython support as well Apr 01 20:52:43 nerdboy: nano always works fine. Apr 01 21:00:23 other than make menuconfig, mc is the only one i can think of righ tnow with a full curses interface Apr 01 21:01:22 JaMa: meta-oe ones are sent Apr 01 21:01:46 what about the license files? Apr 01 21:02:08 same process? should they go to oe-core or poky? Apr 01 21:50:55 okay, oe-core it is... Apr 01 21:52:17 hrmm, meta-beagleboard buggers up dtc :-( Apr 01 21:53:17 nerdboy: your gnuplot change should be just changing the license, leave Tim's change alone or keep original author Apr 01 22:12:12 crap, that was the whole thing, wasn't it... Apr 01 22:37:39 JaMa: fixed Apr 01 22:46:06 okay, so how do i keep it from switching shlib providers from gtk-* to gtk3-* ? Apr 01 23:21:15 nerdboy: the licenses should go to meta-oe repository Apr 01 23:21:56 nerdboy: see de3f394d7bdb5b14b6618cb1bf7e5101c42fc3a9 commit in meta-oe Apr 01 23:22:41 nerdboy: and otherwise oe-core patches needs to go to oe-core ML not oe-devel Apr 01 23:25:07 should they go in common-licenses or somewhere else? Apr 01 23:26:47 meta-oe/licenses/ Apr 01 23:55:35 lemme do a quick build check... **** ENDING LOGGING AT Wed Apr 02 02:59:59 2014