IRC logs for #automotive for Monday, 2016-05-09

*** gmacario has joined #automotive04:10
*** Sisco has quit IRC04:58
*** Sisco has joined #automotive05:00
*** gmacario has quit IRC05:06
*** jobol has joined #automotive05:16
*** gmacario has joined #automotive05:58
*** leon-anavi has joined #automotive06:32
leon-anavimorning06:36
*** CTtpollard has joined #automotive07:18
*** Saint_Isidore has quit IRC07:19
*** ctbruce has joined #automotive07:27
*** sanjeev has joined #automotive07:32
*** anahuelamo has joined #automotive07:54
*** toscalix has joined #automotive08:13
*** jonathanmaw has joined #automotive08:28
*** jobol has quit IRC08:37
*** Saint_Isidore has joined #automotive08:38
*** jobol has joined #automotive08:38
*** Tarnyko has joined #automotive08:42
*** warter has joined #automotive08:46
warteroops! ERROR: ParseError at /home/user/[...]/meta-agl/meta-agl/recipes-sota/rvi-sota-client/rvi-sota-client_git.bb:5: Could not inherit file classes/cargo.bbclass08:48
warterand I made a repo sync before that08:49
*** warter is now known as jbocklage12308:49
CTtpollardjbocklage123: looks like bitbake is missing meta-rust08:50
jbocklage123let me check the number of files in meta-rust... so you can compare08:51
CTtpollardjbocklage123: does bitbake-layers show meta-rust is being parsed?08:52
leon-anavihi warter you need layer meta-rust and it should be defined in bblayers.conf. I have updated the templates for bblayers.conf and my patch has been merged.08:53
leon-anavijbocklage123 ^^^08:53
leon-anavijbocklage123, please make sure that you are using bblayers.conf generated from the new templates (you should have got them after doing repo sync).08:54
jbocklage123ah. I had to delete build/conf. A source ...env porter did not help. Now it seems to work...08:55
leon-anavijbocklage123, alternatively, if you prefer to keep your old build/conf you can just add meta-rust to bblayers.conf manually.08:55
jbocklage123I thought, the source... re-creates the bblayers.conf if the template changed...08:55
jbocklage123nono! I LOVE generated content ;))08:55
leon-anavijbocklage123 ok :)08:55
jbocklage123AGL's choice for IPC is dbus, right?08:56
*** gunnarx has joined #automotive09:02
*** gunnarx has joined #automotive09:02
*** Saint_Isidore has quit IRC09:03
*** Saint_Isidore has joined #automotive09:14
*** gunnarx has quit IRC09:21
RzRCTtpollard, hi09:35
RzRCTtpollard, I tested gdp on max09:35
RzRCTtpollard, it was ok09:36
CTtpollardRzR: thanks a bunch. how long did you enjoy the sunshine for beforehand?09:38
RzRwhat do you mean ?09:39
RzRbtw I plan I have to upstream our demos too , 1st I send meta-oic patches to list ?09:39
RzRis it the right workflow ?09:39
CTtpollardRzR: from thursday '<RzR> CTtpollard, I've lunched the build I will test it after enjoying this sunny day' ;)09:40
RzRah yes09:41
CTtpollardRzR: the list is fine, however it should now be based off the github repo. obviously that means pull requests as well09:42
RzRis it ready now ?09:42
CTtpollardThe minnowbranch is not quite in there yet, but qemu, porter and raspi2 are09:42
RzRI assume I need to push to master 1st09:42
RzRCTtpollard, https://github.com/search?p=1&q=genivi-demo-platform&type=Repositories&utf8=%E2%9C%9309:47
RzRwhich branch is best ?09:49
CTtpollardRzR: we're here now :) https://github.com/GENIVI/09:49
CTtpollardAnd demo is now dev09:50
CTtpollardwhich will probably take me years to stop saying09:50
RzRsorry09:51
RzRI know ;)09:51
*** Saint_Isidore has quit IRC09:57
RzRCTtpollard, https://github.com/GENIVI/genivi-dev-platform/pull/309:57
CTtpollardcheers10:05
CTtpollardthis again goes back to the point of how many support layers we wan't to hold by default, especially if not used in the build by default10:05
RzRit will be used by an other layer10:07
*** Saint_Isidore has joined #automotive10:08
CTtpollardyes, meta-genivi-demo10:09
CTtpollardgahh, dev-demo10:09
CTtpollardmonday10:10
RzR meta-genivi-ocf-demo10:10
*** Saint_Isidore has quit IRC10:12
CTtpollardRzR: could that not become a part of meta-genivi-dev?10:12
RzRIMHO , it would be better to have it into a separate layer10:14
RzRCTtpollard, like that https://github.com/TizenTeam/genivi-dev-platform/commits/sandbox/pcoval/minnowboard10:16
RzRCTtpollard, any ETA of minnow branch in g-dev-p ?10:27
CTtpollardRzR: I'm hoping to hear back from chbae today10:27
RzRanyway oic can be merged on any10:28
*** gmacario has quit IRC10:32
*** gmacario has joined #automotive10:46
CTtpollardRzR: once the minnow branch is in place, all the work can be done in a fork/branch. Could you guys then do a wiki page on how to use it? The same was done for Sota client11:01
*** Tarnyko has quit IRC11:05
*** Tarnyko has joined #automotive11:06
*** toscalix_ has joined #automotive11:12
*** toscalix has quit IRC11:12
*** gunnarx has joined #automotive11:44
*** gunnarx has joined #automotive11:44
RzRCTtpollard, ok can you suggest a wiki url to be used ?11:47
CTtpollardRzR: potentially a subpage of https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=1156787911:48
RzRoki doing this now11:49
*** gunnarx has quit IRC12:03
*** waltminer has joined #automotive13:02
waltminerGood morning13:03
CTtpollardhey waltminer13:08
waltminerhey CTtpollard13:12
*** perryl has left #automotive13:14
*** gunnarx has joined #automotive13:15
*** gunnarx has joined #automotive13:15
* CTtpollard hacks around a single branch approach 13:29
gunnarxHack around as in avoiding? ;)13:42
CTtpollardheh, not in this case13:44
*** jlrmagnus has joined #automotive13:45
*** chbae has joined #automotive13:48
gunnarxMorning jlrmagnus13:55
*** AlisonChaiken has quit IRC14:03
jlrmagnusMorning gunnarx14:04
jlrmagnus3 hours of morning meetings. Yay!14:05
gunnarxGreat14:05
gunnarxStay on IRC just in case you get bored ;)14:06
*** tjamison has joined #automotive14:07
gunnarxIn other news Volvo will start selling tanks.  Apparently we have experience. https://www.youtube.com/watch?v=4yeCG6SS5wI14:09
gunnarxWho needs a marketing department when others do the work... :)14:12
jonathanmawtoscalix_: I just rejected your pull request to genivi-dev-platform's README for the reasons given. Please rework and resend it, or hand over the responsibility to make those changes to me.14:12
*** masterkorp has left #automotive14:13
RzRgunnarx, send us a sample tank, just to control it with a tizen ring , we have a point and destroy usecase , sanjeev14:14
gunnarxOK, will think about it.14:15
RzRwe will demo it at next GENIVI AMM ;)14:15
CTtpollardhaha14:19
CTtpollardGDP on tank14:19
RzRgenivi destruction platform14:21
*** astrophys has joined #automotive14:22
gunnarxawesome14:31
*** anahuelamo has quit IRC14:32
gunnarxI can't really get over the video, you can't buy that kind of publicity...  Granted most of the 1.3M views are probably Swedes so far.14:33
*** anahuelamo has joined #automotive14:35
*** waltminer has quit IRC14:35
rjekOn the other hand, the rear of estate cars don't really need crumple zones :)14:35
leon-anavihehe, viral video :)14:35
*** astrophys has quit IRC14:39
gunnarxleon-anavi, it will be now that #automotive gets a hold of it.  The reach of #automotive is amazing ;)14:41
leon-anavigunnarx, I have already shared it to other irc channels ;)14:41
gunnarx:)14:41
toscalix_jonathanmaw: fine14:55
toscalix_thanks for reviewing14:55
*** toscalix_ is now known as toscalix14:55
toscalixjonathanmaw: while checking the wiki pages changing demo by development I came across your deployment scripts. I think you will have to update the repo names14:55
jonathanmawtoscalix: yep. it's also a really ugly script, so a proper way of doing deployment would also be nice :)15:01
toscalixWe will need to double check the build instructions on feature page and target pages once the migration is completed since the repos has old names15:01
jonathanmawtoscalix: where did you find the script?15:03
toscalixRelease Howto page15:05
toscalixhttps://at.projects.genivi.org/wiki/display/GDP/GDP+release+howto15:05
toscalixRzR: genivi destruction platform..... nooooo! another name change no, please :-)15:10
jonathanmawtoscalix: odd. I can't find my script from that page. Perhaps we're thinking about different things15:11
toscalixchecking15:11
jonathanmawtoscalix: ah, I think I understand what you mean15:11
jonathanmawthe manual instructions have been changed, and you surmise that my script also needs changing15:11
toscalixyes15:12
toscalixjonathanmaw: writing a ticket about it so we do not forget15:13
toscalixI have also related the tasks about changing the name development vs demo with the migration to github since not just the name but the links needs to be updated in the gdp-ivi9 build instructions for every target15:18
toscalixalso for RVI SOTA client, I assume15:18
toscalixwhen we release the minnowboard port will be the right opportunity to check the other instructions, I guess15:19
RzRtoscalix, I am building a qemu image to test before minnow release15:25
chbaeHello.15:26
*** astrophys has joined #automotive15:26
gunnarxHello chbae15:27
chbaeHi. gunnarx.15:27
gunnarxjonathanmaw, toscalix.  There are deployment scripts? :)15:27
gunnarxsounds promising :)15:27
jonathanmawgunnarx: it's really ugly and fragile, hence why the only stuff in the wiki is manual instructions, which hopefully involve the application of common sense :)15:28
gunnarxthat's always a dangerous assumption ;)15:29
gunnarxcommon sense is too uncommon15:29
*** smiller6 has joined #automotive15:31
*** AlisonChaiken has joined #automotive15:35
toscalixgunnarx: deployment today has two main steps. 1.- Make the images and artifacts available for GENIVI devop 2.- move those images/artifacts to the download infra. The current scripts only covers the first point15:36
gunnarxOK.  If you need any help putting any of those steps into Go, let me know.15:38
CTtpollardchbae: are you happy to bring the minnowboard branch to github now? I was going to do it and rework your GDP commit manually on top of it, but didn't feel clean15:40
chbaetoscalix: I thought that we need to add tag in genivi-demo-platform. ex) v9.0 like meta-genivi-demo. Is it ok?15:40
toscalixyes.... but not demo but dev, ok?15:40
gunnarx:)15:41
toscalixgunnarx: we will, thanks15:41
gunnarxdev dev dev dev dev15:41
gunnarxit's going to take a while :)15:41
CTtpollardcan someone reboot gunnarx please15:41
gunnarxI will do it15:41
chbaeCTtpollard: I thought that you can fork genivi/xxx to your github repo., clean up and then merge into genivi/xxx. That’s my recommendation.15:42
*** praneeth has joined #automotive15:42
chbaeWhat I’m saying genivi-demo-platform, because of GDP-ivi9 release in https://at.projects.genivi.org/wiki/display/GDP/GDP-ivi9+version%3A+feature+page. :)15:42
CTtpollardchbae: are you ok with me recreating your patch ( it doesn't apply cleanly due to how we branch)15:42
chbaeCTtpollard: ok.15:43
CTtpollardi.e this patch https://github.com/GENIVI/genivi-dev-platform/commit/b59c3727ed981603438d5dc58946d1cfcd5c71ab15:43
chbaeyou can recreate forcely.15:44
toscalixchbae: that page should mantion development instead of demo already15:45
chbaeCTtpollard: Could you create “v9.0” tag in genivi-demo-platform.git.15:46
chbaetoscalix: yes. but we released ivi9.0 under genivi-demo-platform.15:46
toscalixah, you are talking about the tag that reflect what we released15:47
toscalixthen yes, but if you want to tag something after that, dev. Is that ok for you or you have something different in mind15:47
toscalix?15:47
toscalixwe can also tag with dev the code we had when the name was changed, at AMM15:48
toscalixthat can be of some interest in the future15:49
chbaetoscalix: Did we release in genivi-demo-platform? right?15:49
toscalixup to you guys15:49
toscalixyes15:49
gunnarxAs stated before, there are branches that should be tags instead.  "ivi9-beta", "ivi9-rc1" and so on.15:49
chbaeSo IMO, we can use “GENIVI Development Platform” name after ivi9.15:49
toscalixfine with me15:50
toscalixCTtpollard: jonathanmaw do you guys agree?15:50
gunnarx,,,so putting a tag on those previous points in history, and then getting rid of those branches15:50
chbaegunnarx: agree.15:51
chbaetoscalix: and then, i’ll change Build from scratch GDP-ivi9 section in https://at.projects.genivi.org/wiki/display/GDP/GDP-ivi9+version%3A+feature+page.15:51
chbaegunnarx: However, meta-genivi-demo.git already has v7.0, v8.0, and v9.0 tag.15:52
toscalixthey should, yes15:53
chbaegunnarx, toscalix, CTtpollard, jonathanmaw: If we would like to change tag name, we will decide it and do it.15:53
jonathanmawtoscalix: I'm not sure what I'm being asked about. Is this about what the "D" in GDP-ivi9 release stands for?15:53
toscalixtagging idea from chbae15:54
chbaeWe should create tag in genivi-demo-platform to know real release commit.15:56
jonathanmawI have no objections to creating tags in genivi-dev-platform to identify previous releases15:56
chbaemeta-genivi-demo are using v7.0, v8.0, and v9.0. So if we don’t change the tag naming, we need to use it in genivi-demo-platform.15:58
chbaejonathanmaw: Do you know release commit in genivi-demo-platform?15:59
jonathanmawchbae: I'm not certain16:00
chbaeCTtpollad, jonathanmaw: I recommend tag name(v9.0-rpi2, v9.0-porter, v9.0-qemux86) in genivi-demo-platform.16:00
*** leon-anavi has quit IRC16:01
chbaejonathanmaw: Ok. Could you discuss with CTtpollard and create tag in genivi-demo-platform? I agree the naming what you decide.16:02
toscalixchbae: why do you think it is more useful to classify the tags based on releases first instead of target first. Just wondering...16:02
jonathanmawtoscalix: I think it's nicer in terms of alignment :)16:03
RzRCTtpollard, It builds also fine on qemu , https://github.com/GENIVI/genivi-dev-platform/pull/316:03
toscalixand a second question: why not two separate tags?16:03
jonathanmawtoscalix: two separate tags for what?16:03
toscalixreflect version and reflect target16:03
jonathanmawtoscalix: I still don't understand your question16:04
chbae1. When we use “git tag” command, the list will be arranged in alphbet order. So it’s useful to use releases first.16:04
toscalixchbae: sold16:05
chbae2. I can’t understand your question :)16:05
chbaetoscalix: we also can consider target first. :)16:06
toscalixI am asking if it would be more flexible/useful to have a tag for the target and a different one for the release. Instead of v9.0-rpi2 ... "v9.0" + "rpi2"16:06
toscalixtwo tags16:06
jonathanmawtoscalix: genivi-demo-platform is different for rpi2 and porter, so they point at different refs16:07
chbaetoscalix: A repo doesn’t have same tag name.16:07
jonathanmawtherefore need multiple tags16:07
chbaeex) we use v9.0 tag in rpi2 branch and then we can’t use v9.0 tag in port branch.16:08
jonathanmawtoscalix: also, tags are deliberately hard to change. the tag we call "rpi2" will stay as that release16:08
toscalixI see16:09
jonathanmawtoscalix: and by "deliberately hard to change" I mean "if you tell me to change them, I will argue with you for 3 hours"16:09
toscalixif you guys agree on the naming scheme, fine with me16:09
chbaeSo I recommend we can use target and version’s combination. I’m fine to use “target first” or “version first”.16:09
toscalixjonathanmaw: I would call that...very close to impossible to change16:10
toscalixchbae: the reasons pointed for using number first are solid16:10
toscalixgo ahead16:10
toscalixplease remember that the numbering schema will change.... probably16:11
jonathanmawit gets slightly messier when we consider the "*-beta" and "*-rc1" tags16:11
chbaetoscalix: yes.16:11
toscalixwe will use a numbering schema that will be different for releases (external) and internal.16:12
toscalixso we will use a number to reflect alfas, betas, etc. for devs16:12
chbaetoscalix: cool.16:12
toscalixstill giving some thoughts about how16:12
toscalixchecking previous experiences16:13
chbaejonathanmaw: yes but IMO, it’s enought to add just release tag in ivi9 release.16:13
jonathanmawchbae: ok. iirc, ivi7 and ivi8 releases didn't use genivi-demo-platform, so it'll just be tagging one release16:15
jonathanmawthat makes things simpler :)16:15
chbaeyes.16:15
chbaebut I don’t know real release commit id. So please discuss with Tom and do it :)16:16
chbaeFYI: https://www.linux.com/news/watch-videos-embedded-linux-conference-openiot-summit-north-america-2016?_utm_source=1-2-216:16
chbaeThere is toscalix’s presentation.16:17
toscalixchbae... I was sick as hell that day. I really thought I was not going to make it that day.16:17
toscalixand the day before16:18
toscalixthanks god my partner was with me16:18
toscalixRzR was there16:19
chbae:)16:19
chbaeI’ll join next ELCE 2016 on Oct.16:19
toscalixchbae: https://at.projects.genivi.org/wiki/display/GDP/GDP+Out+There#GDPOutThere-April2016:GDPatELC201616:20
toscalixslides and video linked16:20
toscalixchbae: I will see you there16:20
chbaeCOOL.16:20
*** ctbruce has quit IRC16:21
chbaeI’ll go to bed. see you tomorrow.16:22
chbaebye.16:22
*** chbae has left #automotive16:22
RzR;)16:24
*** jlrmagnus has quit IRC16:33
jonathanmawtags pushed. they point to the old meta-genivi-demo repo, as they did in the release16:42
jonathanmawerk. I got genivi-demo-platform and genivi-dev-platform confused in the tag annotations16:43
*** gmacario has quit IRC16:43
jonathanmawnot even consistently so I can pretend I did it deliberately :S16:43
jonathanmawI think rewriting history and altering the tags would be a graver (and more hypocritical) sin than leaving the annotations slightly wrong. So I guess I'll just have to leave it.16:46
*** jonathanmaw has quit IRC16:47
*** mvick has joined #automotive16:51
*** toscalix has quit IRC17:11
*** waltminer has joined #automotive17:13
*** gmacario has joined #automotive17:16
*** gmacario has quit IRC17:16
*** Saint_Isidore has joined #automotive17:25
*** bjones has joined #automotive17:32
*** jlrmagnus has joined #automotive17:45
*** jjardon has quit IRC18:46
*** jjardon has joined #automotive18:49
*** waltminer has quit IRC18:53
*** gunnarx has quit IRC18:53
*** waltminer has joined #automotive18:56
*** AlisonChaiken has quit IRC19:08
*** Sisco has quit IRC19:20
*** AlisonChaiken has joined #automotive19:22
*** Sisco has joined #automotive19:31
*** Sisco has quit IRC19:36
*** Sisco has joined #automotive19:37
*** Sisco has quit IRC19:41
*** Sisco has joined #automotive19:45
*** jlrmagnus has quit IRC20:33
*** Tarnyko1 has joined #automotive20:45
*** Tarnyko has quit IRC20:48
*** jlrmagnus has joined #automotive20:48
*** jlrmagnus has quit IRC21:30
*** AlisonChaiken has quit IRC21:34
*** jobol has quit IRC21:39
*** AlisonChaiken has joined #automotive21:52
*** jlrmagnus has joined #automotive21:53
*** jlrmagnus has quit IRC22:15
*** AlisonChaiken has quit IRC22:16
*** AlisonChaiken has joined #automotive22:25
*** jlrmagnus has joined #automotive22:28
*** tjamison has left #automotive22:33
*** jlrmagnus has quit IRC22:47
*** smiller6 has quit IRC22:55
*** astrophys has quit IRC23:24

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!