| 00:35.18 | *** join/#oe Vutral (ss@mirbsd/special/Vutral) |
| 00:40.51 | *** join/#oe nullpuppy (~dustin@freematrix/staff/nullpuppy) |
| 01:24.19 | *** join/#oe andyross (~andy@c-67-171-188-207.hsd1.or.comcast.net) |
| 02:01.53 | *** join/#oe silviof1 (~silviof@unaffiliated/silviof) |
| 02:12.51 | *** join/#oe liuyq (~liuyq0307@221.123.128.226) |
| 02:25.00 | *** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy) |
| 02:36.11 | *** join/#oe andyross (~andy@c-67-171-188-207.hsd1.or.comcast.net) |
| 03:14.55 | *** join/#oe toobluesc (~nitro@c-50-136-226-78.hsd1.ca.comcast.net) |
| 04:19.26 | *** join/#oe andyross (~andy@c-67-171-188-207.hsd1.or.comcast.net) |
| 04:25.58 | *** join/#oe zenlinux (~sgarman@c-50-139-96-211.hsd1.or.comcast.net) |
| 05:45.54 | *** join/#oe kbart (~KBart@213.197.143.19) |
| 06:06.08 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:08.05 | *** join/#oe Zagor (~bjst@sestofw01.enea.se) |
| 06:08.05 | *** join/#oe Zagor (~bjst@rockbox/developer/Zagor) |
| 06:10.57 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:17.59 | *** join/#oe blitz00 (~stefans@192.198.151.36) |
| 06:17.59 | *** join/#oe blitz00 (~stefans@unaffiliated/blitz00) |
| 06:24.24 | *** join/#oe zecke (~ich@p5099b351.dip0.t-ipconnect.de) |
| 06:25.21 | *** join/#oe rsalveti (~rsalveti@unaffiliated/rsalveti) |
| 06:26.11 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
| 06:27.08 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:33.34 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:35.12 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:36.51 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:38.30 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:40.13 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:41.52 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:43.28 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:45.01 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:46.40 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:48.16 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:49.58 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:51.37 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:53.17 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:54.59 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:56.34 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:56.59 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
| 06:58.09 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 06:59.51 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 07:01.28 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 07:03.05 | *** join/#oe shawn187 (~Tiberius@unaffiliated/shawn156) |
| 07:03.42 | *** join/#oe lamikr (lamikr@nat/nokia/x-rreinhjygzmluqys) |
| 07:24.44 | *** join/#oe rob_w (~rob@unaffiliated/rob-w/x-1112029) |
| 07:25.20 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
| 07:26.38 | mckoan | good morning |
| 07:27.33 | *** join/#oe ant_work (~ant@host54-128-static.10-188-b.business.telecomitalia.it) |
| 07:33.02 | *** join/#oe stefan_schmidt_w (~stefan_sc@82.43.26.66) |
| 07:35.57 | *** join/#oe silvio_l_ (~silvio@93-57-17-124.ip162.fastwebnet.it) |
| 07:36.47 | silvio_l_ | morning all |
| 07:37.55 | mckoan | hi silvio_l_, all |
| 07:39.17 | *** join/#oe liuyq (~liuyq0307@221.123.128.226) |
| 07:39.30 | silvio_l_ | hi mckoan |
| 07:46.10 | *** join/#oe flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 07:48.38 | *** join/#oe mbelisko (~mbelisko@81.89.61.168.vnet.sk) |
| 07:50.38 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 07:50.46 | *** join/#oe dos1 (~dos@unaffiliated/dos1) |
| 07:56.25 | silviof1 | morning #oe |
| 08:01.02 | bluelightning | morning silviof, all |
| 08:05.05 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
| 08:23.43 | *** join/#oe panda84kde (~diego@static-217-133-170-65.clienti.tiscali.it) |
| 08:29.01 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
| 09:07.55 | *** join/#oe Stygia (~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk) |
| 09:31.17 | *** join/#oe eren (~eren@unaffiliated/eren) |
| 09:48.54 | *** join/#oe blitz00 (~stefans@unaffiliated/blitz00) |
| 10:04.44 | *** join/#oe Stygia (~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk) |
| 10:16.02 | *** join/#oe morphis (~morphis@fiona.nas-admin.org) |
| 10:26.47 | *** join/#oe tasslehoff (~tasslehof@77.40.182.98) |
| 11:24.03 | *** join/#oe hillct (~hillct@c-24-34-200-20.hsd1.ma.comcast.net) |
| 11:26.55 | *** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginmedia.com) |
| 11:33.41 | *** join/#oe Stygia (~gmpsaifi@5.63.151.36) |
| 11:44.48 | *** join/#oe phdeswer (~phdeswer@194.157.27.2) |
| 12:05.42 | *** join/#oe joeythesaint (~jjm@128.224.252.2) |
| 12:12.10 | ndec | hi. why are bitbake commits not sent to openembedded-commits@ mailing list? |
| 12:12.33 | ndec | i was monitoring the list to see when my bitbake patch would be merged, and just noticed that. |
| 12:14.50 | ndec | bluelightning: my bitbake patch for run.do_xxx symlink was merged in master, do you think it could be backported to dylan? when i wrote the patch it applied to both master and dylan branch. i suspect it would still apply. |
| 12:14.50 | ndec | a672b39 build.py: create symlink for run.do_xxx scripts |
| 12:17.38 | Crofton|work | ndec, because OE is not bitbake :) |
| 12:17.43 | Crofton|work | or ebcuase no one asked |
| 12:17.57 | ndec | well, meta-oe commits are sent there too. |
| 12:18.07 | Crofton|work | then reason #2 |
| 12:18.10 | ndec | ;-) |
| 12:18.21 | ndec | maybe i fixed #2 just now, then? |
| 12:18.59 | Crofton|work | I'd ask in the bitbake list |
| 12:19.28 | Crofton|work | I do not think anyone would have a problem adding bitbake commits |
| 12:19.31 | *** join/#oe liuyq (~liuyq0307@221.123.128.226) |
| 12:19.38 | Crofton|work | the volume should not impact list traffic |
| 12:22.16 | *** join/#oe hillct (~hillct@c-24-34-200-20.hsd1.ma.comcast.net) |
| 12:27.14 | *** join/#oe shoragan (~jlu@debian/developer/shoragan) |
| 12:42.53 | bluelightning | ndec: so, generally we backport only bugfixes |
| 12:43.23 | bluelightning | ndec: we might be able to take this one as it's fairly trivial, I'll add it to my list anyway |
| 12:43.34 | ndec | ah. ok. thx. |
| 13:03.25 | *** join/#oe ldnunes (~ldnunes_@187.23.155.55) |
| 13:12.56 | ant_work | bluelightning: JaMa: please be so kind to merge the klibc changes. There is an endianness bug with mips and 3.10 headers exposed by the recipe. I've gathered some attention by the maintainers, you know, it's sunny outside and they will disappear soon as snow ;) |
| 13:23.58 | *** join/#oe kbart (~KBart@213.197.143.19) |
| 13:29.29 | bluelightning | ant_work: looks like JaMa is gone; I can do it if you like |
| 13:30.19 | ant_work | heh, he left after sending that scary queue of 66 patches :p |
| 13:37.17 | *** join/#oe hillct (~hillct@c-24-34-200-20.hsd1.ma.comcast.net) |
| 13:40.16 | *** join/#oe hillct (~hillct@c-24-34-200-20.hsd1.ma.comcast.net) |
| 13:46.22 | *** join/#oe Stygia (~gmpsaifi@cpe-198.144.156.144.ca.yorkinet.com) |
| 13:49.00 | *** join/#oe Noor (~noor@110.93.212.98) |
| 13:51.51 | chouimat | morning |
| 13:54.17 | bluelightning | morning chouimat |
| 13:54.35 | bluelightning | ant_work: I've merged the meta-initramfs changes (3 patches) |
| 13:54.59 | bluelightning | ant_work: havent done the meta-filesystems one, will need to be the maintainer of that layer |
| 13:59.33 | *** join/#oe Stygia (~gmpsaifi@x1-6-00-21-9b-e8-d0-5a.k663.webspeed.dk) |
| 14:16.15 | ant_work | bluelightning: many thx. I'll ping koen |
| 14:16.57 | bluelightning | ant_work: I think it's JaMa for that layer |
| 14:17.31 | ant_work | ok |
| 14:17.33 | *** join/#oe acidfu (~nib@24.37.17.210) |
| 14:17.33 | *** join/#oe acidfu (~nib@unaffiliated/acidmen) |
| 14:34.45 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 14:46.14 | *** join/#oe chouimat (~mathieu@CPE2cb05d9c6d26-CM602ad09323c6.cpe.net.cable.rogers.com) |
| 14:46.26 | *** join/#oe chouimat (~mathieu@kde/developer/chouinard) |
| 14:46.31 | *** join/#oe pabigot (~pab@c-66-41-60-82.hsd1.mn.comcast.net) |
| 14:49.44 | *** join/#oe kristoffer (~kristoffe@c-1ad8e555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 14:51.18 | *** join/#oe JaMa (~martin@ip-62-24-80-145.net.upcbroadband.cz) |
| 15:00.53 | *** join/#oe nitink (nitink@nat/intel/x-zjlafshrvlzbfmkb) |
| 15:01.30 | *** join/#oe Jefro (~jefro@50-0-152-82.dedicated.static.sonic.net) |
| 15:01.44 | *** join/#oe Crofton (~balister@pool-71-171-32-225.ronkva.east.verizon.net) |
| 15:02.04 | *** join/#oe hollisb (~hollisb@nat-wv.mentorg.com) |
| 15:02.30 | *** join/#oe bluelightning_ (~paul@83.217.123.106) |
| 15:02.30 | *** join/#oe bluelightning_ (~paul@pdpc/supporter/professional/bluelightning) |
| 15:04.35 | bluelightning | Stygia: for future patches can you add [meta-oe] in the subject line i.e. --subject-prefix="meta-oe][PATCH" |
| 15:04.49 | bluelightning | Stygia: or meta-perl in this case |
| 15:07.16 | Stygia | bluelightning, Oh. Yea, sure. |
| 15:07.31 | Stygia | bluelightning, Aah, hmm. This means it evades people's mail filters... yea, sorry. |
| 15:08.59 | JaMa | Stygia: I already wrote it in review of your first patch |
| 15:09.39 | JaMa | Stygia: also your patches doesn't seem to be final version, you add recipe and immediately remove it in next patch |
| 15:10.26 | Stygia | JaMa, Hmm? I don't remove them AFAIK? |
| 15:10.58 | JaMa | d .../perl-module-test-harness_3.28.bb | 18 ++++++++++++++++++ |
| 15:10.58 | JaMa | <PROTECTED> |
| 15:11.04 | JaMa | <PROTECTED> |
| 15:11.04 | JaMa | <PROTECTED> |
| 15:11.22 | JaMa | <PROTECTED> |
| 15:11.33 | Stygia | JaMa, God dammit. I deleted the repo and cloned it again to avoid those old patches that I never pushed. |
| 15:11.40 | Stygia | JaMa, How the hell did they still get in there... |
| 15:11.46 | JaMa | <PROTECTED> |
| 15:12.56 | Stygia | JaMa, Weird... Well, fuck. Those weren't supposed to be part of this at all. |
| 15:13.12 | bluelightning | Stygia: I'd honestly suggest getting familiar with git rebase -i origin/master |
| 15:13.14 | JaMa | well it's what you sent to ML |
| 15:13.26 | Stygia | bluelightning, I probably should yea... |
| 15:13.42 | bluelightning | Stygia: if you check out a new branch beforehand you can play around with it and not risk losing anything |
| 15:13.50 | Stygia | JaMa, Hmm so it seem anyway. |
| 15:14.10 | Stygia | bluelightning, Hmm right, but I deleted all of my meta-openembedded repo, and I figured that would reset everything I did earlier. |
| 15:14.20 | Stygia | Somehow it still knows about the incomplete versions of my recipes and such... |
| 15:14.29 | Stygia | Well. That was definitively unintended. |
| 15:14.37 | bluelightning | Stygia: hmm, I'm not quite sure how that has happened, but in any case deleting isn't necssary |
| 15:15.01 | Stygia | bluelightning, Yea I know there's a better way, I just didn't want to bother - I deleted it and cloned it again... so I figured that I had a completely clean setup here. |
| 15:15.38 | bluelightning | Stygia: I would have thought that would have done it yes, I can only assume some sort of directory mix-up |
| 15:16.14 | Stygia | bluelightning, I suppose. I'm 100% I deleted meta-openembeddded and cloned it again. |
| 15:16.17 | Stygia | Ah, either way. |
| 15:16.24 | Stygia | From now on, I'll use git status to see what I've done before I send-email. |
| 15:16.34 | bluelightning | Stygia: honestly though "git rebase -i" is so useful it'll be worth the time to learn how to use it - at least when I did my git productivity went up hugely |
| 15:16.34 | Stygia | That'll show me if there's some rename or something else unwelcome, yea? |
| 15:16.58 | Stygia | bluelightning, Yes I know. Learning to use git properly is on my list of things... unfortunately not at the top. |
| 15:17.03 | bluelightning | well git status only tells you what branch you're on and what hasn't yet been committed |
| 15:17.45 | Stygia | bluelightning, But if it says, "New file: ..." that _should_ mean I can safely commit it assuming the recipe itself is good, yea? |
| 15:18.01 | bluelightning | Stygia: yes |
| 15:18.09 | Stygia | bluelightning, Then it servers my purpose for now. :) |
| 15:18.16 | Stygia | bluelightning, But yea. I know. I suck at git and I should learn. |
| 15:18.23 | bluelightning | Stygia: ok |
| 15:18.27 | Stygia | But for now I'd rather just push these patches and get back to work. :) |
| 15:19.00 | bluelightning | Stygia: I'd say if you have time for nothing else, definitely play around with git rebase -i :) |
| 15:19.17 | bluelightning | I'll get down off my soapbox now :) |
| 15:19.19 | Stygia | bluelightning, Yup, I'll note that down. |
| 15:30.43 | kergoth | also, don't just add [meta-perl] or whatever, keep the PATCH bit too, please :) |
| 15:34.55 | Stygia | kergoth, Ah, so... [meta-perl][PATCH] should be the prefix? |
| 15:35.17 | Stygia | Ah shit, I missed that in bluelightning's message to me originally... dammit. |
| 15:35.30 | kergoth | indeed, yes. --subject-prefix='meta-perl][PATCH' or so |
| 15:35.36 | kergoth | not a problem, just a reminder for the future |
| 15:35.44 | kergoth | uses the [PATCH bit in his filters too :) |
| 15:35.47 | Stygia | kergoth, Alright... Well now it's in my bash history, heh. |
| 15:36.11 | Stygia | kergoth, That's how I usually remember long commands. |
| 15:38.07 | kergoth | heh, a friend of mine set up a shell prompt command to email him new shell history entries in blocks, so even bits that are outside the maximum history size get archived, for that reason. seemed a bit overly complex to me, but interesting nonetheless |
| 15:39.31 | Gaston|Home | Completely off topic. Isn't there like a sequence to store your own work then rebase and readd your work? Like git stash, git rebase ... ?? |
| 15:40.36 | kergoth | if you have just local changes, thats what stash is for. if you have multuiple commits, you don't need a stash, you can put it on a branch |
| 15:42.22 | Gaston|Home | yeah, but someone said it was useful for collecting multiple changes in one commit, can't remember exactly how the workflow went |
| 15:42.31 | Gaston|Home | into one* |
| 15:43.14 | kergoth | yes, rebase -i lets you rearrange, merge, etc commits |
| 15:43.22 | kergoth | but there's no need for stash for that, rebase alone does htat job just fine |
| 15:43.46 | kergoth | stash is just for temporarily setting aside local, non-checked-in changes, usually when switching branches or updating your local branch from upstream before checking in |
| 15:44.27 | Gaston|Home | very good explanation, thanks ! |
| 15:45.03 | Gaston|Home | looks like git stash pop is the reversal |
| 15:45.23 | kergoth | indeed |
| 15:47.37 | bluelightning | "git stash list" and "git stash show -p" become useful as you start to rely on stashing more and more :) |
| 15:51.10 | Gaston|Home | As I interprete kergoth I'm a bad boy that don't commit. I should really find a better workflow instead of relying on stash. |
| 15:52.12 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
| 15:59.45 | *** join/#oe andyross (~andy@c-67-171-188-207.hsd1.or.comcast.net) |
| 16:03.27 | Gaston|Home | It is very tempting to misuse stash and base a local workflow off it. Reading the examples almost encourages misuse due to limited knowledge of other ways: https://www.kernel.org/pub/software/scm/git/docs/git-stash.html |
| 16:05.50 | bluelightning | the git docs are only about 50% useful IMO :/ |
| 16:08.05 | ant_work | JaMa: are you the ad interim maintainer of meta-filesystems? |
| 16:09.36 | JaMa | honestly I don't know :) I was waiting for Hongxu to ack that patch before merging it (the same for meta-perl patches) |
| 16:10.53 | *** join/#oe galak (~galak@99-51-185-173.lightspeed.austtx.sbcglobal.net) |
| 16:16.20 | bluelightning | ant_work: ping with CC to Hongxu I would suggest |
| 16:17.25 | ant_work | see, koen appears as maintainer |
| 16:17.33 | ant_work | well, of the recipe |
| 16:17.54 | ant_work | I suppose he can remove it |
| 16:21.07 | *** join/#oe awozniak (~awozniak@74.82.132.35) |
| 16:25.00 | JaMa | bluelightning: btw I have small fix for mariadb transition (PROVIDES in mariadb-native) |
| 16:25.54 | JaMa | bluelightning: and there is small problem in incremental builds, because mysql5 isn't cleared from sysroot before mariadb is built, so all header files are still from mysql5 not mariadb |
| 16:26.25 | JaMa | not only header files all files with the same name and path |
| 16:26.27 | bluelightning | JaMa: I'm ok with the former, feel free to apply that |
| 16:26.33 | bluelightning | JaMa: is there any way to actually fix the latter? |
| 16:27.10 | JaMa | I can only think of implementing my suggestions from https://bugzilla.yoctoproject.org/show_bug.cgi?id=4102 |
| 16:27.28 | JaMa | alias REPLACES variables |
| 16:31.46 | *** join/#oe eren (~eren@unaffiliated/eren) |
| 16:32.41 | bluelightning | JaMa: right, unfortunately we don't have that mechanism at the moment though |
| 16:33.53 | bluelightning | JaMa: that bug is marked RESOLVED FIXED, is that really correct? |
| 16:34.17 | bluelightning | or do we need a separate feature request? |
| 16:35.08 | JaMa | bluelightning: well I'm not sure if we want to bump OELAYOUT_ABI for every recipe rename or package_arch change |
| 16:35.36 | bluelightning | er, no, that would be excessive |
| 16:35.45 | JaMa | with more layers I see changes like this quite often |
| 16:36.10 | JaMa | usually it's easy for me to spot it and manually clean what's needed to be cleaned |
| 16:36.30 | JaMa | but for new commers it just means that incremental builds aren't reliable |
| 16:38.10 | *** join/#oe bluelightning_ (~paul@83.217.123.106) |
| 16:38.10 | *** join/#oe bluelightning_ (~paul@pdpc/supporter/professional/bluelightning) |
| 16:39.31 | *** part/#oe pabigot (~pab@c-66-41-60-82.hsd1.mn.comcast.net) |
| 16:40.07 | bluelightning_ | JaMa: I know; FWIW I would like to see a mechanism present that would help solve this at least where it's practical |
| 16:40.25 | JaMa | agreed |
| 16:40.41 | bluelightning_ | something we can look at in 1.6 |
| 16:40.53 | JaMa | ant_work: did you forgot to Cc Hongxu in last oe-devel e-mail? |
| 16:41.34 | ant_work | I really didn't see his e-mail as maintainer |
| 16:42.31 | bluelightning_ | JaMa: CCs get dropped on mails sent out by the list server, so not necessarily |
| 16:42.52 | ant_work | JaMa: no, cc: Hongxu Jia <hongxu.jia@windriver.com> |
| 16:43.08 | ant_work | bluelightning_: yes |
| 16:43.51 | JaMa | aha |
| 16:44.57 | *** join/#oe acidfu (~nib@24.37.17.210) |
| 16:44.57 | *** join/#oe acidfu (~nib@unaffiliated/acidmen) |
| 16:45.50 | bluelightning_ | it's confusing, but I suspect there's no way for the list server to show CC on the email it sends out or it would CC the person again :) |
| 16:46.07 | JaMa | true |
| 16:46.28 | bluelightning_ | it's funny I've been using mailing lists for years but I only noticed that recently |
| 16:47.20 | JaMa | I was even thinking that I've seen Cc: headers there, but that was probably in e-mails sent by me :) |
| 16:49.14 | bluelightning | if the CC is the mailing list itself it'll show up, it seems |
| 16:49.31 | *** join/#oe hno (~hno@squid/developer/hno) |
| 16:51.25 | hno | how do I create a snapshot of all sources used for building a specific image? Need this for GPL compliance reasons. |
| 16:54.46 | Crofton|work | I think you need archiver.bbclass, but I am not certain how to use it |
| 16:55.24 | bluelightning | there's a section of the manual on that |
| 16:55.53 | bluelightning | the Yocto Project dev manual that is |
| 16:55.54 | bluelightning | http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-open-source-license-compliance-during-your-products-lifecycle |
| 16:55.57 | bluelightning | hno: ^ |
| 16:58.03 | ant_work | bbl |
| 17:06.52 | *** join/#oe mr_science (~sarnold@gentoo/developer/nerdboy) |
| 17:08.11 | *** join/#oe c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) |
| 17:09.12 | mr_science | i wonder what he's like at home... |
| 17:12.09 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 17:15.53 | hno | bluelightning, thanks, Just found the same via another user hinting about archiver.bbclass |
| 17:21.13 | *** join/#oe _chase_ (~a0271661@nat/ti/x-jgkcczhapxiogsmd) |
| 17:32.47 | *** join/#oe espiral (~maze@unaffiliated/espiral) |
| 17:54.38 | *** join/#oe _chase_1 (~a0271661@nat/ti/x-qezohvhvazzlqgne) |
| 17:55.33 | *** part/#oe _chase_1 (~a0271661@nat/ti/x-qezohvhvazzlqgne) |
| 18:06.00 | *** join/#oe soltys (soltys@soltys.info) |
| 18:06.32 | *** join/#oe soltys (soltys@soltys.info) |
| 18:07.13 | *** join/#oe soltys (soltys@soltys.info) |
| 18:23.59 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 18:24.19 | JaMa | heh looks like axis is using OE too :) |
| 18:37.39 | *** join/#oe zecke (~ich@91-65-247-193-dynip.superkabel.de) |
| 18:47.09 | Crofton|work | axis? |
| 18:47.14 | Crofton|work | the webcam people? |
| 18:47.38 | mckoan | JaMa: unbelievable! |
| 18:48.25 | *** join/#oe pabigot (~pab@c-66-41-60-82.hsd1.mn.comcast.net) |
| 18:48.50 | mckoan | JaMa: how did you know that? |
| 18:49.34 | JaMa | got e-mail from their buildbot :) |
| 18:49.58 | JaMa | eren: ^ |
| 18:50.05 | *** join/#oe shoragan (~jlu@debian/developer/shoragan) |
| 18:52.23 | Crofton|work | :) |
| 18:52.23 | mckoan | JaMa: BTW, I suppose you will be at ELCE this year, don't you? |
| 18:52.52 | JaMa | yes, hotel and flight is already booked |
| 18:53.08 | JaMa | only ELCE registration is remaining :) |
| 18:53.20 | mckoan | JaMa: but aren't you in Edi? |
| 18:53.26 | *** join/#oe florian (~fuchs@sign-4db6b0c4.pool.mediaWays.net) |
| 18:53.26 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
| 18:53.39 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 18:53.42 | JaMa | florian: xserver-common ping |
| 18:53.45 | mckoan | JaMa: damn! He's XorA |
| 18:54.28 | *** join/#oe eFfeM (~frans@c73189.upc-c.chello.nl) |
| 18:55.17 | mckoan | unfortunately Yocto day has been added the day before elce, so I had to book an hotel more for the 22 only |
| 18:56.30 | florian | re |
| 18:56.35 | florian | JaMa: thx |
| 19:02.50 | *** join/#oe ksharp (82a43e9d@gateway/web/freenode/ip.130.164.62.157) |
| 19:03.15 | Crofton|work | anyone know much about using external sourcery toolchains? |
| 19:04.07 | Crofton|work | should external-sourcery-toolahin work in dylan or is there a better way |
| 19:04.14 | Crofton|work | hopes kergoth is awake :) |
| 19:13.49 | *** join/#oe nitink (nitink@nat/intel/x-tfyaffalyjzwbqlm) |
| 19:15.05 | *** join/#oe amarsman (~marsman@195-241-212-143.ip.telfort.nl) |
| 19:15.43 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
| 19:18.29 | Crofton|work | can anyone explain why/when you would use meta-sourcery over external-sourcery-toolchain? |
| 19:18.57 | fray | meta-sourcery includes better support for tunes, multilibs and other tidbits.. |
| 19:18.59 | kergoth | the one in oe-core isn't really maintained right now |
| 19:19.03 | fray | I really think the external-sourcery should be removed |
| 19:19.14 | Crofton|work | ah |
| 19:19.25 | kergoth | that reminds me, i need to finish reviewing seebs's multilibs pull request |
| 19:19.32 | Crofton|work | A friend of mine is using the one in oe-core |
| 19:19.40 | Crofton|work | I've pointed him a meta-sourcery |
| 19:19.46 | Crofton|work | should it work with Dylan? |
| 19:20.56 | kergoth | yep, should. |
| 19:21.50 | Crofton|work | thanks kergoth |
| 19:22.06 | Crofton|work | I also suggested they can use the issue tracker there |
| 19:28.49 | *** join/#oe eren` (~eren@unaffiliated/eren) |
| 19:39.28 | *** part/#oe pabigot (~pab@c-66-41-60-82.hsd1.mn.comcast.net) |
| 19:43.58 | *** join/#oe ant_home (~andrea@87.13.50.37) |
| 19:56.14 | *** join/#oe hillct (~hillct@c-24-34-200-20.hsd1.ma.comcast.net) |
| 20:07.48 | *** join/#oe zecke (~ich@91-65-247-193-dynip.superkabel.de) |
| 20:15.13 | *** join/#oe eren (~eren@unaffiliated/eren) |
| 20:41.22 | *** join/#oe jmpdelos (~polk@71-34-156-120.clsp.qwest.net) |
| 20:51.02 | *** join/#oe dijenerate (~dijenerat@65.48.221.118) |
| 20:53.37 | *** join/#oe _chase_ (~a0271661@nat/ti/x-coxjlggrrbgcenbk) |
| 22:07.06 | *** join/#oe shawn196 (~Tiberius@unaffiliated/shawn156) |
| 22:18.45 | zibri | jama: haha... sorry about the axis buildbot mails... a bit embarassing. i disabled all mail notifications for the time being. |
| 22:22.59 | JaMa | zibri: no problem at all, at least we know another company using OE :) |
| 22:23.08 | zibri | jama: :) |
| 22:23.30 | JaMa | and I like the name of that layer :) |
| 22:23.31 | zibri | (it was all a trick to promote axis' use of oe!) |
| 22:24.10 | *** join/#oe Daemon404 (~who_knows@host86-143-213-41.range86-143.btcentralplus.com) |
| 22:24.17 | zibri | jama: heh, our line manager thought poky was called porky during a meeting, and the name stuck :) |
| 22:24.35 | *** join/#oe Daemon404 (~who_knows@pdpc/supporter/student/Daemon404) |
| 22:24.39 | JaMa | :) |
| 22:25.10 | JaMa | reminds me manager in previous job who called meeting to decide whether to use SuSe or ReadHead |
| 22:25.58 | zibri | :D |
| 22:26.16 | JaMa | until now I don't know if it was honest mistake or funny nickname for less favourite option :) |
| 22:37.55 | ant_home | JaMa, another discovery...klcc-cross is machine specific as it is. Somehow rebuilds in sysroot so I could not see failures rebuilding armv5te after qemuarm |
| 22:38.16 | ant_home | jeez |
| 22:46.51 | *** join/#oe blindvt (~brf@91-119-70-34.dynamic.xdsl-line.inode.at) |
| 22:51.12 | *** join/#oe mario-goulart (~user@email.parenteses.org) |
| 22:53.36 | *** join/#oe jkridner (~jkridner@c-98-250-142-42.hsd1.mi.comcast.net) |
| 22:53.36 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 23:00.09 | Crofton | zibri, welcome aboard |
| 23:06.56 | *** join/#oe dos1 (~dos@unaffiliated/dos1) |
| 23:14.09 | Crofton | otavio, thanks for the PR http://www.ossystems.com.br/blog/2013/09/01/o-s-systems-at-esc-brazil-2013.html |
| 23:52.08 | *** join/#oe chris______ (~chris@cpe-74-71-215-22.twcny.res.rr.com) |