*** waltminer has joined #automotive | 00:04 | |
*** jlrmagnus has quit IRC | 00:05 | |
*** waltminer has quit IRC | 00:09 | |
*** rosch has quit IRC | 01:43 | |
*** rosch has joined #automotive | 01:44 | |
*** mdurnev has joined #automotive | 01:48 | |
*** AlisonChaiken has quit IRC | 01:52 | |
*** IOBN has quit IRC | 02:28 | |
*** IOBN has joined #automotive | 02:40 | |
*** sanjeev has joined #automotive | 02:49 | |
*** Sisco has quit IRC | 03:57 | |
*** Sisco has joined #automotive | 03:59 | |
*** jobol has joined #automotive | 05:48 | |
*** Tarnyko has quit IRC | 05:56 | |
*** toscalix has joined #automotive | 05:58 | |
*** chbae has joined #automotive | 06:24 | |
*** gunnarx has joined #automotive | 06:34 | |
*** gunnarx has joined #automotive | 06:34 | |
*** gmacario1 has joined #automotive | 06:45 | |
*** fredcadete has joined #automotive | 06:56 | |
*** nuohan has quit IRC | 07:05 | |
*** leon has joined #automotive | 07:05 | |
*** nuohan has joined #automotive | 07:06 | |
*** leon is now known as Guest40429 | 07:06 | |
*** Guest40429 is now known as leon-anavi | 07:09 | |
leon-anavi | morning | 07:09 |
---|---|---|
CTtpollard | morning | 07:10 |
*** Tarnyko has joined #automotive | 07:10 | |
Tarnyko | good morning | 07:10 |
CTtpollard | gunnarx: the pull request for the new kernel for raspi is delayed until audio is working | 07:14 |
CTtpollard | gunnarx: also I'd changed minnow,qemu & raspi pipelines to -dev beforehand | 07:15 |
*** CTtpollard has quit IRC | 07:17 | |
*** kooltux_ has joined #automotive | 07:19 | |
*** CTtpollard has joined #automotive | 07:20 | |
*** kooltux_ has quit IRC | 07:20 | |
CTtpollard | gunnarx: although it looks like chbae has updated the request since I left work yesterday | 07:23 |
gunnarx | ok, thanks for the updates | 07:23 |
*** sanjeev has quit IRC | 07:23 | |
*** ctbruce has joined #automotive | 07:25 | |
chbae | CTtpollard: hello :) | 07:29 |
chbae | I fixed the audio problem. | 07:30 |
CTtpollard | chbae: yeh I saw :D | 07:30 |
chbae | yep | 07:30 |
CTtpollard | chbae: jonathanmaw is back in the office tomorrow so I'm sure he will test it then | 07:31 |
chbae | CTtpollard: Ok. good. | 07:31 |
gunnarx | chbae - cool. so we can now again make a in-car music player based on GDP and R-Pi | 07:32 |
chbae | :) | 07:32 |
gunnarx | pedroalvarez around? | 07:33 |
*** toscalix has quit IRC | 07:33 | |
*** kooltux_ has joined #automotive | 07:36 | |
*** toscalix has joined #automotive | 07:53 | |
*** ctbruce has quit IRC | 07:57 | |
*** fredcadete has quit IRC | 08:00 | |
CTtpollard | note 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 error | 08:02 |
CTtpollard | meta-renesas maintainer has been informed, so hopefully there will be a resolution soon | 08:06 |
*** ctbruce has joined #automotive | 08:06 | |
*** yannick__ has joined #automotive | 08:07 | |
*** IOBN has quit IRC | 08:15 | |
*** nuohan has quit IRC | 08:21 | |
*** nuohan has joined #automotive | 08:22 | |
*** fredcadete has joined #automotive | 08:23 | |
pedroalvarez | gunnarx: hi! | 08:38 |
gunnarx | Hello | 08:39 |
gunnarx | I was going to ask something about the PR builds but forget what. | 08:40 |
pedroalvarez | :) | 08:40 |
pedroalvarez | gunnarx: so, do I have to add genivigo as collaborator? or that is now done? | 08:40 |
gunnarx | Yes I added it | 08:41 |
gunnarx | So we can do some more testing now maybe. Also commented on https://github.com/GENIVI/meta-genivi-dev/pull/4 | 08:41 |
gunnarx | Here is an interesting thing. Non-merge commit tested correctly. https://github.com/GENIVI/meta-genivi-dev/pull/3 | 08:45 |
gunnarx | It links to build #14 on your pipeline but I actually triggered that build manually this morning, I'm quite sure. | 08:46 |
gunnarx | Whatever the reason, the build result was correctly reported for the topmost commit on that pull | 08:46 |
gunnarx | BTW 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 |
pedroalvarez | gunnarx: yay, new PR triggered the build | 08:49 |
gunnarx | OK, so we're back on track. Adding the genivigo user seems key. | 08:50 |
gunnarx | I 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 |
gunnarx | So the theory would then be that Github requires an authenticated user to use the web API from which the PRs are fetched | 08:51 |
pedroalvarez | I'm wondering if genivi-dev-platform already has genivigo as collaborator | 08:52 |
gunnarx | It does | 08:52 |
gunnarx | I've added it | 08:52 |
pedroalvarez | great, thanks | 08:52 |
gunnarx | In 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 |
pedroalvarez | hm.. maybe | 08:54 |
gunnarx | I don't have any reason to spend time investigating that further however. Now it works. | 08:54 |
pedroalvarez | exactly :) | 08:54 |
gunnarx | well except for all the remaining bugs in the plugin :) | 08:54 |
pedroalvarez | hah | 08:55 |
gunnarx | pedroalvarez, It looks nice in the PR if the pipeline has a good name. So to consider is the pipeline names going forward. | 08:59 |
gunnarx | I suggested GDP-Pull-Request/build | 08:59 |
gunnarx | the first part is the pipeline, the second is the stage name | 08:59 |
gunnarx | Since 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 fixed | 09:00 |
*** Tarnyko has quit IRC | 09:01 | |
*** Tarnyko has joined #automotive | 09:01 | |
pedroalvarez | tbh I don't mind about the naming, so feel free to rename it | 09:01 |
gunnarx | OK fair enough, I will do once we get more structure around this. | 09:02 |
pedroalvarez | regarding 1PR : 1branch... I'm not sure we can do that? | 09:02 |
gunnarx | why not? | 09:02 |
gunnarx | it 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 IRC | 09:05 | |
*** Tarnyko has joined #automotive | 09:06 | |
*** nuohan has quit IRC | 09:10 | |
*** nuohan has joined #automotive | 09:10 | |
CTtpollard | gunnarx: looks like .gitmodules doesn't complain if there's placeholders | 09:19 |
gunnarx | Of course it doesn't, I told you ;-) | 09:19 |
gunnarx | jk, thanks for reporting | 09:19 |
CTtpollard | gunnarx: and from what I'm testing now I think on the qemu .gitmodule file needs a placeholder | 09:20 |
CTtpollard | gunnarx: something like https://github.com/tom--pollard/genivi-dev-platform/blob/tompollard/qemucleanbase/.gitmodules | 09:20 |
gunnarx | OK 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 organization | 09:21 |
CTtpollard | that line group is the end of the core modules, so is common | 09:22 |
CTtpollard | but I get your point | 09:22 |
gunnarx | ok sure, but I think the selection of what is considered core is probably arbitrary in the long run | 09:22 |
CTtpollard | true | 09:22 |
gunnarx | I imagine keeping a placeholder comment for every future module like in my proposal might be even more robust. | 09:23 |
gunnarx | anyway, good to know that the concept works | 09:24 |
CTtpollard | the only difference across branches should be bsp | 09:24 |
gunnarx | "should" ;) | 09:24 |
CTtpollard | unless you're thinking of a different scenario (in terms of layers) | 09:24 |
gunnarx | No 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 |
pedroalvarez | hm.. placeholders in .gitmodules? | 09:25 |
gunnarx | pedroalvarez, it's the latest coolest thing. you should try it. | 09:26 |
pedroalvarez | and then init.sh will replace them and, sync, etc? | 09:26 |
gunnarx | get with the program, man | 09:26 |
CTtpollard | pedroalvarez: haha, one of the problems with having qemu as the 'master' branch is that .gitmodules does not match across target branches | 09:26 |
gunnarx | CTtpollard, would you kindly point pedroalvarez to the relevant ticket :) | 09:26 |
CTtpollard | as it local and bblayers conf | 09:27 |
pedroalvarez | oh, complex problem then | 09:27 |
gunnarx | not that complex. I wrote a long entry on it based on Tom's reports, too tired to repeat | 09:27 |
CTtpollard | https://at.projects.genivi.org/jira/browse/GDP-126 is the main hub for the structure stuff, although sadly the debate has taken many forums | 09:27 |
pedroalvarez | I 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 target | 09:28 |
gunnarx | ah. maybe. might be against git principles and make git confused IDK | 09:29 |
CTtpollard | pedroalvarez: we could also drop gitmodules all together and do all the layers in ini.shit ;) | 09:29 |
CTtpollard | lol! | 09:29 |
CTtpollard | that was an honest typo | 09:29 |
pedroalvarez | hah | 09:29 |
* gunnarx think it was an appropriate name for that script | 09:29 | |
CTtpollard | xD | 09:29 |
CTtpollard | whyalwaysme | 09:29 |
pedroalvarez | you will find yourself reimplementing "repo" | 09:29 |
gunnarx | please noooooooooo | 09:30 |
rjek | pedroalvarez: I thought flatmush had already done that? :) | 09:30 |
*** fredcadete has quit IRC | 09:32 | |
*** fredcadete has joined #automotive | 09:32 | |
CTtpollard | gunnarx: any cunning plan beyond having a template of local & bblayers conf for all targets on every branch? | 09:33 |
*** Tarnyko has quit IRC | 09:37 | |
*** Tarnyko has joined #automotive | 09:37 | |
fredcadete | hi. I am trying to set up an AGL build on porter and all I get is a splash screen | 09:38 |
fredcadete | I followed instructions from here: https://wiki.automotivelinux.org/start/building_for_the_renesas_r-car_m2?s[]=porter | 09:38 |
fredcadete | shouldn't I be getting a pretty app with graphical effects instead of a static splash screen? | 09:39 |
*** Tarnyko has quit IRC | 09:42 | |
gunnarx | CTtpollard, only the original plan - the one that people now want to change... ;) | 09:45 |
CTtpollard | gunnarx: what was in the original plan for conf files? | 09:48 |
gunnarx | what we have now - conf files are in their right location already, version controlled by git. | 09:50 |
gunnarx | variations in those files are handled by branches, like all other source code variations | 09:51 |
CTtpollard | if we want to continually merge off master, we need to change that | 09:54 |
CTtpollard | if there all to be named the default names | 09:54 |
CTtpollard | they're | 09:54 |
gunnarx | I don't follow. The name is always the same right? local.conf and bblayers.conf? or are you talking about something else. | 09:58 |
CTtpollard | and currently the only way I see to handle that is the templates and init.sh moving into place method I did in the single branch | 09:59 |
CTtpollard | yes | 09:59 |
CTtpollard | but I'd like it to be cleaner if possible | 10:01 |
gunnarx | I'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 |
CTtpollard | gunnarx: 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 step | 10:03 |
CTtpollard | the local & bblayers conf (if named as such) will always conflict those in the target branches on merge | 10:03 |
gunnarx | yeah again they "shouldn't" but I guess we're not making headway there | 10:04 |
CTtpollard | handling those with placeholders is way more problematic than .gitmodules | 10:04 |
CTtpollard | take a look at porters local.conf for example | 10:05 |
gunnarx | I'm not saying there should be placeholders, not at all | 10:05 |
gunnarx | Well I guess for the list of layers then, assuming that's where you get the conflict | 10:05 |
CTtpollard | bblayers conflicts yes, and local.conf | 10:06 |
gunnarx | For 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 local | 10:06 |
gunnarx | Let's go back to how to possible solve your new idea | 10:06 |
gunnarx | so 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 |
CTtpollard | haha 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.conf | 10:07 |
gunnarx | no parse. which track are you on now? the new one or the old one? | 10:08 |
CTtpollard | heh irc isn't the best for this | 10:09 |
CTtpollard | I just want to find a solution to the problems with merging local & bblayers conf from qemu/master to all targets | 10:09 |
CTtpollard | and using templates/dummies seems the only way to me right now | 10:10 |
gunnarx | well you did not answer what to do about init.sh | 10:10 |
CTtpollard | if we're having branch per target then no, you can't build any target on any branch | 10:10 |
*** chbae has quit IRC | 10:11 | |
CTtpollard | init.sh would have a mv command based on the branch it is on | 10:11 |
gunnarx | got 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 |
gunnarx | I 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 baggage | 10:12 |
CTtpollard | gunnarx: .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 targets | 10:14 |
CTtpollard | porter varies wildly from qemu for example | 10:14 |
CTtpollard | it's not a set of known additions (i.e we know new submodules are 3 lines in .gitmodules) | 10:15 |
gunnarx | I 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 |
radiofree | surely supporting different platforms is entirely a matter of the kernel + bootloader you build (and cross compiling)? | 10:19 |
radiofree | if the userspace differs so greatly for the porter, then that's an issue that needs to be fixed | 10:19 |
radiofree | qemu, 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 kernel | 10:20 |
gunnarx | "should" | 10:20 |
radiofree | if it doesn't then that's a problem | 10:20 |
gunnarx | radiofree, thing is, if we can reduce our differences of course that's a goal | 10:21 |
gunnarx | easy to say | 10:21 |
gunnarx | I'm not disagreeing with you radiofree, in fact rather your points are in some sense obvious | 10:21 |
gunnarx | devil is in the details and patches welcome :) | 10:21 |
* radiofree steps away | 10:21 | |
gunnarx | thanks radiofree, no hard feelings :) | 10:22 |
radiofree | :) | 10:22 |
gunnarx | CTtpollard, 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 |
gunnarx | I 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 |
gunnarx | You 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 |
CTtpollard | I'd also like to try everything possible to not have to reset git history by rebranching, but fear all paths lead to that | 10:32 |
gunnarx | You should not have to throw away all history though. | 10:36 |
gunnarx | As far as I can tell git merge algorithms will make use of a common parent it will find in the history | 10:36 |
gunnarx | So 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 |
gunnarx | You 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 |
CTtpollard | agreed | 10:46 |
*** Tarnyko has joined #automotive | 11:04 | |
leon-anavi | hi CTtpollard, how is the double check of my patch going on? :) | 11:11 |
CTtpollard | leon-anavi: Currently 4 running tasks (3468 of 4834) :) | 11:14 |
leon-anavi | ok :) | 11:16 |
leon-anavi | building from scratch always requires time | 11:16 |
CTtpollard | leon-anavi: yeh, I sadly lost most of my cached builds when switching upstreams to github, don't ask | 11:18 |
leon-anavi | I won't ask :) | 11:19 |
*** waltminer has joined #automotive | 11:21 | |
CTtpollard | the feeling when you forcefully 'rm -r' the wrong path :) | 11:21 |
* JEEB has done that at least once | 11:25 | |
JEEB | the feeling of "wait that space wasn't supposed to be *there*" | 11:26 |
* CTtpollard pats JEEB | 11:28 | |
JEEB | yeah, thankfully those fat fingers never caused any major damage :) | 11:29 |
leon-anavi | I know this feeling very well too :) | 11:33 |
CTtpollard | tab complete can bite back | 11:33 |
* waltminer has has done ‘sudo rm -r’ from root that was a fine mess | 11:34 | |
Tarnyko | the case where you most appreciate Ctrl+C existence | 11:38 |
*** gunnarx has quit IRC | 11:42 | |
Tarnyko | Figure: hi Figure, around ? | 11:49 |
*** praneeth has quit IRC | 11:58 | |
*** praneeth has joined #automotive | 11:59 | |
CTtpollard | leon-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 |
CTtpollard | actually, I'll merge the PR request, the branching issue isn't really a problem in meta-genivi | 12:53 |
CTtpollard | leon-anavi: merged, I'll update all gdp branches to the new commit | 12:57 |
leon-anavi | thanks | 12:58 |
leon-anavi | this is my first commit to GENIVI through GitHub :) | 12:59 |
CTtpollard | I'd like to try moving the meta-genivi-dev submodule to track master instead of refs | 13:04 |
CTtpollard | but that's a long way off | 13:07 |
CTtpollard | leon-anavi: it's on all target branches now, so we should be able to tell people having problem to pull :) | 13:15 |
leon-anavi | CTtpollard, thank you, I was going to create GitHub pull request for this | 13:16 |
CTtpollard | leon-anavi: any eta on the updated rvi_core request? | 13:16 |
leon-anavi | CTtpollard, 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-anavi | I hope it will be discussed in the next open call. | 13:18 |
leon-anavi | Depending on the result of the discussion I will generate GitHub pull request to add it. | 13:18 |
CTtpollard | leon-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-anavi | that's easy :) I will provide it, just a moment. | 13:19 |
CTtpollard | feel free to submit it whenever you wan't, I'll still try it out before any decision | 13:20 |
leon-anavi | CTtpollard, https://github.com/GENIVI/genivi-dev-platform/pull/9 | 13:34 |
CTtpollard | gmacario1: merged your readme fixup, sorry for the delay | 13:37 |
CTtpollard | leon-anavi: thanks | 13:40 |
CTtpollard | leon-anavi: can rvi node server talk to sota client? | 13:53 |
toscalix | leon-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 #automotive | 13:55 | |
leon-anavi | CTtpollard, 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-anavi | ATS as a company is working on the development of SOTA therefore they can provide more details. | 13:56 |
leon-anavi | toscalix, ok, thank you! | 13:56 |
CTtpollard | leon-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 wiki | 13:57 |
leon-anavi | CTtpollard, yes: https://advancedtelematic.github.io/rvi_sota_server/ | 13:58 |
CTtpollard | leon-anavi: excellent | 14:00 |
leon-anavi | in 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/1 | 14:01 |
CTtpollard | added to the page | 14:01 |
leon-anavi | CTtpollard, thanks! | 14:01 |
leon-anavi | I got an email from confluence about your change. This is a convenient feature of the wiki. | 14:02 |
*** pavelk has joined #automotive | 14:07 | |
CTtpollard | leon-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 use | 14:09 |
leon-anavi | CTtpollard, so I should include the ticket id in the git comment, shouldn't I? | 14:10 |
leon-anavi | I 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 #automotive | 14:11 | |
CTtpollard | leon-anavi: I'm just double checking the example | 14:11 |
*** raz__ has joined #automotive | 14:13 | |
CTtpollard | leon-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-152 | 14:14 |
leon-anavi | can I have a look at the example too? | 14:14 |
leon-anavi | ah, ok | 14:14 |
CTtpollard | sorry I thought it was not working, it was due to jira timing my session out | 14:14 |
leon-anavi | CTtpollard, 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-anavi | raz__, AGL is using wayland, there is no X11 | 14:18 |
CTtpollard | toscalix ^ do you know if it needs the title as well as the [ID] i.e [GDP-152] ? | 14:19 |
toscalix | only ID | 14:19 |
leon-anavi | toscalix, CTtpollard btw it will be easier if we have a wiki article about the exact syntax to link GitHub pull request to JIRA issue :0 | 14: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-anavi | raz__, I suggest you do this as a configuration of Weston through weston.ini. | 14:20 |
toscalix | leon https://at.projects.genivi.org/wiki/display/GDP/GENIVI+Development+Platform+management#GENIVIDevelopmentPlatformmanagement-Githubbestpractices | 14:20 |
CTtpollard | or depending on the environment of your bootloader, you may be able to set resolution there raz__, for instance uboot | 14:20 |
leon-anavi | toscalix, thanks | 14:22 |
CTtpollard | I'd point out that the wiki has links to functionality that we don't have quite yet jira - github wise | 14:22 |
*** mdurnev has quit IRC | 14:22 | |
leon-anavi | CTtpollard, 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 |
CTtpollard | leon-anavi: I believe so, but you should just be able to amend the comment for the PR in the browser? | 14:24 |
CTtpollard | I've not personally tried to send a PR in yet | 14:24 |
toscalix | leon-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 request | 14:25 |
leon-anavi | ok, I have edited the commit message int he browser: https://github.com/GENIVI/genivi-dev-platform/pull/9 | 14:26 |
leon-anavi | as in the video from the wiki I added the ID at the beginning of the first line | 14:26 |
leon-anavi | toscalix, how long should I wait for it to appear in the development menu? | 14:27 |
toscalix | inmediately. Did you add [] ? | 14:28 |
*** raz__ has quit IRC | 14:29 | |
toscalix | leon-anavi: but the video says the meta section, not the comment section | 14:29 |
toscalix | of the pull request | 14:29 |
toscalix | right? | 14:30 |
leon-anavi | I am confused. | 14:30 |
leon-anavi | Is there a test sand for trying out this? | 14:31 |
leon-anavi | I have just reverted my change of the comment. | 14:32 |
toscalix | in 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 brackets | 14:32 |
toscalix | https://github.com/GENIVI/genivi-dev-platform/pull/9/commits/e5e3173008dd07b3d7084a02aa8874d4e2ceffee in the blue box | 14:32 |
CTtpollard | it looks ok to me | 14:33 |
leon-anavi | toscalix, the blue box contains my git commit messages | 14:36 |
toscalix | there you should add the ID | 14:36 |
toscalix | let me show you the example I sent to the ML | 14:36 |
leon-anavi | toscalix, are the brackets required? I don't see them in the video: https://youtu.be/SCNWWfXpCw0?t=3m42s | 14:37 |
toscalix | https://github.com/GENIVI/meta-genivi-dev/pull/3/commits/eb33adc4f6cd06888c1946a1242637876768c624 | 14:37 |
toscalix | ah, wait, in the example chbae also added the ID to the comment | 14:38 |
leon-anavi | yes, it is in the commend | 14:38 |
leon-anavi | *comment | 14:38 |
toscalix | that is the mistake..... | 14:38 |
toscalix | in the example, the ID is in both places, the commit description (where it should be) and the comment (where is irrelevant for this feature | 14:39 |
toscalix | I need to clarify this | 14:39 |
leon-anavi | yes, clarification will be welcome | 14:39 |
leon-anavi | as well as an example with exact steps | 14:39 |
toscalix | I will improve the wiki... | 14:39 |
leon-anavi | because I am personally a bit nervous to experiment with such important commits | 14:40 |
leon-anavi | may be if there is a test repo it will be easier to verify these features. | 14:40 |
CTtpollard | the default comment is generated from the commit | 14:40 |
leon-anavi | yes, exactly. | 14:41 |
*** Tarnyko1 has joined #automotive | 14:41 | |
*** Tarnyko has quit IRC | 14:43 | |
toscalix | leon-anavi: https://at.projects.genivi.org/wiki/display/GDP/GENIVI+Development+Platform+management#GENIVIDevelopmentPlatformmanagement-IntegrationbetweenGitHubandJIRA | 14:45 |
toscalix | leon-anavi: I will create a test ticket in jira | 14:46 |
leon-anavi | thank you! | 14:47 |
leon-anavi | so only the commit message is relevant, right? | 14:47 |
*** nisha_afk is now known as nisha | 14:48 | |
* nisha waves | 14:48 | |
leon-anavi | hi nisha | 14:48 |
nisha | hi leon-anavi | 14:48 |
nisha | anyone around who can help me with my sota client connection issue? :) | 14:49 |
*** waltminer has quit IRC | 14:50 | |
leon-anavi | nisha, have you tried the recommendations from the mailing list? | 14:52 |
toscalix | leon-anavi: yes | 14:52 |
toscalix | https://at.projects.genivi.org/wiki/display/GDP/GENIVI+Development+Platform+management#GENIVIDevelopmentPlatformmanagement-IntegrationbetweenGitHubandJIRA | 14:52 |
toscalix | I added a test ticket and the explanations | 14:52 |
nisha | leon-anavi, let me check if the hostname resolves | 14:53 |
leon-anavi | nisha, can you please share the content of /etc/hosts on your embedded device (VTC1010)? | 14:53 |
nisha | leon-anavi: | 14:54 |
nisha | root@intel-corei7-64:~# cat /etc/hosts | 14:54 |
nisha | 127.0.0.1 localhost.localdomain localhost | 14:54 |
nisha | 192.168.16.150 rvi-client | 14:54 |
leon-anavi | ok, so the docker containers are running on 192.168.16.150, right? | 14:54 |
nisha | no they're running on my host machine which is on the same network as the vtc1010 | 14:55 |
leon-anavi | nisha, what is the IP of your host machine? | 14:57 |
nisha | 192.168.16.95 | 14:58 |
leon-anavi | nisha, ok, on vtc1010 open /etc/hosts and add the following line: 192.168.16.95 rvi-client | 14:59 |
*** rjek has left #automotive | 15:02 | |
nisha | leon-anavi, ok that worked. Sorry for the confusion :/ | 15:03 |
leon-anavi | nisha, ok, could you please reply to the mailing list to confirm that it is working. | 15:04 |
leon-anavi | ? | 15:04 |
nisha | leon-anavi, I will. thanks | 15:05 |
leon-anavi | ok, thank you. | 15:08 |
CTtpollard | nisha: as linkedin decided to point me to your page.... I see you've helped at Free Geek? | 15:14 |
nisha | CTtpollard, yeah! long time ago though | 15:14 |
CTtpollard | that's awesome! I've read about them / watched videos | 15:15 |
nisha | they're pretty cool! except they don't do much in the way of linux distros anymore I've heard | 15:16 |
CTtpollard | nisha: hmm, I think they still put ubuntu on their reconditioned computers | 15:16 |
tjamison | They do! They're currently using Linux Mint. | 15:17 |
CTtpollard | anyway, I should look into if there's a branch in the UK yet | 15:17 |
nisha | CTtpollard, tjamison it was second hand news. I'm happy they're still using linux distros :D | 15: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 |
nisha | tjamison, no kidding...like in build? They're always looking for build people | 15:19 |
tjamison | When I last checked, they had tons of weekday availability for build but Saturdays you'd usually have to schedule 2-3 weeks out | 15:20 |
nisha | ah ok. I volunteered when I was pregnant and unemployed so I could volunteer during the week | 15:21 |
nisha | they pretty much taught me everything I needed to know to get started and more! | 15:21 |
*** Tarnyko1 has quit IRC | 15:32 | |
CTtpollard | the failing libdrm upstream used by meta-renesas is back online, porter builds should be ok now | 15:34 |
*** smiller6 has joined #automotive | 15:45 | |
*** ctbruce has quit IRC | 15:49 | |
*** pavelk has quit IRC | 15:59 | |
*** waltminer has joined #automotive | 15:59 | |
*** jlrmagnus has joined #automotive | 16:05 | |
*** nisha has quit IRC | 16:24 | |
*** nisha has joined #automotive | 16:28 | |
leon-anavi | it's dinner time for me, see you tomorrow :) | 16:31 |
*** leon-anavi has quit IRC | 16:31 | |
*** jlrmagnus has quit IRC | 16:36 | |
*** gunnarx has quit IRC | 16:47 | |
*** jlrmagnus has joined #automotive | 16:51 | |
*** gmacario1 has quit IRC | 16:56 | |
*** gmacario has joined #automotive | 16:59 | |
*** chbae has joined #automotive | 17:03 | |
*** Saint_Isidore has joined #automotive | 17:04 | |
*** kooltux_ has quit IRC | 17:18 | |
*** AlisonChaiken has joined #automotive | 17:25 | |
*** smiller6 has quit IRC | 17:37 | |
*** chbae has quit IRC | 17:47 | |
*** jlrmagnus has quit IRC | 17:48 | |
*** gmacario has quit IRC | 17:50 | |
*** jlrmagnus has joined #automotive | 18:13 | |
*** rZr has quit IRC | 18:26 | |
*** joone has quit IRC | 18:26 | |
*** samuli has quit IRC | 18:26 | |
*** vgrade has quit IRC | 18:26 | |
*** vgrade has joined #automotive | 18:26 | |
*** RzR has joined #automotive | 18:26 | |
*** joone has joined #automotive | 18:27 | |
*** samuli has joined #automotive | 18:27 | |
*** toscalix has quit IRC | 18:41 | |
*** smiller6 has joined #automotive | 18:42 | |
*** smiller6 has quit IRC | 19:30 | |
*** smiller6 has joined #automotive | 19:44 | |
*** waltminer has quit IRC | 20:27 | |
*** jlrmagnus has quit IRC | 20:34 | |
*** jobol has quit IRC | 20:38 | |
*** smiller6 has quit IRC | 20:42 | |
*** jlrmagnus has joined #automotive | 20:52 | |
*** jlrmagnus has quit IRC | 21:52 | |
*** waltminer has joined #automotive | 22:15 | |
*** waltminer has quit IRC | 22:21 | |
*** astrophys has joined #automotive | 22:44 | |
*** nisha is now known as nisha_afk | 22:54 | |
*** tjamison has left #automotive | 23:02 | |
*** tjamison has joined #automotive | 23:03 | |
*** tjamison has left #automotive | 23:03 | |
*** Tarnyko has joined #automotive | 23:19 | |
*** smiller6 has joined #automotive | 23:30 | |
*** zskdan has quit IRC | 23:34 | |
*** smiller6 has quit IRC | 23:37 | |
*** fury has quit IRC | 23:48 | |
*** fury has joined #automotive | 23:55 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!