**** BEGIN LOGGING AT Tue Sep 10 03:00:00 2013 Sep 10 08:51:04 Hello everybody. Are you using OPKG as your preferred package manager ? I think it is strange how it proceeds to update a package => 1. Delete, 2. Download, 3. Update files... Well what if it removes the package then finds the internet connection is down ? Sep 10 09:57:39 How do I disable mirrors in certain recipe? Currently oe constructs some nonsensical mirrors and tries to fetch from them. Sep 10 10:08:11 morning all Sep 10 10:08:38 kbart: you can just set PREMIRRORS = "" and MIRRORS = "" in the recipe Sep 10 10:11:35 Hi bluelightning and thank you for the answer. Sep 10 10:19:53 kbart: np Sep 10 10:49:50 bluelightning: Hello Sep 10 10:50:30 I know the answer to my question will be no but asking coz I wanna make sure Sep 10 10:51:06 hi Noor Sep 10 10:51:11 is there a way to include one bb file in another with bbappend applied on included bbfile Sep 10 10:51:42 Noor: no, unfortunately not; the two mechanisms operate at different levels within bitbake Sep 10 10:52:01 Noor: if you're needing to do that it probably indicates some refactoring of the recipes is needed Sep 10 10:52:29 bluelightning: there is an image file in one layer Sep 10 10:52:52 we have our own image recipe which is including that image recipe Sep 10 10:53:09 and we added bbappend append of the image recipe as well Sep 10 10:53:46 so that bbappend is not added in our image recipe when we include that image recipe in our image recipe Sep 10 10:56:17 Noor: is the original image recipe something you're in control of? Sep 10 10:57:23 bluelightning: if that is possible then I might have added change directly to that recipe instead of creating bbappend :) Sep 10 10:57:51 bluelightning: is it corrent to include bbappend as well just like the original bbfile :) Sep 10 10:58:03 this just came to my mind Sep 10 10:58:12 Noor: right, ok :) Sep 10 10:58:13 hm. Noor, it is possible using two layers Sep 10 10:58:27 two extra + the original one Sep 10 10:58:58 bluelightning: we have /meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.8.bb Sep 10 10:59:00 and http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.8.bbappend Sep 10 10:59:00 ant_work: sorry can you explain a bit Sep 10 10:59:27 Noor: first .bb requires one recipe in oe-core Sep 10 10:59:58 thenthere is an infra-layer Sep 10 11:00:01 then the BSP Sep 10 11:22:59 What is the preferred way to get sources from private repositories (username and password protected) with oe? I have a private repository in BitBucket but can't get it working with https and git credential-cache.. Sep 10 11:24:11 I mean it works all right outside of oe, but I simply fail to integrate it in the build process. Sep 10 11:35:05 kbart: in my case, our private trees are private git trees, managed/accessed through ssh. we use the ssh:// in SRC_URI, and request users to setup ~/.ssh/config properly (e.g. username and key) Sep 10 11:36:32 Heh, that's exactly what I'm looking at now.. But I prefer certs to username/key. Sep 10 11:36:55 I somehow missed that BitBucket allows ssh access ;x Sep 10 11:39:21 ndec, could you give an example SRC_URI with ssh? All recipes I'm looking into use svn+ssh.. Sep 10 11:39:54 sure. one sec. Sep 10 11:41:06 kbart: SRC_URI = "git://git.linaro.org/path/project.git.git;protocol=ssh" Sep 10 11:41:54 the key thing is to use git:// even though it is ssh, git:// prefix here tells bitbake 'this is git stuff', then protocol field is used to decide how to fetch. Sep 10 11:46:44 ndec, thanks a lot, looks like it's gonna work at last. It took me few hours of googling already. Getting error now but that's OK as I still need to set up keys. Sep 10 11:47:28 kbart: ok. you need to connect at least once outside of OE to make sure that the host is added in ~/.known_hosts, or you need to configure to skip the check. Sep 10 12:57:26 Grr, still stuck with that SRC_URI in my recipe.. I need resulting URL in form of git@alias:accountname/reponame.git (as stated in https://confluence.atlassian.com/pages/viewpage.action?pageId=271943168), for example, git@BitBucket:user/kernel.git. Is it possible to achieve this without writing custom do_fetch function? Sep 10 13:23:51 bluelightning, I started the bot so you can use meetbot for the tsc meeting Sep 10 13:25:01 I'll be probably a bit late for the meeting, but will read backlog later Sep 10 13:25:37 Crofton|work: thanks, I'll have to re-figure out how to use it... Sep 10 13:25:57 use #startmeeting Sep 10 13:26:04 that will kick things off Sep 10 13:26:13 also google meetbot Sep 10 13:44:53 JaMa: thanks for your answer, it wasn't needed before, is that documented anywhere ? Sep 10 13:50:28 abelloni: xserver-common? it was always needed Sep 10 13:52:55 hum, I don't think so Sep 10 13:53:02 abelloni: sorry you're right, xdg autostart was removed when xinput-calibrator was moved from meta-oe to oe-core Sep 10 13:53:16 abelloni: ask the person who added it to oe-core if it's documented somewhere Sep 10 13:55:01 I think there is a real issue Sep 10 13:55:32 I used to compile core-image-sato with master around mid august Sep 10 13:55:37 and it was working fine Sep 10 13:55:43 abelloni: what's the problem? Sep 10 13:55:51 now, matchbox is not working Sep 10 13:56:08 I tracked it down to /etc/X11/Xsession Sep 10 13:56:42 core-image-sato depends on both xserver-common and x11-common Sep 10 13:56:48 both provides /etc/X11/Xsession Sep 10 13:57:01 one of them is buggy Sep 10 13:57:14 let me check Sep 10 13:57:59 sigh Sep 10 13:58:17 I wish I'd had time to unravel this xserver-common vs. x11-common business :/ Sep 10 13:59:11 yeah, the one from xserver-common is definitely buggy Sep 10 13:59:21 ls -X is sorting by file extension Sep 10 13:59:32 which is obviously not what you want Sep 10 15:56:05 public TSC/workgroup meeting starting in here in ~5 mins Sep 10 15:56:15 all welcome, of course :) Sep 10 15:56:47 * kergoth tries to remember what he wanted to bring up in said meeting Sep 10 15:59:54 ~startmeeting Sep 10 15:59:55 bluelightning: Error: "startmeeting" is not a valid command. Sep 10 16:00:16 #startmeeting Sep 10 16:00:16 Meeting started Tue Sep 10 16:00:16 2013 UTC. The chair is bluelightning. Information about MeetBot at http://wiki.debian.org/MeetBot. Sep 10 16:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic. Sep 10 16:00:39 * RP is here... Sep 10 16:01:33 * fray is here Sep 10 16:02:08 khem: ping Sep 10 16:02:09 * khem is here Sep 10 16:02:13 heh Sep 10 16:03:33 good morning all - thanks crofton for starting up meetbot Sep 10 16:03:59 first order is finding a meeting chair. Sep 10 16:04:05 have pinged koen btw Sep 10 16:04:06 I'll try to insert topic markers as necessary. The full agenda is at http://pastebin.com/CaRntQDZ Sep 10 16:04:19 yeah, all hail to the bot! Sep 10 16:04:24 :) Sep 10 16:04:41 #topic pick a chair Sep 10 16:04:46 (I think I did that right) :) Sep 10 16:04:46 fray: i've a spare chair Sep 10 16:05:14 fray I think so - crofton would know Sep 10 16:05:43 actually only chairs can choose #topics Sep 10 16:05:52 since there is are volunteers a plenty.. :) I guess I can do it.. :) Sep 10 16:06:05 fray: well volunteered :) Sep 10 16:06:12 #topic new issues Sep 10 16:06:34 I saw one issue (already on the agenda) mentioned on the mailing list(s). Does anyone have anything additional to suggest? Sep 10 16:06:38 (question is open for all) Sep 10 16:07:00 We could quickly mention default PROVIDES Sep 10 16:07:21 sounds like that would be good to mention under the status items Sep 10 16:07:37 fine with me Sep 10 16:07:44 PACKAGE_EXCLUDE should be mentioned as well.. Sep 10 16:08:06 any other new features/changes in the last month that people may have missed? Sep 10 16:08:13 _remove ? Sep 10 16:08:23 yes that would be good as well.. Sep 10 16:08:45 ok.. think about them while we move on.. (if anyone has any additional issues that come to mind, let us know or msg me and I'll make sure it gets addressed..) Sep 10 16:09:13 koen - welcome.. preliminary agenda - http://pastebin.com/CaRntQDZ Sep 10 16:09:20 anything to add, otherwise we'll move on to 3.. Sep 10 16:09:43 nope Sep 10 16:09:49 #topic lingering issues - role of the TSC Sep 10 16:09:56 On 3a, the TSC has pinged the board for elections Sep 10 16:10:07 can someone refresh our memory where this ended last time and what is left? Sep 10 16:10:11 there is also agreement to try and operate in a bit of a different way going forward Sep 10 16:10:27 which is what we're doing now Sep 10 16:11:23 ack Sep 10 16:11:25 So the TSC still exists and is able to make decisions but meets less often and instead nurtures a working group composed of hopefully a wider group of people Sep 10 16:11:58 with the working groups as people guiding and doing the work.. with the TSC setting direction, and resolving conflicts should they happen Sep 10 16:12:13 I mentioned it in the mailing list post, but in any case we're planning to have these public meetings on a monthly basis Sep 10 16:12:19 (maintainers will continue to be the primary resolver of conflicts in given areas fo course) Sep 10 16:13:24 so if there are no further comments/questions aboutt hat.. should we discuss working groups or other related items? Sep 10 16:14:57 * fray hears crickets.. Sep 10 16:15:17 From the proposed agenda, I see references to licensing information as one possible working group.. Sep 10 16:15:35 fray: I don't think the intention is to setup specific groups Sep 10 16:15:45 more to enable people to come forward to help work on specific issues Sep 10 16:15:50 will working groups also update report in this same meeting Sep 10 16:15:54 yes sorry.. that is what I meant.. Sep 10 16:15:59 task force might be a better way of describing it Sep 10 16:16:21 one possible group that could become a working group "style" task force.. is the SPDX integration effort that is ongoing by the University of Nebraska, Omaha (I hope I have that right) Sep 10 16:16:47 since I've been involved in that group I can give a little bit of status, see if anyoen has any other similar issues to report on.. Sep 10 16:17:43 recently the SPDX "support" has been merged into the system, what this support does is allows you to enable additional tasks that farm our licensing requestions to an external server interface. That interface can process the sources, and will return back SPDX formated licensing information for potentially later processing by the end user.. Sep 10 16:18:18 could be used for compliance, documentation, etc.. very early in the process still but the work is underway.. if you are interested let me know or Beth (pidge on IRC).. and we can direct you to the work in progress Sep 10 16:18:24 is there a common server like ntp servers available for this ? Sep 10 16:18:49 khem, that is expected to be part of the design.. the server will have an interface into fossology for processing as well as a database cache of already processed sources Sep 10 16:20:02 any other questions on SPDX work? Sep 10 16:20:22 OK, will there be a file level granularity option Sep 10 16:20:24 for checks Sep 10 16:20:33 or package level only Sep 10 16:20:47 yes, source file level granularity within the SPDX information, but the SPDX information will be attached to the recipe Sep 10 16:21:29 software not yet planned will need to be created to make the transition from the recipe to the package and eventually to a binary bill-of-materials like list.. Sep 10 16:21:50 its in the vision, but we need the file / server / database infrastructure first Sep 10 16:22:49 ok anyone else working on other similar projects, meta-oe / oe-core sync for example, and have status? Sep 10 16:24:19 fray: are we still talking about licensing or other OE-related projects in general? Sep 10 16:24:27 other oe projects in general.. Sep 10 16:24:51 (there might not be anything further to report at this time) Sep 10 16:25:06 seems like we need to more work getting people to report on their personal projects Sep 10 16:25:44 well, re oe-core / meta-oe overlayed recipes and bbappends, we're down to no bbappends but xserver-nodm-init is still overlayed in meta-oe, and there are a couple of recipes in meta-gnome that overlay recipes in OE-Core that I discovered the other day Sep 10 16:25:45 I'm not sure personal projects as much as things that are likely to benefit others, or affect a wider range of OE.. Sep 10 16:25:48 FWIW there are now meta-darwin and meta-mingw layers which support building the cross-canadian bits for those OSs Sep 10 16:26:08 I am looking for overlapping work Sep 10 16:26:18 I also fixed the fortran bits in master. Not sure what to do with the horrible hack I needed to make it build though Sep 10 16:26:40 the layer index at http://layers.openembedded.org received an update the other day, with a new navigation structure, some additional info and now indexes OE-Classic for reference Sep 10 16:26:47 why I fixed fortran I have no idea, it should have died 20 year aho Sep 10 16:26:58 :) Sep 10 16:27:00 ROFL Sep 10 16:27:03 RP: I thought you said you had a soft spot for it? :) Sep 10 16:27:22 ok.. unless anyone has anything else like that.. lets move on to eglibc.. Sep 10 16:27:42 bluelightning: I can only think I might have been wondering where its soft (weak) spot was to kill it and you misheard? ;-) Sep 10 16:27:53 RP: heh perhaps Sep 10 16:28:05 lol Sep 10 16:28:23 #topic lingering issues - eglibc Sep 10 16:28:44 Khem I defer this one to you.. any progress/plans on the kconfig, eglibc stuff? Sep 10 16:28:46 Fortran is pretty nice for numerical stuff. Not much use otherwise. Sep 10 16:28:50 merging back with glibc, main concern is the configuration bits? Sep 10 16:28:57 correct Sep 10 16:29:10 the configuration bits will cease being maintained in about a years time if I remember right.. Sep 10 16:29:21 first step to MAYBE getting it maintained is the work Khem had been doing Sep 10 16:29:33 fray: there is no change of getting it into glibc? Sep 10 16:29:38 chance Sep 10 16:30:06 at this time, I doubt it.. if the code can be improved, it can be brought up on the glibc list.. but be prepared to have your asbestos underwear on Sep 10 16:30:58 I know we left the last meeting wondering if anyone was actually using the work as it stands today.. Sep 10 16:31:21 if not, trying to either maintain it going forward (or getting it into glibc proper) might turn out to not be worthwhile Sep 10 16:31:25 it is used in poky-tiny and I know of people who have used that Sep 10 16:33:20 ok.. since there is nothing further.. we'll have to just keep up on this topic as we get closer to ELC-E.. if anyone has any questions, I strongly suggest you voice them on the oe-core and potentially even the eglibc-devel mailing list Sep 10 16:33:38 #topic lingering issues - janitor items Sep 10 16:33:51 sorry guys my home connection was lost Sep 10 16:33:56 with eglibc Sep 10 16:34:03 khem, ahh we'll backup then Sep 10 16:34:07 #topic lingering issues - eglibc Sep 10 16:34:25 I have plans to prepare kconfig patches for glibc Sep 10 16:34:31 sometime ELCE timeframe Sep 10 16:34:50 since eglibc will have its last release in 2.19 Sep 10 16:35:09 and from 2.20 onwards it will have to merge all eglibc changes into glibc Sep 10 16:35:39 ok.. that matches what I thought.. Sep 10 16:35:46 ok.. back to the next topic Sep 10 16:35:50 khem: thanks for working on that Sep 10 16:35:55 #topic lingering issues - janitor items Sep 10 16:36:15 * fray passes this to Bluelighting as I think he was leading the Janitor discussion a bit before Sep 10 16:36:18 I think we could really do with getting together a modern up to date list of items Sep 10 16:36:46 ya, multiple lists of maybe things to do isn't the best way to coordinate for those who would like to help Sep 10 16:37:02 I had an idea for janitor tasks - upgrades of non-critcal recipes. Example: I've been doing recent vim upgrades, 7.4 is now available but it doesn't need to be upgraded urgently Sep 10 16:37:03 I think we have consolidated few bbappends from meta-openembedded into core Sep 10 16:37:10 that bluelightning for that Sep 10 16:37:41 paulbarker: submit the patches if you havent already Sep 10 16:37:57 paulbarker ya, general upgrades are definitely janitor items.. as are things like compressing man pages, cleaning up code, etc.. Sep 10 16:37:59 paulbarker: I'm pretty sure such patches would be very welcome Sep 10 16:38:17 DESCRIPTION/SUMMARY improvements Sep 10 16:38:24 I don't have patches yet, it's a way down my todo list Sep 10 16:38:30 ya.. right now I think there is a very small group of people doing most of hte upgrades in oe-core.. (others in the other layers).. would be nice if we could get more people involved.. Sep 10 16:38:31 I think what we need to do is actually write down a decent list of suggestions for general janitor tasks Sep 10 16:38:52 we do have a category for this in the bugzilla if that helps Sep 10 16:38:56 most of these aren't the kind of things that are appropriate for bug reports so they'd have to go into a wiki page Sep 10 16:39:04 and an intro page on the wiki: http://openembedded.org/index.php/OpenEmbeddedJanitors Sep 10 16:40:14 we do now have a tool in the layer index for editing SUMMARY / DESCRIPTION, that's useful janitor type work Sep 10 16:40:21 if we could limit the interfaces to the bugzilla and the wiki it would probably be the best.. wiki for the nebulous things.. and the bugzilla for more concrete items.. Sep 10 16:40:34 right, sounds sensible to me Sep 10 16:40:38 that sounds good Sep 10 16:42:35 wasnt there a tool for recipe code checker Sep 10 16:42:51 Having one janitors page may be a good idea - maybe merge the OE and Yocto janitors pages together Sep 10 16:43:13 or at least put links to the other on each if they are both needed Sep 10 16:43:16 +1 Sep 10 16:43:16 secondly, when writing new recipes I find it useful to use vim plugins that are available in bitbake Sep 10 16:43:47 yes, we should pick one wiki and link from the other Sep 10 16:44:05 khem: there is recipe_sanity.bbclass but I think that's quite out of date by now Sep 10 16:44:42 (on mobile internet so don't wait for replies from me - connection is dodgy) Sep 10 16:44:43 right, it has _remove in its methods :) Sep 10 16:45:54 koen: RP fixed that I think Sep 10 16:46:23 about sanity, maybe add some checks on do_compile logs like Gentoo does and emit QA/warning about bad programming practices? Sep 10 16:46:24 ok.. so do we have someone (anyone here) that can lead the charge to get the wiki updated and synced? (they don't have to do the work.. just coordinate and ask others to if needed) Sep 10 16:46:47 I know there is little point, the sources are upstream Sep 10 16:47:40 fray: I'm afraid I'm maxed out with the usual patches and review :( Sep 10 16:47:49 I am as well.. Sep 10 16:47:52 much as I'd like to help :/ Sep 10 16:48:15 anyone can volunteer :) Sep 10 16:48:31 I can merge the two into one page and add a link, won't have time to do updating though Sep 10 16:48:37 if we don't get anyone to volunteer, then we need to take this to the mailing lists and see if someone not here is willing to step in.. Sep 10 16:48:54 paulbarker if you can take the lead on this.. just figure out what needs to be done.. we can beg for resources or help you out.. Sep 10 16:49:27 (not what janitor tasks need to be done, but what things to combine, and what others can help with either in wiki edits or gathering tasks) Sep 10 16:49:51 * fray won't discourage people from contributing janitor tasks either.. ;) Sep 10 16:50:02 paulbarker: would be great if you could send out an RFC for janitor tasks on the OE-Core mailing list Sep 10 16:50:17 ok.. 10 minutes left.. I'm going to jump around a bit Sep 10 16:50:26 ant_work: insane.bbclass already does a lot of that Sep 10 16:50:29 Yea I'll give it a go and post an RFC on the mailing list once they're merged a little Sep 10 16:50:41 oe-core status, mention the 4 items in the agenda.. then on to infrasturcture.. back to 4 if there is more time.. Sep 10 16:50:49 #topic projects in progress - status - oe-core release Sep 10 16:51:04 We're currently in a stabilization cycle, RP? Sep 10 16:51:08 The release is coming along but there are a lot of bugs in the bugzilla Sep 10 16:51:16 yes, now focusing on bug fixing Sep 10 16:51:26 sadly the bug count is rising, not falling Sep 10 16:51:57 We're doing what we can with the people available, any more help would be much appreciated Sep 10 16:52:08 if someone has a new feature (or one that didn't make it in yet).. estimate for the end of the stabilization cycle, and opening of new development is after ELC-E? Sep 10 16:52:41 do we have an easy way to list the oustanding bugs? Sep 10 16:52:49 fray: realistically new features won't get much attention until after then Sep 10 16:53:08 Crofton|work: bugzilla and search for open bugs in 1.5 ? Sep 10 16:53:19 as in a link we can publish? Sep 10 16:53:45 Crofton|work: you can make a url for any query Sep 10 16:54:42 basically, we should have such a link on the janitor page and publish the lists Sep 10 16:54:49 try this: Sep 10 16:54:51 https://bugzilla.yoctoproject.org/buglist.cgi?list_id=89293&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&version=1.5&version=1.5.1&version=1.5.2&target_milestone=1.5&target_milestone=1.5%20M1&target_milestone=1.5%20M2&target_milestone=1.5%20M3&target_milestone=1.5%20M4&target_milestone=1.5%20M5&target_milestone=1.5.1&target_milestone=1.5.2 Sep 10 16:55:01 * fray needs a URL shortener.. :P Sep 10 16:55:14 should be ok if you put it in a wiki link Sep 10 16:55:18 yup Sep 10 16:55:37 ok.. noting the clock is running out.. Sep 10 16:55:38 Crofton|work: on the yocto wiki we have the bugzilla plugin so you can have a dyanmic table Sep 10 16:55:47 default PROVIDES ... Sep 10 16:55:55 https://wiki.yoctoproject.org/wiki/Bug_Triage for example Sep 10 16:56:15 CUrrently we support "bitbake make-3.82" Sep 10 16:56:33 I sent out an patch explaining why this is problematic and that we should probably remove it Sep 10 16:56:48 if anyone has any strong feelings, please see that discussion Sep 10 16:57:07 sorry to rush.. PACKAGE_EXCLUDE Sep 10 16:57:37 recently new functionality that allows you to 'exclude' a package from being installed into the rootfs was added. What this really does is blacklist a package and prevents it (and anything depending on it) from being installed.. Sep 10 16:58:04 if a solution can't be found, an error is generated. This is just a piece of the puzzle for the many requests from people to "remove packages" from the rootfs images.. Sep 10 16:58:28 Also added were NO_RECOMMENDATIONS, and support for BAD_RECOMMENDATIONS when RPM packaging are enabled.. Sep 10 16:58:53 fray: all good improvements... Sep 10 16:58:57 NO_RECOMMENDATIONS should create a smaller filesystem by disabling any recommended packages -- note that kernel-modules are often recommended.. so this could cause issues unless you are not careful.. Sep 10 16:59:22 BAD_RECOMMENDATIONS previously existed in IPK support, and now does in RPM -- Deb is not supported, if someone can figure out how to make it work, we'd love the patch.. Sep 10 16:59:23 nice feature... Sep 10 16:59:34 ok.. _remove Sep 10 16:59:53 We now support a remove operator like append and prepend Sep 10 17:00:04 its the long awaited -= implementation Sep 10 17:00:29 * Jefro hears rejoicing in the streets Sep 10 17:00:33 the time its evaulated matches append and prepend which is why it wasn't called -= Sep 10 17:00:35 :) Sep 10 17:00:56 we also found and fixed a bug in it recently Sep 10 17:01:12 so hopefully people will find it useful Sep 10 17:01:22 one other oe-core release item just came to mind.. Sep 10 17:01:27 PR Server, and processing hangs.. Sep 10 17:01:38 ah, we've fixed several of those Sep 10 17:01:39 recently a number of PR server issues and initial processing hangs have been corrected Sep 10 17:01:45 and massively sped up the PR server Sep 10 17:01:58 if anyone gets any hangs or odd behavior from the PR server, we really need to know ASAP.. (preferabbly with reproducers) Sep 10 17:01:59 to the point it didn't write any changes to disk, oops :) Sep 10 17:02:13 that is a good way to speed it up.. ;) Sep 10 17:02:16 that is fixed now and we kept the speedup Sep 10 17:02:52 ok.. we are a couple minutes over.. I'd like to get to infrastucture before calling this done.. Sep 10 17:02:58 #topic infrastructure Sep 10 17:03:14 koen: I meant this: an invitation to open a bug upstream http://bugs.mysql.com/bug.php?id=60247 Sep 10 17:03:15 khem or anyone else.. do you have an infrastructure update? Sep 10 17:03:33 Michael has said that the YP-backed infrastructure is about to have significant additional bandwidth added, FWIW Sep 10 17:03:49 nothing from me Sep 10 17:04:16 do we need to keep the 5a / 5b on the future agendas? or has the oe.org flooding and patchwork spam been dealt with? Sep 10 17:04:17 nothing from me Sep 10 17:04:23 if you have any infra issues, please copy the board Sep 10 17:04:24 bluelightning: +1 Sep 10 17:04:29 we can readd if there are issues Sep 10 17:04:43 ok.. we'll remove them.. and re-add if necessary.. Sep 10 17:04:48 khem: no word on more general OE autobuilders? Sep 10 17:05:09 bluelightning: I think Martin is already using them Sep 10 17:05:13 right, I guess Martin does cover a lot of that Sep 10 17:05:44 I will check with Tom if we can create a general queue Sep 10 17:05:55 but I think if we are able to grok the patchwork Sep 10 17:06:07 for incoming patches and launch builds that will do it Sep 10 17:06:23 since we keep patchwork clean with meta-openembedded this seems possible Sep 10 17:06:36 khem: even too much... Sep 10 17:06:58 khem: patches are almost immediately archived (bundled Sep 10 17:07:17 then its already in works Sep 10 17:07:22 iirc JaMa changed the behavior Sep 10 17:07:34 * RP needs to head afk Sep 10 17:07:41 same here.. Sep 10 17:07:44 ant_work: isn't it good? no queue = no problems :) Sep 10 17:07:44 * khem too Sep 10 17:07:46 I'm going to need to call a close to the meeting.. Sep 10 17:08:16 if you have additional topics, comments, concerns.. please use the mailing lists, or feel free to email the TSC folks and we'll get your comments brought to the group and community at large (if appropriate) Sep 10 17:08:25 * fray looks over at jefro on how to close the meeting w/ the bot Sep 10 17:08:29 excellent meeting folks Sep 10 17:08:33 crofton-bot has to close it Sep 10 17:08:34 Jefro: Error: "has" is not a valid command. Sep 10 17:08:36 so, what's the schedule for this meeting? Sep 10 17:08:46 who type #startmeeting? Sep 10 17:08:50 crofton-bot #endmeeting Sep 10 17:08:50 type #endmeeting Sep 10 17:08:50 Jefro: Error: "#endmeeting" is not a valid command. Sep 10 17:09:00 crofton has to close it, I can't Sep 10 17:09:05 #endmeeting Sep 10 17:09:06 Meeting ended Tue Sep 10 17:09:05 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Sep 10 17:09:06 Minutes: oe/2013/oe.2013-09-10-16.00.html Sep 10 17:09:06 Minutes (text): oe/2013/oe.2013-09-10-16.00.txt Sep 10 17:09:06 Log: oe/2013/oe.2013-09-10-16.00.log.html Sep 10 17:09:09 sorry Sep 10 17:09:10 :) Sep 10 17:09:12 :) Sep 10 17:09:14 :) Sep 10 17:09:15 Crofton|work - I think you did ;) Sep 10 17:09:21 bluelightning, did Sep 10 17:09:26 who wants the files? Sep 10 17:09:36 jefro needs them for the TSC records.. Sep 10 17:09:37 wiki wants them Sep 10 17:10:01 I need to get with ka6sox aobut setting something upI owe him a key Sep 10 17:10:35 again, when is the next meeting? Sep 10 17:10:44 yup Sep 10 17:10:46 I"m waiting :) Sep 10 17:10:58 :) Sep 10 17:11:16 denix the next meeting will be either 24 sept or 1 oct Sep 10 17:11:22 the next public meeting, that is Sep 10 17:11:28 Jefro: thanks Sep 10 17:11:30 ka6sox, pm we the address to send it to Sep 10 17:11:47 sure I will send "we" the address Sep 10 17:11:58 :) Sep 10 17:12:14 you guys are speaking Scottish already Sep 10 17:12:22 Aye Sep 10 17:12:33 but thats wee Sep 10 17:12:38 Jefro, I prefer pirate.. Ar' Sep 10 17:12:41 like "wee little dram" Sep 10 17:13:01 fray what about Scottish pirate? Sep 10 17:13:13 Aye Ar' Sep 10 17:13:13 * ka6sox expects XorA is laughing about now. Sep 10 17:13:14 :) Sep 10 17:13:41 ka6sox: little? disappointing. Sep 10 17:14:47 rburton, its early here... Sep 10 17:14:51 ok mails sent Sep 10 17:14:54 I must go ride Sep 10 17:15:48 ka6sox: ok, fair enough Sep 10 17:16:10 when the sun is under the yardarm...then we start bending an elbow. Sep 10 17:16:57 I need to go change trains. I'll try to be on a real network connection for the next meeting! Sep 10 17:50:46 * JaMa way too late for TSC meeting :/ but got racing license for go karts! :) Sep 10 18:10:44 Crofton|work, ping when you get back Sep 10 20:16:48 hi all Sep 10 20:17:52 hi pb_ Sep 10 21:00:56 ka6sox: everyone at ELCE should walk into a pub and loudly proclaim "I am a Sassenach and you Jocks owe me a free pint" to claim their free pint! Sep 10 21:01:49 XorA, Works for me! Sep 10 21:03:35 *disclaimer, the pint may be comprised of your own blood Sep 10 21:04:05 * hollisb googles Sassenach Sep 10 21:04:51 translate "I am English give me a free pint" Sep 10 21:24:48 XorA: only a pint? Sep 10 21:25:11 RP: :-D Sep 10 21:27:51 is there a similar word for American? (or is it just "American"?) Sep 10 21:29:40 There is a nice Geordie/Scottish word for friend, "hinny". Good one to try down the pub too :) Sep 10 21:30:02 The online translations are dubious at best :) Sep 10 21:35:27 * XorA wonders how many fights we can start with dodgy translations **** ENDING LOGGING AT Wed Sep 11 02:59:59 2013