--- Log opened Thu Aug 31 00:00:09 2017
00:32 #navit: < pmckinley> Hey KaZeR
00:38 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:38 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:38 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
00:57 #navit: < pmckinley> oh no!!!
00:57 #navit: < pmckinley> run away!
01:13 #navit: < pmckinley> :-D
02:49 -!- noradtux [~noradtux@port-3676.pppoe.wtnet.de] has quit [Ping timeout: 252 seconds]
02:50 -!- noradtux [~noradtux@2a02:2028:53f:5101:64ed:95a1:d178:a551] has joined #navit
04:51 -!- noradtux [~noradtux@2a02:2028:53f:5101:64ed:95a1:d178:a551] has quit [Ping timeout: 240 seconds]
15:56 -!- noradtux [~noradtux@port-56350.pppoe.wtnet.de] has joined #navit
16:33 #navit: < ilovekiruna> KaZeR: hi
16:34 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has quit [Ping timeout: 240 seconds]
16:45 #navit: <@KaZeR> hi there
16:46 #navit: <@KaZeR> ilovekiruna: need help with the pr? iirc you need to remove one commit from your branch to submit it?
16:46 #navit: < ilovekiruna> exactly
16:46 #navit: < ilovekiruna> was curious how to do it in one step
16:46 #navit: < ilovekiruna> i know, one can cherry pick in another branch
16:46 #navit: < ilovekiruna> but still, am too  curious about the more direct way
16:52 #navit: < ilovekiruna> I read the man page of that git command-line command
16:52 #navit: < ilovekiruna> but dont understant it completely
16:53 #navit: <@KaZeR> i don't think that you can do it in one step, AFAIK pull requests are always based on a branch
16:54 #navit: < ilovekiruna> for github, I saw that there is a feature request to allow cherry picking while creating boot requests
16:54 #navit: < ilovekiruna> unfortunately, not implemented
16:57 #navit: <@KaZeR> yeah it could be nice, but in the end it'd be a wrapper around creating a branch, cherry picking commits and then pushing it as a PR :)
16:58 #navit: <@KaZeR> want to try doing it in seperate steps?
16:59 #navit: < ilovekiruna> u know, with the command git request-pull, I could do it already
16:59 #navit: < ilovekiruna> just had to run it on hte servers of github ;-)
16:59 #navit: < ilovekiruna> yeah, let's do the manual way
17:03 #navit: <@KaZeR> well with "git request-pull" you still need to cherry pick to remove the commit you don't want, no?
17:03 #navit: < ilovekiruna> no, u can specify start and end commit
17:04 #navit: < ilovekiruna> so I could cut out the last commit
17:05 #navit: <@KaZeR> ohhh
17:06 #navit: <@KaZeR> what error are you facing when using "git request-pull" ?
17:07 #navit: < ilovekiruna> I am not facing an error, but it is not for my use-case
17:07 #navit: <@KaZeR> i'm confused :)
17:07 #navit: < ilovekiruna> as it would pull from another repo
17:07 #navit: < ilovekiruna> thats why I say, running from the github-server it would work
17:08 #navit: < ilovekiruna> in case I understood the command directly
17:09 #navit: <@KaZeR> is the code you want to PR in a branch of the repo or in your fork?
17:09 #navit: < ilovekiruna> right now in my fork
17:09 #navit: < ilovekiruna> not yet a branch in the main navit repo
17:10 #navit: <@KaZeR> is it in the trunk of your repo? or in another branch?
17:10 #navit: < ilovekiruna> in another branch in my repo
17:11 #navit: < ilovekiruna> so do i first need to merge it in trunk in my repo?
17:11 #navit: <@KaZeR> ok. what's your repo? i don't see a "ilovekiruna" fork
17:11 #navit: <@KaZeR> i don't think that you need to merge it in your trunk
17:11 #navit: < ilovekiruna> https://github.com/hoehnp/navit
17:12 #navit: <@KaZeR> adjustable_speed_warner branch?
17:13 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 248 seconds]
17:13 #navit: < ilovekiruna> exactly
17:14 #navit: < ilovekiruna> as I said, only thing, I do not want in my pull-request, is my change to circleci.yml
17:14 #navit: < ilovekiruna> for my fork, I just built it with android
17:14 #navit: < ilovekiruna> should we then run tests on all platforms first?
17:17 #navit: <@KaZeR> tests will be run automatically when the PR will be pushed
17:17 #navit: <@KaZeR> (as long as you do not push a change to circleci's config of course)
17:17 #navit: <@KaZeR> my understanding of the doc says that this might be what you want :
17:17 #navit: <@KaZeR> git request-pull 962c078c685399458cdcb61f63ba4f8b8e4cbcab https://github.com/hoehnp/navit.git trunk:adjustable_speed_warner 6ae8aa3321becebbdca87b0185f6553c61da5f5f
17:19 #navit: < ilovekiruna> cool, would try it
17:24 #navit: < ilovekiruna> I get the following warning:
17:24 #navit: < ilovekiruna> https://dpaste.de/sehB
17:32 #navit: <@KaZeR> try https://github.com/hoehnp/navit/commits/adjustable_speed_warner instead of https://github.com/hoehnp/navit.git maybe
17:40 #navit: < ilovekiruna> tried it
17:41 #navit: < ilovekiruna> gives fatal error, that the remote doesnt exist
17:43 #navit: < ilovekiruna> am testing the feature nwo locally in a tiny repo
17:45 #navit: <@KaZeR> i think that actually we should reference adjustable_speed_warner instead of trunk:adjustable_speed_warner
17:45 #navit: <@KaZeR> looks like this should be the branch that your work is in, in your repo
17:46 #navit: <@KaZeR> "summarizing the changes between the v1.0 release and your master"
17:46 #navit: < ilovekiruna> managed it locally, in my test repo
17:47 #navit: < ilovekiruna> could now make that pulling from the second branch to the first one
17:47 #navit: < ilovekiruna> how can we do it, using github?
17:47 #navit: < ilovekiruna> I make another branch starting from before my last commit?
17:47 #navit: < ilovekiruna> and then make a pull request on that?
17:49 #navit: <@KaZeR> there's different ways to do it. the approach you described should work. You could also create a new branch, and apply the two commits as patches ( https://github.com/hoehnp/navit/commit/962c078c685399458cdcb61f63ba4f8b8e4cbcab.patch and https://github.com/hoehnp/navit/commit/6ae8aa3321becebbdca87b0185f6553c61da5f5f.patch ) then then push
17:50 #navit: <@KaZeR> or you can create a new branch based on your adjustable_speed_warner branch, and revert the circleci commit, then push
17:50 #navit: <@KaZeR> or create a branch by cherry picking from adjustable_speed_warner and push
17:51 #navit: < ilovekiruna> I think the last one sounds most interesting
17:51 #navit: < ilovekiruna> will check it out
17:51 #navit: <@KaZeR> cool
17:54 #navit: < ilovekiruna> actually I notice that probably nothing is left to be done for me
17:55 #navit: < ilovekiruna> if i go to main trunk, and compare my fork and the difference between it and main, seems only my change of circleci.yml is from me
17:55 #navit: < ilovekiruna> to make the speed warner toggle on click you already commited to the trank in May
17:55 #navit: <@KaZeR> oh!
17:56 #navit: < ilovekiruna> you also hv that in the commit comment
17:56 #navit: < ilovekiruna> Damn it, did not mean to commit against trunk.
17:56 #navit: < ilovekiruna> ;-)
17:56 -!- gernot_ [d9e52a21@gateway/web/freenode/ip.217.229.42.33] has joined #navit
17:56 #navit: < gernot_> hi
17:56 #navit: <@KaZeR> hi gernot_
17:56 #navit: < ilovekiruna> hi gernot_
17:56 #navit: <@KaZeR> ilovekiruna: well it was a good exercise to practice git :)
17:57 #navit: < ilovekiruna> yes, never mind
17:57 #navit: < gernot_> KaZeR: at weekend i test the TT_navit build...
17:57 #navit: < ilovekiruna> at least good for me to know, that I can close one case for myself :D
17:57 #navit: <@KaZeR> gernot_: https://2456-30791823-gh.circle-artifacts.com/0/tmp/tomtom/sdcard/navitom_minimal.zip
17:57 #navit: <@KaZeR> perfect
17:57 #navit: < gernot_> look all files in place
17:57 #navit: <@KaZeR> ilovekiruna: yep :)
17:58 #navit: <@KaZeR> gernot_: we might be missing the output of a zip or something for the plugin build : https://circleci.com/gh/navit-gps/navit/2460#artifacts/containers/0
17:58 #navit: <@KaZeR> but it'll be easy to fix
17:59 #navit: < gernot_> I cant test the plugin. My TT dont start it or freeze after boot
18:00 #navit: <@KaZeR> are you in touch with the guy who wrote the script to build the plugin in the first place?
18:00 #navit: <@KaZeR> it would be great to get feedback
18:01 #navit: < gernot_> no, but i found articles saying that TT changed the menue system
18:02 #navit: <@KaZeR> ah, ok thanks
18:03 #navit: < gernot_> opentom.org is closed for yers, but some pages are stored at archive.org
18:04 #navit: < gernot_> It worked on a 8 year old TT, but after updating it stopped working.
18:06 #navit: < gernot_> So i drop the TT environment and use a fullcustom opentom system.
18:06 #navit: < gernot_> Much better results.
18:07 #navit: < gernot_> the activated swap help a lot on a 32Mb device ;-)
18:22 #navit: <@KaZeR> haha yeah 32mb.. boy...
18:24 #navit: < gernot_> Navit work outside big town well, but all some bit restricted.
18:24 #navit: < gernot_> On 64Mb devices it is better :-)
18:29 #navit: < ilovekiruna> btw: kazer: whendriving last with sailfish, it seemed that navit had sometimes quite some nervous times
18:29 #navit: < ilovekiruna> just sth like, continously saying, turn right, turn left, no please tchange  direction of driving
18:30 #navit: <@KaZeR> it happened to me once or twice in the past. Always at the very same location
18:31 #navit: <@KaZeR> do you remember where it happened exactly?
18:31 #navit: <@KaZeR> do you have a gps log ?
18:31 #navit: < ilovekiruna> a kind of
18:31 #navit: < ilovekiruna> next time will do a log
18:31 #navit: < ilovekiruna> I noticed twice this the same route, it wanted me to turn right
18:31 #navit: < ilovekiruna> but there was no road
18:32 #navit: < ilovekiruna> need to note the position next time
18:34 #navit: <@KaZeR> yeah it would be interesting to see if it's related to the osm data. That's what i suspected in my case since it happened twice on the same street
18:51 #navit: < gernot_> I had also such a problem, but navit showed my position on a near parallel street.
18:53 #navit: < gernot_> I drive a highway, navit showed my position on a parallel field way
19:01 #navit: < ilovekiruna> yeah, pretty common
19:08 #navit: <@KaZeR> unfortunately this one is tricky to solve. We could favor the road you were last driving on, but then it would be wrong when you actually take an exit
19:10 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has joined #navit
19:11 #navit: < gernot_> Yes i use this setting. increased it from 300 to 1800. It helped a lot to stay on track. Leafing the trak work without a problem.
19:11 #navit: < ilovekiruna> couldnt one also consider the direction of travelling?
19:11 #navit: < ilovekiruna> shouldn that change if you exit?
19:13 #navit: < gernot_> navit use direction, angle and distance track - road to detect the actual position.
19:14 #navit: < ilovekiruna> especially as it also happens rather frequent, that navit thinks i am on a crossing road
19:14 #navit: < ilovekiruna> and asks me to enter the current one
19:17 #navit: < gernot_> try        <tracking cdf_histsize="0" route_pref="1800"/>  then that dont happen
19:17 #navit: < ilovekiruna> ok, will try next time
19:17 #navit: <@KaZeR> if you guys have positive feedback on the cdf maybe we should enable it by default, or at least add a menu entry to enable it from the UI
19:18 #navit: < ilovekiruna> this goes, to navit.xml, right?
19:18 #navit: < gernot_> I dont change cdf. only the route_pref="1800" is the difference
19:19 #navit: < gernot_> 300 is the default in source
19:19 #navit: <@KaZeR> ah, i thought that it wasn't enabled by default thanks gernot_
19:19 #navit: <@KaZeR> ilovekiruna: yes
19:56 #navit: < gernot_> by
19:56 -!- gernot_ [d9e52a21@gateway/web/freenode/ip.217.229.42.33] has quit []
19:59 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
21:06 -christel(christel@freenode/staff/exherbo.christel)- [Global Notice] We are excited to have announced more speakers for the freenode #live conference in Bristol, UK this October! It is not too late to register and get your tickets over at https://freenode.live -- hope to see you there!
23:04 #navit: < pmckinley> hi
23:08 #navit: <@KaZeR> hi pmckinley
23:09 #navit: < pmckinley> :-D
23:09 #navit: < pmckinley> hey buddy
23:09 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
23:38 -!- Horwitz [~mich1@p200300800E00ED00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
23:51 -!- Horwitz [~mich1@p200300800E00B700022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:51 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Fri Sep 01 00:00:11 2017