IRC logs for #automotive for Thursday, 2016-05-19

*** waltminer has joined #automotive00:04
*** jlrmagnus has quit IRC00:05
*** waltminer has quit IRC00:09
*** rosch has quit IRC01:43
*** rosch has joined #automotive01:44
*** mdurnev has joined #automotive01:48
*** AlisonChaiken has quit IRC01:52
*** IOBN has quit IRC02:28
*** IOBN has joined #automotive02:40
*** sanjeev has joined #automotive02:49
*** Sisco has quit IRC03:57
*** Sisco has joined #automotive03:59
*** jobol has joined #automotive05:48
*** Tarnyko has quit IRC05:56
*** toscalix has joined #automotive05:58
*** chbae has joined #automotive06:24
*** gunnarx has joined #automotive06:34
*** gunnarx has joined #automotive06:34
*** gmacario1 has joined #automotive06:45
*** fredcadete has joined #automotive06:56
*** nuohan has quit IRC07:05
*** leon has joined #automotive07:05
*** nuohan has joined #automotive07:06
*** leon is now known as Guest4042907:06
*** Guest40429 is now known as leon-anavi07:09
leon-anavimorning07:09
CTtpollardmorning07:10
*** Tarnyko has joined #automotive07:10
Tarnykogood morning07:10
CTtpollardgunnarx: the pull request for the new kernel for raspi is delayed until audio is working07:14
CTtpollardgunnarx: also I'd changed minnow,qemu & raspi pipelines to -dev beforehand07:15
*** CTtpollard has quit IRC07:17
*** kooltux_ has joined #automotive07:19
*** CTtpollard has joined #automotive07:20
*** kooltux_ has quit IRC07:20
CTtpollardgunnarx: although it looks like chbae has updated the request since I left work yesterday07:23
gunnarxok, thanks for the updates07:23
*** sanjeev has quit IRC07:23
*** ctbruce has joined #automotive07:25
chbaeCTtpollard: hello :)07:29
chbaeI fixed the audio problem.07:30
CTtpollardchbae: yeh I saw :D07:30
chbaeyep07:30
CTtpollardchbae: jonathanmaw is back in the office tomorrow so I'm sure he will test it then07:31
chbaeCTtpollard: Ok. good.07:31
gunnarxchbae - cool.  so we can now again make a in-car music player based on GDP and R-Pi07:32
chbae:)07:32
gunnarxpedroalvarez around?07:33
*** toscalix has quit IRC07:33
*** kooltux_ has joined #automotive07:36
*** toscalix has joined #automotive07:53
*** ctbruce has quit IRC07:57
*** fredcadete has quit IRC08:00
CTtpollardnote to anyone trying to build the porter GDP image, there's an issue with the src_uri for libdrm so you will encounter a build error08:02
CTtpollardmeta-renesas maintainer has been informed, so hopefully there will be a resolution soon08:06
*** ctbruce has joined #automotive08:06
*** yannick__ has joined #automotive08:07
*** IOBN has quit IRC08:15
*** nuohan has quit IRC08:21
*** nuohan has joined #automotive08:22
*** fredcadete has joined #automotive08:23
pedroalvarezgunnarx: hi!08:38
gunnarxHello08:39
gunnarxI was going to ask something about the PR builds but forget what.08:40
pedroalvarez:)08:40
pedroalvarezgunnarx: so, do I have to add genivigo as collaborator? or that is now done?08:40
gunnarxYes I added it08:41
gunnarxSo we can do some more testing now maybe.  Also commented on https://github.com/GENIVI/meta-genivi-dev/pull/408:41
gunnarxHere is an interesting thing.  Non-merge commit tested correctly.  https://github.com/GENIVI/meta-genivi-dev/pull/308:45
gunnarxIt links to build #14 on your pipeline but I actually triggered that build manually this morning, I'm quite sure.08:46
gunnarxWhatever the reason, the build result was correctly reported for the topmost commit on that pull08:46
gunnarxBTW I guess you know that the plugin only builds the top-most commit in a PR, which makes sense of course, but worth pointing out.  And then if you add more commits to the same PR it should rebuild the new tip.08:47
pedroalvarezgunnarx: yay, new PR triggered the build08:49
gunnarxOK, so we're back on track.  Adding the genivigo user seems key.08:50
gunnarxI documented that this is required only for reporting the result, not for noticing the PR.  But I'm leaning towards that it might be necessary also for noticing the PR.  After all the build-PR plugin is also configured with user=genivigo and an OATH token, so it must be used for something?08:51
gunnarxSo the theory would then be that Github requires an authenticated user to use the web API from which the PRs are fetched08:51
pedroalvarezI'm wondering if genivi-dev-platform already has genivigo as collaborator08:52
gunnarxIt does08:52
gunnarxI've added it08:52
pedroalvarezgreat, thanks08:52
gunnarxIn our previous IRC discussion I reported on seeing a 401 Authorization error somewhere on the api.github.com.  Also, I think it's logical Github might not allow anonymous requests to its API - that would enable somebody to anonymously spider the entire set of metadata in all of GitHub, probably something they want to keep track of.08:53
pedroalvarezhm.. maybe08:54
gunnarxI don't have any reason to spend time investigating that further however.  Now it works.08:54
pedroalvarezexactly :)08:54
gunnarxwell except for all the remaining bugs in the plugin :)08:54
pedroalvarezhah08:55
gunnarxpedroalvarez, It looks nice in the PR if the pipeline has a good name.  So to consider is the pipeline names going forward.08:59
gunnarxI suggested GDP-Pull-Request/build08:59
gunnarxthe first part is the pipeline, the second is the stage name08:59
gunnarxSince the user GoUser is shown with its icon that doesn't need to part of the name.    However I suppose one PR- pipeline per branch is the way to go, once the master bug is fixed09:00
*** Tarnyko has quit IRC09:01
*** Tarnyko has joined #automotive09:01
pedroalvareztbh I don't mind about the naming, so feel free to rename it09:01
gunnarxOK fair enough, I will do once we get more structure around this.09:02
pedroalvarezregarding 1PR : 1branch... I'm not sure we can do that?09:02
gunnarxwhy not?09:02
gunnarxit seems to me we will have to.  PRs are proposed by the submitter for merging into a particular branch.  Sure, if the maintenance team goes for a single-branch setup, that issue will be reduced of course.09:04
*** Tarnyko has quit IRC09:05
*** Tarnyko has joined #automotive09:06
*** nuohan has quit IRC09:10
*** nuohan has joined #automotive09:10
CTtpollardgunnarx: looks like .gitmodules doesn't complain if there's placeholders09:19
gunnarxOf course it doesn't, I told you  ;-)09:19
gunnarxjk, thanks for reporting09:19
CTtpollardgunnarx: and from what I'm testing now I think on the qemu .gitmodule file needs a placeholder09:20
CTtpollardgunnarx: something like https://github.com/tom--pollard/genivi-dev-platform/blob/tompollard/qemucleanbase/.gitmodules09:20
gunnarxOK sure, that's the minimal approach. But keeping BSPs at the end (or maybe at the top come to think of it) seems a neater organization09:21
CTtpollardthat line group is the end of the core modules, so is common09:22
CTtpollardbut I get your point09:22
gunnarxok sure, but I think the selection of what is considered core is probably arbitrary in the long run09:22
CTtpollardtrue09:22
gunnarxI imagine keeping a placeholder comment for every future module like in my proposal might be even more robust.09:23
gunnarxanyway, good to know that the concept works09:24
CTtpollardthe only difference across branches should be bsp09:24
gunnarx"should" ;)09:24
CTtpollardunless you're thinking of a different scenario (in terms of layers)09:24
gunnarxNo real scenario.  I just like solutions that go one step further, just in case.  Nothing more annoying than having a problem you have solved come back again.09:25
pedroalvarezhm.. placeholders in .gitmodules?09:25
gunnarxpedroalvarez, it's the latest coolest thing.  you should try it.09:26
pedroalvarezand then init.sh will replace them and, sync, etc?09:26
gunnarxget with the program, man09:26
CTtpollardpedroalvarez: haha, one of the problems with having qemu as the 'master' branch is that .gitmodules does not match across target branches09:26
gunnarxCTtpollard, would you kindly point pedroalvarez to the relevant ticket :)09:26
CTtpollard as it local and bblayers conf09:27
pedroalvarezoh, complex problem then09:27
gunnarxnot that complex.  I wrote a long entry on it based on Tom's reports, too tired to repeat09:27
CTtpollardhttps://at.projects.genivi.org/jira/browse/GDP-126 is the main hub for the structure stuff, although sadly the debate has taken many forums09:27
pedroalvarezI was just wondering if it was possible to configure all the submodules in ,gitmodules, and then in init.sh only sync the ones needed for the target09:28
gunnarxah. maybe. might be against git principles and make git confused IDK09:29
CTtpollardpedroalvarez: we could also drop gitmodules all together and do all the layers in ini.shit ;)09:29
CTtpollardlol!09:29
CTtpollardthat was an honest typo09:29
pedroalvarezhah09:29
* gunnarx think it was an appropriate name for that script09:29
CTtpollardxD09:29
CTtpollardwhyalwaysme09:29
pedroalvarezyou will find yourself reimplementing "repo"09:29
gunnarxplease noooooooooo09:30
rjekpedroalvarez: I thought flatmush had already done that? :)09:30
*** fredcadete has quit IRC09:32
*** fredcadete has joined #automotive09:32
CTtpollardgunnarx: any cunning plan beyond having a template of local & bblayers conf for all targets on every branch?09:33
*** Tarnyko has quit IRC09:37
*** Tarnyko has joined #automotive09:37
fredcadetehi. I am trying to set up an AGL build on porter and all I get is a splash screen09:38
fredcadeteI followed instructions from here: https://wiki.automotivelinux.org/start/building_for_the_renesas_r-car_m2?s[]=porter09:38
fredcadeteshouldn't I be getting a pretty app with graphical effects instead of a static splash screen?09:39
*** Tarnyko has quit IRC09:42
gunnarxCTtpollard, only the original plan - the one that people now want to change... ;)09:45
CTtpollardgunnarx: what was in the original plan for conf files?09:48
gunnarxwhat we have now - conf files are in their right location already, version controlled by git.09:50
gunnarxvariations in those files are handled by branches, like all other source code variations09:51
CTtpollardif we want to continually merge off master, we need to change that09:54
CTtpollardif there all to be named the default names09:54
CTtpollardthey're09:54
gunnarxI don't follow. The name is always the same right?  local.conf and bblayers.conf?  or are you talking about something else.09:58
CTtpollardand currently the only way I see to handle that is the templates and init.sh moving into place method I did in the single branch09:59
CTtpollardyes09:59
CTtpollardbut I'd like it to be cleaner if possible10:01
gunnarxI'm not following your latest idea.  If we have branches for a particular target, then that branch should only need the files relevant for that target, and the init script can only build that target.  If we have a single branch it needs all the file variants as in your single-branch proposal.10:02
CTtpollardgunnarx: I'm trying to overcome the merge conflicts of having targets branches based off master/qemu, the .gitmodules is one, local conf & bblayers is the next step10:03
CTtpollardthe local & bblayers conf (if named as such) will always conflict those in the target branches on merge10:03
gunnarxyeah again they "shouldn't" but I guess we're not making headway there10:04
CTtpollardhandling those with placeholders is way more problematic than .gitmodules10:04
CTtpollardtake a look at porters local.conf for example10:05
gunnarxI'm not saying there should be placeholders, not at all10:05
gunnarxWell I guess for the list of layers then, assuming that's where you get the conflict10:05
CTtpollardbblayers conflicts yes, and local.conf10:06
gunnarxFor all other things I'm only saying that the few changes that are common to all (i.e. made on qemu branch and merged over) should be possible to merge.  I don't see why not.  Most of the changes I expect will not go to master/qemu first, but will be local10:06
gunnarxLet's go back to how to possible solve your new idea10:06
gunnarxso you have all conf files on all branches.  does the init script allow building a target that is not supported on that branch, or is the init script different on each branch...10:07
CTtpollardhaha I don't want it to be a new idea, I agree that the changes should be common to all, but that still won't stop git falling over on the differences in local.conf10:07
gunnarxno parse.  which track are you on now?  the new one or the old one?10:08
CTtpollardheh irc isn't the best for this10:09
CTtpollardI just want to find a solution to the problems with merging local & bblayers conf from qemu/master to all targets10:09
CTtpollardand using templates/dummies seems the only way to me right now10:10
gunnarxwell you did not answer what to do about init.sh10:10
CTtpollardif we're having branch per target then no, you can't build any target on any branch10:10
*** chbae has quit IRC10:11
CTtpollardinit.sh would have a mv command based on the branch it is on10:11
gunnarxgot it.  but then init.sh is slightly different.  so you have to hope you have no conflicts in merging that :)10:11
CTtpollard+!10:11
gunnarxI know you want a solution.  Single branch is one solution.  Another we have not tried (I think) is make a new clean branch structure to see if some conflicts are inherent in some historical baggage10:12
CTtpollardgunnarx: .gitmodules is working on clean branches with placeholder, the local conf's aren't due to the structure of the file being so varied across targets10:14
CTtpollardporter varies wildly from qemu for example10:14
CTtpollardit's not a set of known additions (i.e we know new submodules are 3 lines in .gitmodules)10:15
gunnarxI understand but maintain that variations in themselves do not automatically mean merge conflicts with git.  Unless what you are trying to merge in fact has no commonality which means it's an unsolvable problem.  I'm not disputing you have them currently though.10:17
radiofreesurely supporting different platforms is entirely a matter of the kernel + bootloader you build (and cross compiling)?10:19
radiofreeif the userspace differs so greatly for the porter, then that's an issue that needs to be fixed10:19
radiofreeqemu, minnow-board, should be the same (just build the drm drivers as modules), porter should only differ in the fact that you cross-compile for arm and need a different kernel10:20
gunnarx"should"10:20
radiofreeif it doesn't then that's a problem10:20
gunnarxradiofree, thing is, if we can reduce our differences of course that's a goal10:21
gunnarxeasy to say10:21
gunnarxI'm not disagreeing with you radiofree, in fact rather your points are in some sense obvious10:21
gunnarxdevil is in the details and patches welcome :)10:21
* radiofree steps away10:21
gunnarxthanks radiofree, no hard feelings :)10:22
radiofree:)10:22
gunnarxCTtpollard, what I am aiming for is that re-arranging the conf files into common and differing sections ought to make it possible to merge common changes into the common sections.  Whatever remains wildly different has no commonality that can be merged, per definition.10:22
gunnarxI think we're likely suffering from bad structure plus some weird baggage in the git history which can be fixed by re-branching off a new common master.10:23
gunnarxYou might be bitten by a conflict in the list of layers  identical to the .gitmodules problem but if we put the BSP at the top or something like that you might avoid it.10:25
CTtpollard:)10:30
CTtpollardI'd also like to try everything possible to not have to reset git history by rebranching, but fear all paths lead to that10:32
gunnarxYou should not have to throw away all history though.10:36
gunnarxAs far as I can tell git merge algorithms will make use of a common parent it will find in the history10:36
gunnarxSo AFAICT you make a new branch off the master where you put all current differences that describe how to go from master to <branch> into one single new commit (the first on the new branch).  Then they have a common parent and the differences are now "known" on subsequent merges.10:40
gunnarxYou would not use git merge or anything that makes use of previous git history.  To create the commit that branches off into the new direction it's git reset, copy files in shell and so on.  You only want to inform git:  hey this is the exact single diff you need to  get from master to <branch>.  That should bring a clean slate.10:44
gunnarx"should" :)10:44
CTtpollardagreed10:46
*** Tarnyko has joined #automotive11:04
leon-anavihi CTtpollard, how is the double check of my patch going on? :)11:11
CTtpollardleon-anavi: Currently 4 running tasks (3468 of 4834) :)11:14
leon-anaviok :)11:16
leon-anavibuilding from scratch always requires time11:16
CTtpollardleon-anavi: yeh, I sadly lost most of my cached builds when switching upstreams to github, don't ask11:18
leon-anaviI won't ask :)11:19
*** waltminer has joined #automotive11:21
CTtpollardthe feeling when you forcefully 'rm -r' the wrong path :)11:21
* JEEB has done that at least once11:25
JEEBthe feeling of "wait that space wasn't supposed to be *there*"11:26
* CTtpollard pats JEEB 11:28
JEEByeah, thankfully those fat fingers never caused any major damage :)11:29
leon-anaviI know this feeling very well too :)11:33
CTtpollardtab complete can bite back11:33
* waltminer has has done ‘sudo rm -r’ from root that was a fine mess11:34
Tarnykothe case where you most appreciate Ctrl+C existence11:38
*** gunnarx has quit IRC11:42
TarnykoFigure: hi Figure, around ?11:49
*** praneeth has quit IRC11:58
*** praneeth has joined #automotive11:59
CTtpollardleon-anavi: I'm happy to merge it :), do you wish to have the merge commit visible, or are you ok with me just merging the patch?12:52
CTtpollardactually, I'll merge the PR request, the branching issue isn't really a problem in meta-genivi12:53
CTtpollardleon-anavi: merged, I'll update all gdp branches to the new commit12:57
leon-anavithanks12:58
leon-anavithis is my first commit to GENIVI through GitHub :)12:59
CTtpollardI'd like to try moving the meta-genivi-dev submodule to track master instead of refs13:04
CTtpollardbut that's a long way off13:07
CTtpollardleon-anavi: it's on all target branches now, so we should be able to tell people having problem to pull :)13:15
leon-anaviCTtpollard, thank you, I was going to create GitHub pull request for this13:16
CTtpollardleon-anavi: any eta on the updated rvi_core request?13:16
leon-anaviCTtpollard, rvi_core is provided by meta-rvi. Yesterday I asked about this layer during the open call but it is related to the general discussion whether layers for components which are not included by default in GDP should be included. toscalix asked me to remind him about this question next week.13:17
leon-anaviI hope it will be discussed in the next open call.13:18
leon-anaviDepending on the result of the discussion I will generate GitHub pull request to add it.13:18
CTtpollardleon-anavi: Yeh I understand that, I meant that we discussed the need for a new patchset/PR that included the latest commit of meta-rvi, in which the rvi_core recipe was switch to look at github :)13:18
leon-anavithat's easy :) I will provide it, just a moment.13:19
CTtpollardfeel free to submit it whenever you wan't, I'll still try it out before any decision13:20
leon-anaviCTtpollard, https://github.com/GENIVI/genivi-dev-platform/pull/913:34
CTtpollardgmacario1: merged your readme fixup, sorry for the delay13:37
CTtpollardleon-anavi: thanks13:40
CTtpollardleon-anavi: can rvi node server talk to sota client?13:53
toscalixleon-anavi: if for whatever reason I forget, when I send the invitation by mail, remind me and I will include it in the agenda. I hope the remind won't be neccessary but...13:55
*** gunnarx has joined #automotive13:55
leon-anaviCTtpollard, I am afraid that I am not sure about the exact steps regarding this use case. Could you please forward this question to the developers from ATS?13:55
leon-anaviATS as a company is working on the development of SOTA therefore they can provide more details.13:56
leon-anavitoscalix, ok, thank you!13:56
CTtpollardleon-anavi: I may, I was just wondering if there was any further documentation we could link to the in the sota/core pages on the wiki13:57
leon-anaviCTtpollard, yes: https://advancedtelematic.github.io/rvi_sota_server/13:58
CTtpollardleon-anavi: excellent14:00
leon-anaviin the mean time I found a minor typo in the readme of meta-rvi. This pull request fixes it: https://github.com/GENIVI/meta-rvi/pull/114:01
CTtpollardadded to the page14:01
leon-anaviCTtpollard, thanks!14:01
leon-anaviI got an email from confluence about your change. This is a convenient feature of the wiki.14:02
*** pavelk has joined #automotive14:07
CTtpollardleon-anavi: if a pull request, if you include the jira ticket it should link it to the ticket, I've not tried it personally but I've seen it in use14:09
leon-anaviCTtpollard, so I should include the ticket id in the git comment, shouldn't I?14:10
leon-anaviI have used similar feature of redmine in the past but I am not that familiar with JIRA (and JIRA is not that open source ;) )14:11
*** tjamison has joined #automotive14:11
CTtpollardleon-anavi: I'm just double checking the example14:11
*** raz__ has joined #automotive14:13
CTtpollardleon-anavi: so yeh if you add to the comment meta data like here https://github.com/GENIVI/meta-genivi-dev/pull/3 , it will appear in the jira ticket (you have to be logged into jira to see them) https://at.projects.genivi.org/jira/browse/GDP-15214:14
leon-anavican I have a look at the example too?14:14
leon-anaviah, ok14:14
CTtpollardsorry I thought it was not working, it was due to jira timing my session out14:14
leon-anaviCTtpollard, so I need to add a new line with "[<JIRA ID>] <JIRA title>" at the bottom on my commit message, is that all?14:16
raz__hello, I am trying to get xrandr into my agl build but when I add the IMAGE_INSTALL_append = " xrandr" to local.conf bitbake gets this ERROR: xrandr was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES) any suggestions ?14:17
leon-anaviraz__, AGL is using wayland, there is no X1114:18
CTtpollardtoscalix ^ do you know if it needs the title as well as the [ID] i.e [GDP-152] ?14:19
toscalixonly ID14:19
leon-anavitoscalix, CTtpollard btw it will be easier if we have a wiki article about the exact syntax to link GitHub pull request to JIRA issue :014:19
leon-anavi:)14:19
raz__leon-anavi, but I need program like xrandr so I can change my second monitor resolution, is there anyway to do it without xrandr?14:20
leon-anaviraz__, I suggest you do this as a configuration of Weston through weston.ini.14:20
toscalixleon https://at.projects.genivi.org/wiki/display/GDP/GENIVI+Development+Platform+management#GENIVIDevelopmentPlatformmanagement-Githubbestpractices14:20
CTtpollardor depending on the environment of your bootloader, you may be able to set resolution there raz__, for instance uboot14:20
leon-anavitoscalix, thanks14:22
CTtpollardI'd point out that the wiki has links to functionality that we don't have quite yet jira - github wise14:22
*** mdurnev has quit IRC14:22
leon-anaviCTtpollard, so... if I force push a change to my fork of genivi-dev-platform and add the ID then the GitHub pull request will appear in JIRA. Is my assumption correct?14:23
CTtpollardleon-anavi: I believe so, but you should just be able to amend the comment for the PR in the browser?14:24
CTtpollardI've not personally tried to send a PR in yet14:24
toscalixleon-anavi: if you add to your pull request an ID from a jira issue, it will appear the development menu in the jira issue, with the status of the pull request14:25
leon-anaviok, I have edited the commit message int he browser: https://github.com/GENIVI/genivi-dev-platform/pull/914:26
leon-anavias in the video from the wiki I added the ID at the beginning of the first line14:26
leon-anavitoscalix, how long should I wait for it to appear in the development menu?14:27
toscalixinmediately. Did you add [] ?14:28
*** raz__ has quit IRC14:29
toscalixleon-anavi: but the video says the meta section, not the comment section14:29
toscalixof the pull request14:29
toscalixright?14:30
leon-anaviI am confused.14:30
leon-anaviIs there a test sand for trying out this?14:31
leon-anaviI have just reverted my change of the comment.14:32
toscalixin the next pull request... when you create it, you have to fill out the pull request description/meta. Is there where you have to add the ticket ID between brackets14:32
toscalixhttps://github.com/GENIVI/genivi-dev-platform/pull/9/commits/e5e3173008dd07b3d7084a02aa8874d4e2ceffee in the blue box14:32
CTtpollardit looks ok to me14:33
leon-anavitoscalix, the blue box contains my git commit messages14:36
toscalixthere you should add the ID14:36
toscalixlet me show you the example I sent to the ML14:36
leon-anavitoscalix, are the brackets required? I don't see them in the video: https://youtu.be/SCNWWfXpCw0?t=3m42s14:37
toscalixhttps://github.com/GENIVI/meta-genivi-dev/pull/3/commits/eb33adc4f6cd06888c1946a1242637876768c62414:37
toscalixah, wait, in the example chbae also added the ID to the comment14:38
leon-anaviyes, it is in the commend14:38
leon-anavi*comment14:38
toscalixthat is the mistake.....14:38
toscalixin the example, the ID is in both places, the commit description (where it should be) and the comment (where is irrelevant for this feature14:39
toscalixI need to clarify this14:39
leon-anaviyes, clarification will be welcome14:39
leon-anavias well as an example with exact steps14:39
toscalixI will improve the wiki...14:39
leon-anavibecause I am personally a bit nervous to experiment with such important commits14:40
leon-anavimay be if there is a test repo it will be easier to verify these features.14:40
CTtpollardthe default comment is generated from the commit14:40
leon-anaviyes, exactly.14:41
*** Tarnyko1 has joined #automotive14:41
*** Tarnyko has quit IRC14:43
toscalixleon-anavi: https://at.projects.genivi.org/wiki/display/GDP/GENIVI+Development+Platform+management#GENIVIDevelopmentPlatformmanagement-IntegrationbetweenGitHubandJIRA14:45
toscalixleon-anavi: I will create a test ticket in jira14:46
leon-anavithank you!14:47
leon-anaviso only the commit message is relevant, right?14:47
*** nisha_afk is now known as nisha14:48
* nisha waves14:48
leon-anavihi nisha14:48
nishahi leon-anavi14:48
nishaanyone around who can help me with my sota client connection issue? :)14:49
*** waltminer has quit IRC14:50
leon-anavinisha, have you tried the recommendations from the mailing list?14:52
toscalixleon-anavi: yes14:52
toscalixhttps://at.projects.genivi.org/wiki/display/GDP/GENIVI+Development+Platform+management#GENIVIDevelopmentPlatformmanagement-IntegrationbetweenGitHubandJIRA14:52
toscalixI added a test ticket and the explanations14:52
nishaleon-anavi, let me check if the hostname resolves14:53
leon-anavinisha, can you please share the content of /etc/hosts on your embedded device (VTC1010)?14:53
nishaleon-anavi:14:54
nisharoot@intel-corei7-64:~# cat /etc/hosts14:54
nisha127.0.0.1       localhost.localdomain           localhost14:54
nisha192.168.16.150  rvi-client14:54
leon-anaviok, so the docker containers are running on 192.168.16.150, right?14:54
nishano they're running on my host machine which is on the same network as the vtc101014:55
leon-anavinisha, what is the IP of your host machine?14:57
nisha192.168.16.9514:58
leon-anavinisha, ok, on vtc1010 open /etc/hosts and add the following line: 192.168.16.95  rvi-client14:59
*** rjek has left #automotive15:02
nishaleon-anavi, ok that worked. Sorry for the confusion :/15:03
leon-anavinisha, ok, could you please reply to the mailing list to confirm that it is working.15:04
leon-anavi?15:04
nishaleon-anavi, I will. thanks15:05
leon-anaviok, thank you.15:08
CTtpollardnisha: as linkedin decided to point me to your page.... I see you've helped at Free Geek?15:14
nishaCTtpollard, yeah! long time ago though15:14
CTtpollardthat's awesome! I've read about them / watched videos15:15
nishathey're pretty cool! except they don't do much in the way of linux distros anymore I've heard15:16
CTtpollardnisha: hmm, I think they still put ubuntu on their reconditioned computers15:16
tjamisonThey do! They're currently using Linux Mint.15:17
CTtpollardanyway, I should look into if there's a branch in the UK yet15:17
nishaCTtpollard, tjamison it was second hand news. I'm happy they're still using linux distros :D15:18
tjamison(I volunteered a bunch with them last year. I've been meaning to get over there again this year but they have limited availability for volunteering)15:18
nishatjamison, no kidding...like in build? They're always looking for build people15:19
tjamisonWhen I last checked, they had tons of weekday availability for build but Saturdays you'd usually have to schedule 2-3 weeks out15:20
nishaah ok. I volunteered when I was pregnant and unemployed so I could volunteer during the week15:21
nishathey pretty much taught me everything I needed to know to get started and more!15:21
*** Tarnyko1 has quit IRC15:32
CTtpollardthe failing libdrm upstream used by meta-renesas is back online, porter builds should be ok now15:34
*** smiller6 has joined #automotive15:45
*** ctbruce has quit IRC15:49
*** pavelk has quit IRC15:59
*** waltminer has joined #automotive15:59
*** jlrmagnus has joined #automotive16:05
*** nisha has quit IRC16:24
*** nisha has joined #automotive16:28
leon-anaviit's dinner time for me, see you tomorrow :)16:31
*** leon-anavi has quit IRC16:31
*** jlrmagnus has quit IRC16:36
*** gunnarx has quit IRC16:47
*** jlrmagnus has joined #automotive16:51
*** gmacario1 has quit IRC16:56
*** gmacario has joined #automotive16:59
*** chbae has joined #automotive17:03
*** Saint_Isidore has joined #automotive17:04
*** kooltux_ has quit IRC17:18
*** AlisonChaiken has joined #automotive17:25
*** smiller6 has quit IRC17:37
*** chbae has quit IRC17:47
*** jlrmagnus has quit IRC17:48
*** gmacario has quit IRC17:50
*** jlrmagnus has joined #automotive18:13
*** rZr has quit IRC18:26
*** joone has quit IRC18:26
*** samuli has quit IRC18:26
*** vgrade has quit IRC18:26
*** vgrade has joined #automotive18:26
*** RzR has joined #automotive18:26
*** joone has joined #automotive18:27
*** samuli has joined #automotive18:27
*** toscalix has quit IRC18:41
*** smiller6 has joined #automotive18:42
*** smiller6 has quit IRC19:30
*** smiller6 has joined #automotive19:44
*** waltminer has quit IRC20:27
*** jlrmagnus has quit IRC20:34
*** jobol has quit IRC20:38
*** smiller6 has quit IRC20:42
*** jlrmagnus has joined #automotive20:52
*** jlrmagnus has quit IRC21:52
*** waltminer has joined #automotive22:15
*** waltminer has quit IRC22:21
*** astrophys has joined #automotive22:44
*** nisha is now known as nisha_afk22:54
*** tjamison has left #automotive23:02
*** tjamison has joined #automotive23:03
*** tjamison has left #automotive23:03
*** Tarnyko has joined #automotive23:19
*** smiller6 has joined #automotive23:30
*** zskdan has quit IRC23:34
*** smiller6 has quit IRC23:37
*** fury has quit IRC23:48
*** fury has joined #automotive23:55

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