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

sanjeevHaving trouble to build GDP from github repos on Ubuntu 16.0400:05
sanjeevlibpulse-dev is installed.00:06
*** johnnynines has quit IRC00:08
*** sanjeev has quit IRC00:11
*** jlrmagnus has left #automotive00:15
*** mdurnev has joined #automotive01:22
*** leon-anavi has joined #automotive06:51
leon-anavimorning06:58
*** ctbruce has joined #automotive07:22
*** CTtpollard has joined #automotive07:22
CTtpollardmorning all07:38
*** toscalix has joined #automotive07:59
*** kooltux_ has joined #automotive08:03
*** jonathanmaw has joined #automotive08:16
leon-anavitoscalix, thanks for updating GDP-20608:27
leon-anaviI hope that with joint efforts we can solve this issue.08:28
toscalixwe will08:35
toscalixjonathanmaw: and CTtpollard are waiting for the touchscreen08:36
toscalixI am planning of buying myself one08:36
leon-anavivery good :)08:36
CTtpollardgahh merge commits09:14
*** kooltux_ has quit IRC09:24
*** perryl has left #automotive10:19
*** gunnarx has joined #automotive10:31
*** gunnarx has joined #automotive10:31
CTtpollardhi gunnarx10:37
gunnarxhello10:37
gunnarxjeremiah, you there?10:38
CTtpollardgunnarx: another downside of multiple branches now that we've moved to github is pull request, specifically merge commits10:38
gunnarxthey are harder to merge?10:39
CTtpollardgunnarx: well, easy to merge to the branch from which they create the pull request from10:40
gunnarxyes10:40
gunnarxDo you mean a pull request that happens to a merge commit?   Not sure I follow10:40
CTtpollardfor instance here https://github.com/GENIVI/genivi-dev-platform/commits/qemux86-64 personally I'm not a fan or merge commits anyway, but getting the actual commit + merge commit onto all branches is not pretty10:41
CTtpollardI can cherry pick one or the other10:41
CTtpollardhowever both will bring in the actual change10:42
gunnarxYou mean the topmost commit on that URL or many of them?10:42
gunnarxdon't understand yet what I should look at...10:42
CTtpollardthe top commit is the merge commit, the commit before is the actual commit10:43
CTtpollardyou can add the pull request as a branch and merge to where ever you want, but we can't handle merges like that due to conflicts in conf files. hence why I'm trying to cherry pick10:44
CTtpollardfor something as simple as adding a licence file, this is annoying :)10:45
gunnarxI'm not really sure what jeremiah-LICENSE-patch branch contained.  If it had branched off qemux86 and added one commit, the merge should be just a fast forward.  If other changes were between I suppose the jeremiah branch could be rebased first10:45
gunnarxThere's something broken in the whole setup...  when there are conflicts on simple merges10:46
CTtpollardgunnarx: the issue isn't with the qemu branch, it's getting it onto other branches cleanly10:46
gunnarxand that's where there is something not right, IMHO10:46
CTtpollardthe 'patch' is fine to apply, merging however is not10:47
gunnarxanyhow, it seems an extension of what you have already stated which is that merges between the branches are not trivial, although I am surprised they are not.10:47
CTtpollardI'm not sure where the surprise comes from, there's conflicting files between branches10:48
gunnarxconflicting files = the same part of the same file edited in two different ways10:48
gunnarxthat's a surprise actually.10:48
gunnarxActually maybe I am not that surprised, because we never really made an effort to set it up10:49
CTtpollardlocal conf & bblayers conf will never match between branches10:49
gunnarxthey don't need to10:49
gunnarxsay you have a master branch with MACHINE=qemu10:49
gunnarxthen all other branches are modifications of that branch where MACHINE is set to something else.10:49
CTtpollard+ tons of other config10:49
gunnarxNow that diff is known by the tool and happens earlier in the config.  Merges from master to other branches should not conflict10:50
gunnarxBetween the other branches, possibly10:50
gunnarxoops, happens earlier in the git history I meant to say10:50
CTtpollardI was half thinking about taking the approach I made with having the multiple templates for bblayers & local confs that I did in the single branch poc, but across all branches10:51
CTtpollardI think that's a possibility that may work, and would allow us to still branch per target10:51
gunnarxI'm disputing you have issues with merging.  I just feel it should be theoretically possible to set it up cleanly to minimize that.10:51
gunnarxNot sure I understand this hybrid approach...10:52
gunnarxIs the difference then that you have no shared conf files that can conflict?10:53
CTtpollardyes, and then init.sh is set per branch to extract the one for the specific branch10:54
gunnarxok, and the difference compared to single branch is you can have submodules locked to different hashes10:54
CTtpollardor not included submodules at all10:55
gunnarxright, you don't include BSPs that are not used for example10:55
CTtpollardthe .gitmodules file can be a pain to merge sometimes as well10:55
CTtpollardas we found with meta-rust10:55
CTtpollardappending a new module to the end of the file is different, when one ends in $bsp1 and the other $bsp210:56
gunnarxyeah... I'm trying to fully grasp that as well.  If we started from fresh the master .gitmodules would be a subset of all the others...  with the right setup I feel it *should* merge cleanly.  We are not making conflicting edits for each change, just adding or subtracting.10:58
CTtpollardtrying to make things easier for everyone and everything is hard10:59
gunnarx(I know it's tiring hearing me say that it "should" work :)10:59
CTtpollardgunnarx: the problem is a contributer (I was using meta-rust as an example) adds a new submodule, and uses the qemu branch. This module gets appended to the end of the .modules file. However the board branches all have the .modules file += their bsp layer on the end11:01
gunnarxAh ok.  Yes in this case I can see it happening11:01
CTtpollardnow I can hack this manually, but it's stuff like that I want to avoid11:02
gunnarxHmm, maybe some clever work around...  You would have to get git to understand this is not a conflicting change but a new one.11:03
CTtpollardI still think the potential to switch to the .conf templates across all branches is a possible idea11:04
gunnarxMaybe if .gitmodules had some comment lines so git can find its way better.  Some set of placeholders for new submodules to be added.11:04
CTtpollardgunnarx: interesting11:04
gunnarxIf git figures it is a modification of an existing line (that exists on all branches) instead of two independent additions, I think it should merge cleanly.11:05
gunnarxBut I'm just thinking out loud here.11:05
gunnarxI'm not saying you should do this, just brainstorming.   But if .gitmodules was set up with a bunch of placehodlers like #module1 #module2 #module3 #module4 etc. then git would know that you are inserting something new that is not the same as a previous insert earlier in the history.  Would be cool to try.11:06
gunnarxAnother thing do you understand what is going on with https://github.com/GENIVI/genivi-dev-platform/pull/1 ?11:07
CTtpollardI can't tell if jeremiah meant the branch was unneeded, or the patch itself11:08
CTtpollardi.e the local branch11:08
CTtpollardtbh I just want to put the structure stuff to bed so we can concentrate on ivi1011:11
gunnarxhe closed the PR11:12
gunnarxI want the README fixed... it should not say "almost ready for public" and so on any longer.  Jeremiah's PR was a good first quick fix.11:13
CTtpollardsure11:13
CTtpollardgunnarx: we've discussed as maintainers about github merge commits, do you have a view on them?11:14
gunnarxGenerally I would recommend maintainers don't use the web interface.  If you can study and merge (and possibly clean up) PRs locally and push them instead.11:17
gunnarxYou mean merge commits that Github creates by using the web interface to merge right?11:17
gunnarx^^ merge locally, then push11:17
gunnarxdoes that address the question or was it a different one?11:19
CTtpollardit addresses it, personally I think they just add noise (and currently make things harder)11:19
CTtpollardbut for bigger sets (e.g new functionality) it can be nice to have it to link back to the pr11:20
CTtpollardif viewing in the web ui, git log not so much :)11:21
gunnarxah ok I get the issue now.11:22
gunnarxYeah OK, if you cherry pick and such I suppose it is not as clear.11:22
CTtpollardif can cherry pick the pr merge commit onto another branch, or the actual commit (in the case of this licence patch) but I can't seem to fangle cherry-pick to pull both onto another branch11:24
CTtpollardjust aiming for consistency11:24
gunnarxI would say as long as there is a connection to contributions made by others that should be enough.   I don't think PRs by themselves are all that important - they are needed for review but once you have merged the actual commits matter more.  Just my feeling11:25
gunnarxI suppose github keeps the web part of the PR regardless, i.e. you can see any +1 and comments11:26
gunnarxthat's important of course, but the git history including the tree of PR branches, for me less so.11:26
CTtpollardyeh it does keep the pr request, just losing out on the pr link in the history11:27
CTtpollardI think we agree here11:27
CTtpollardughh pr request11:28
CTtpollardlunch break I think...11:28
gunnarxsend me a request for  pull request request ...11:29
CTtpollardit's like PIN number11:29
gunnarxI like PIN number11:30
CTtpollardwhat about ATM machine?11:30
gunnarxthat too11:31
gunnarxSpeaking of trees, doesn't github put together something useful anyhow, i.e. PRs come from other people's forks and Github shows where those forks go into and out of the history since it can find common commits.  It's up to the submitter to keep their local branches or not, I think.11:32
gunnarxSo as long as you don't rewrite the actual commit (but that's a choice you take locally) it should piece it together somewhat nicely I expect11:32
CTtpollardnot 100% sure tbh11:33
CTtpollardit handles submodule commits nicely if they're also hosted on github11:35
gunnarxI'm pretty sure it will link up identical hashes in the graphs, wherever they are found.11:35
gunnarxyes11:36
*** gunnarx has quit IRC11:49
*** praneeth has quit IRC11:57
*** praneeth has joined #automotive11:58
*** GuyS has joined #automotive12:08
*** GuyS has quit IRC12:13
*** gunnarx has joined #automotive12:27
*** gunnarx has joined #automotive12:27
*** GSgns has joined #automotive12:41
*** GSgns has quit IRC12:45
*** GSgns has joined #automotive12:46
*** waltminer has joined #automotive12:52
CTtpollardjeremiah: you around? :)13:39
gunnarxwhoa, you have to write access CTtpollard ? :)13:58
gunnarxno write access13:59
CTtpollardseems that way13:59
gunnarxI can fix it13:59
gunnarxif Jeremiah's not around14:00
gunnarxtry onw14:02
gunnarxnow14:02
CTtpollardgunnarx: your magical powers fixed it14:02
CTtpollardgunnarx: thanks14:04
gunnarxyou are welcome14:05
*** AlisonChaiken has quit IRC14:15
jeremiahCTtpollard: Hiya14:32
jeremiahSorry I was out of the loop14:32
jeremiahThanks for fixing gunnarx14:32
gunnarxnp14:32
jeremiahJust so everyone knows, I've given magic write powers to those in the GDP Crew team14:33
gunnarxscary14:33
*** tjamison has joined #automotive14:33
jeremiahBut they can only write to the genivi-dev-platform. :-)14:33
CTtpollard:)14:33
jeremiahSo hopefully not too wicked scary14:33
gunnarxyou never know14:33
jeremiahSo far its only been me who's been randomly commiting to the wrong branch :P14:34
CTtpollardjeremiah: your licence patch is on all targets now, however the qemu branch is the only one with the github PR merge commit for it14:46
gunnarxCTtpollard, jeremiah opened up the README also.  You could merge it (and remove the extra branch after)...14:47
gunnarxopened the README pull request14:48
gunnarxI was trying to look at if this could be cleanly merged but have other things that need to be done.  For the moment if you need to cherry-pick, I imagine you could continue doing that to avoid the merge hassles that are there now14:49
*** waltminer has quit IRC14:49
*** waltminer has joined #automotive14:50
*** astrophys has joined #automotive14:52
CTtpollardheh, you can add .patch to the end of PR url to get a plaintext patch https://patch-diff.githubusercontent.com/raw/GENIVI/genivi-dev-platform/pull/1.patch14:52
*** mdurnev has quit IRC14:55
*** jlrmagnus has joined #automotive14:58
*** mvick has joined #automotive15:01
toscalixjeremiah: since tomorrow the news about GDP on github will be out in the newsletter and Minnow release announcement, I was thinking it could be good to mention in the How to Contribute page Giyhub15:04
toscalixGitHub15:05
*** gunnarx has quit IRC15:06
toscalixjeremiah: wouldn't it be better to provide rights to push opnl maintainers?15:13
toscalixsorry15:13
toscalixjeremiah: wouldn't it be better to provide rights to push only to maintainers?15:13
toscalixGDP crew is meant to be everybody involved in GDP15:14
toscalixadded admin rights to maintainers in genivi-dev-platformmaintainers15:16
toscalixremoved write rights to genivi crew to in meta-genivi-demo waiting for jeremiah confimation15:16
*** jlrmagnus has quit IRC15:20
*** brlogger has joined #automotive15:28
*** astrophys has quit IRC15:40
*** ToxicGumbo-work has quit IRC15:41
*** ToxicGumbo-work has joined #automotive15:47
*** RzR has quit IRC16:01
*** RzR has joined #automotive16:01
*** ctbruce has quit IRC16:24
toscalixSo we are ready to release GDP-ivi9 port to Intel Minnowboard tomorrow16:25
RzRtoscalix, on master branch ?16:33
RzRtoscalix, I will test it16:33
toscalixyes16:34
toscalixgreat16:34
RzRI can try tonight if it helps16:34
toscalixit does16:34
RzRok I can build master16:34
toscalixhttps://github.com/GENIVI/meta-genivi-dev16:35
RzRor qemu branch16:35
toscalixyes16:35
RzRok16:35
toscalixcheck this: https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=1156931116:35
toscalixwe will release images though16:35
*** jonathanmaw has quit IRC16:51
*** leon-anavi has quit IRC16:58
*** ToxicGumbo-work has quit IRC16:59
*** ToxicGumbo-work has joined #automotive17:03
*** toscalix has quit IRC17:06
*** waltminer has quit IRC17:43
*** jlrmagnus has joined #automotive17:44
*** jlrmagnus has quit IRC18:02
*** AlisonChaiken has joined #automotive18:04
*** mvick has quit IRC18:06
*** jlrmagnus has joined #automotive18:18
*** waltminer has joined #automotive18:36
*** jlrmagnus has quit IRC18:47
*** jlrmagnus has joined #automotive19:00
*** waltminer has quit IRC19:47
*** kooltux_ has joined #automotive19:49
*** AlisonChaiken has quit IRC20:01
*** jlrmagnus has quit IRC20:02
*** AlisonChaiken has joined #automotive20:16
*** jlrmagnus has joined #automotive20:18
*** Sisco has joined #automotive20:52
*** Sisco_ has quit IRC20:53
*** AlisonChaiken has quit IRC21:01
*** jlrmagnus has quit IRC21:17
*** AlisonChaiken has joined #automotive21:19
*** Saint_Isidore has joined #automotive21:37
*** Saint_Is_ has quit IRC21:38
*** chbae has joined #automotive21:47
*** jlrmagnus has joined #automotive22:02
*** chbae has quit IRC22:09
*** sanjeev has joined #automotive22:13
*** kooltux_ has quit IRC22:22
*** tjamison has left #automotive22:57
*** waltminer has joined #automotive23:12
*** jlrmagnus has quit IRC23:25
*** Saint_Isidore has quit IRC23:26

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