--- Log opened Tue Oct 24 00:00:48 2017 00:39 #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:39 #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:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 02:47 -!- noradtux [~noradtux@2a04:4540:8c03:5f01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 258 seconds] 02:52 -!- noradtux [~noradtux@port-56323.pppoe.wtnet.de] has joined #navit 05:14 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 08:14 -!- rdorsch [~rdo@mail.bokomoko.de] has quit [Quit: Coyote finally caught me] 08:16 -!- rdo [~rdo@mail.bokomoko.de] has joined #navit 08:16 -!- rdo is now known as rdorsch 14:20 #navit: < jkoan> Kazer what about a dev blog built on jekyll (github pages)? Then we can host website and blog on GitHub. Even we have versioning, can announce releases there and provide a rss feed for that. Even we can post news and developments logs (probably monthly) 14:21 #navit: < jkoan> youte: what do you think about this? Even for marketing it could be good. 14:21 #navit: < jkoan> Also hi KaZeR and youte 14:24 #navit: < jkoan> It should not be to hard to transfer the upcoming website to jekyll and add a blog to it 14:24 -!- pini [~pini@bou-fi.pustule.org] has joined #navit 14:25 #navit: < jkoan> Hi pini 14:28 #navit: < youte> hi 14:29 #navit: < youte> i will do make a website for navit 14:29 #navit: < youte> a new website 14:51 #navit: < jkoan> youte: did you seen the new one which is not yet published? 15:26 #navit: < youte> yes yes, kazer dont like no? 15:27 #navit: < jkoan> i dont know. Thought only the mages needet to be replaced 15:30 #navit: < youte> yes the old website sux xD 15:31 #navit: < jkoan> which? the current or the new-old one? (the github one) 15:35 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:36 #navit: < youte> the websitewhen use actualy 15:36 #navit: < jkoan> then i denfently agree 15:36 #navit: < jkoan> but what do you think about add an blog on the site? 15:41 #navit: < youte> good idea 15:54 #navit: < jkoan> but do you want to build a completed new site? ord only optimize the new github version? 16:01 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 16:04 #navit: < youte> i go to see the site 16:04 #navit: < jkoan> http://navit-gps.github.io/website/ 16:04 #navit: < jkoan> this one 16:04 #navit: < jkoan> images need to be replaced 16:05 #navit: < jkoan> also we probably need to replace paypal with open collective 16:07 #navit: < jkoan> and remove iphone download and add others there (tomtom, linux and so on) 16:07 #navit: < jkoan> also download should be a site with all listed in my opinion (i can do that) 16:09 #navit: < jkoan> probably the logo also needs to be replaced with svg version? 16:10 #navit: < jkoan> anything else which need to be added to the todo? 16:15 #navit: < youte> i think I think that Kazer would like to change the design of the site 16:25 #navit: < jkoan> which one? ^^ to the github site or complete new? 16:35 #navit: < youte> complete new i think 16:36 #navit: < youte> i need day with 48 hours 16:36 #navit: < youte> xD 16:36 #navit: < jkoan> yep i know your problem 16:38 #navit: <@KaZeR> hi there 16:38 #navit: < jkoan> hi KaZeR 16:39 #navit: <@KaZeR> jkoan: the blog sounds like a good idea as long as we actually post content :) 16:39 #navit: <@KaZeR> one monthly post could be a good start but we would have to really commit to it 16:40 #navit: < jkoan> yes, but even if we only use it for releases it would be good ;) 16:40 #navit: < jkoan> so move to jekyll ? :) 16:41 #navit: <@KaZeR> works for me, i've used jekyll in the past and i like it. But if we do that i hope that we'll post short articles about things that we do 16:41 #navit: <@KaZeR> like how we fix a specific ticket, or how we did something specific 16:41 #navit: < jkoan> if we would use the version right now work is already in progress :D 16:41 #navit: <@KaZeR> cool :) 16:41 #navit: < jkoan> but only for big things ;) 16:42 #navit: < jkoan> copying some of the things i did on my page :D 16:42 #navit: <@KaZeR> jkoan: maybe we should open issues in the website repository, and actually get the shit done. The website repo has been around for almost 2 years already 16:42 #navit: <@KaZeR> nice! 16:43 #navit: < jkoan> do you want to do the issues i write down earlier? then i continue work on it 16:43 #navit: <@KaZeR> ok will do 16:43 #navit: < jkoan> thx 16:44 #navit: < jkoan> add me as assigned ;) 16:48 #navit: <@KaZeR> will do! 16:49 #navit: < jkoan> thx 16:50 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 248 seconds] 17:04 #navit: < ilovekiruna> hi all 17:05 #navit: < jkoan> hi ilovekiruna 17:07 #navit: < ilovekiruna> for the website, i followed up the discussion 17:07 #navit: < ilovekiruna> did i get it wrong, or should the website be totally on github pages? 17:08 #navit: < ilovekiruna> i have some doubts how to have there dynamic content 17:08 #navit: < ilovekiruna> like php 17:08 #navit: < jkoan> this has to be discussed later ;) 17:08 #navit: < jkoan> ther will be no dynamic content 17:08 #navit: < jkoan> we dont need dynamics 17:09 #navit: < ilovekiruna> then the wiki would be still at another location, right? 17:09 #navit: < jkoan> if we add new posts (for example) the page gets rebuild 17:10 #navit: < ilovekiruna> am a bit confused now 17:10 #navit: < jkoan> why? 17:10 #navit: < ilovekiruna> are you talking about blog, website or wiki 17:10 #navit: < jkoan> blog and website combined 17:10 #navit: < jkoan> wiki will remain 17:10 #navit: < ilovekiruna> ok 17:10 #navit: < ilovekiruna> then i get it 17:11 #navit: < ilovekiruna> anything which has to be dynamic would be still with the wiki 17:11 #navit: < ilovekiruna> anything static in blog and website combined 17:11 #navit: < ilovekiruna> right? 17:11 #navit: < jkoan> right 17:11 #navit: < ilovekiruna> :) 17:11 #navit: < jkoan> add a blogpost will be easy 17:12 #navit: < ilovekiruna> what could be also nice to show that we are active is as said earlier a development feed 17:12 #navit: < ilovekiruna> of the commits 17:12 #navit: < jkoan> a commit feed exits 17:12 #navit: < ilovekiruna> :-o 17:12 #navit: < ilovekiruna> didnt know 17:13 #navit: < jkoan> https://github.com/navit-gps/navit/commits/trunk.atom 17:13 #navit: < jkoan> every repo on github has one 17:13 #navit: < ilovekiruna> but what about putting it also on the website? 17:14 #navit: < jkoan> the link or with "gui"? 17:14 #navit: < ilovekiruna> jkoan: what is new in the sailfish version bump? do you know? 17:14 #navit: < ilovekiruna> "gui" 17:15 #navit: < jkoan> dont have anything to do with sailfish, so dont know 17:15 #navit: < ilovekiruna> ah, ok 17:15 #navit: < ilovekiruna> saw that in the feed 17:15 #navit: < jkoan> what would be the benefit of the "gui"? 17:16 #navit: < ilovekiruna> showcase that we are active 17:18 #navit: < jkoan> but this would need afford and wouldn't give a *big* benefit 17:19 #navit: < ilovekiruna> I thought it wouldnt be of much afford 17:19 #navit: < ilovekiruna> if it takes larger affords, i agree, leave it 17:20 #navit: < jkoan> thy this: 17:20 #navit: < jkoan> http://jkoan.github.io/startpage/ 17:20 #navit: < jkoan> add the navit feed and switch on rss. Lokk then on the right site. whoud this ok? 17:21 #navit: < jkoan> okay forgot it, not working 17:22 #navit: < ilovekiruna> why not working? 17:22 #navit: < jkoan> for me the "startpage" is broken 17:23 #navit: < jkoan> what do you think about an javascript atom reader? this whould be possible 17:23 #navit: < jkoan> better exable: http://www.jquery-plugins.net/FeedEK/FeedEk_demo.html 17:24 #navit: < ilovekiruna> u know i see another benefit, honestly 17:24 #navit: < ilovekiruna> without looking at the feed wouldnt have known about the version bump for Sailfish 17:24 #navit: < jkoan> even by adding javascript? 17:25 #navit: < ilovekiruna> I mean for the feed 17:25 #navit: < jkoan> i also dont known ^^ 17:26 #navit: < ilovekiruna> does the github feed work for you on the jquery plugins website? 17:26 #navit: < jkoan> nop 17:26 #navit: < ilovekiruna> :( 17:26 #navit: < jkoan> but i dont know why 17:27 #navit: < ilovekiruna> me, neither :( 17:28 #navit: < jkoan> will look into it after i did the rest 17:28 #navit: < ilovekiruna> sure, no rush 17:29 #navit: < ilovekiruna> jkoan: I hope i dont ask you for too much 17:29 #navit: < ilovekiruna> have a good rest 17:29 #navit: < ilovekiruna> I just tell my suggestions, ofc you decide what you do 17:29 #navit: < jkoan> everything is okay 17:33 #navit: < ilovekiruna> KaZeR: can you give me some suggestions on my OSD? 17:43 #navit: < jkoan> KaZeR: do i have access to website? ^^ could you add me rights? 18:02 #navit: < ilovekiruna> i think i solved my problem :) 18:03 #navit: < jkoan> ilovekiruna: with what? 18:03 #navit: < ilovekiruna> yesterday, I thought i modified the navit.xml 18:03 #navit: < ilovekiruna> like discussed to include complete road names 18:03 #navit: < ilovekiruna> tested today, nothing changed, then saw that for some reason the navit.xml on my phone was still the old version :-o 18:04 #navit: < jkoan> well done :D 18:05 #navit: < ilovekiruna> strange 18:05 #navit: < ilovekiruna> even now, when checking the file in editor on phone seems nothing changed 18:05 #navit: < jkoan> android ? 18:06 #navit: < ilovekiruna> yes 18:06 #navit: < jkoan> hm okay, i dont know where the file mus been stored 18:06 #navit: < jkoan> until now this was my biggest problem 18:06 #navit: < ilovekiruna> i mean i know where i stored it 18:07 #navit: < ilovekiruna> strange thing, if i open the file in the file explorer of android seems like nothing has changed 18:07 #navit: <@KaZeR> ilovekiruna: sure 18:07 #navit: < jkoan> probably it could ne ba canged? 18:07 #navit: < ilovekiruna> am restarting phone, will test again 18:07 #navit: < jkoan> or we have a bug (file will be saved but not read from the same path) 18:08 #navit: < ilovekiruna> that wouldnt be a navit bug though 18:08 #navit: < ilovekiruna> android one :( 18:08 #navit: < jkoan> KaZeR: thx 18:08 #navit: <@KaZeR> jkoan: you now have access to the website repo 18:08 #navit: < jkoan> i was quicker :D 18:09 #navit: < jkoan> KaZeR: even push slow progress in a branch? 18:14 #navit: < jkoan> if yes i would do a first push into a brache now ;) 18:15 -!- pini [~pini@bou-fi.pustule.org] has joined #navit 18:17 #navit: <@KaZeR> jkoan: always push any progress! it shows that something is active and it helps other to contribute 18:17 #navit: <@KaZeR> jkoan: we should finish putting your country boundaries script in production : https://github.com/navit-gps/navit/issues/347 18:17 #navit: < ilovekiruna> crazy 18:17 #navit: < jkoan> i agree, but dident you want to rewrite the mapserver first? 18:18 #navit: < ilovekiruna> i copied the file on my phone from one file to another and it is different 18:18 #navit: <@KaZeR> i'd like to get some updates in the mapserver yeah, but this is going to take a long time, so we shouldn't wait on that 18:19 #navit: < ilovekiruna> anyone any idea? 18:19 #navit: <@KaZeR> ilovekiruna: will need more details :) 18:19 #navit: < jkoan> then do it ^^ i cant do anything because i dont know what to do 18:19 #navit: < ilovekiruna> KaZeR: I try to modify my navit.xml 18:19 #navit: < ilovekiruna> so i edit it on the computer. 18:20 #navit: < ilovekiruna> then I copy a modified file with a new name to my phone 18:20 #navit: <@KaZeR> jkoan: how about we do it together, to share the knowledge? 18:20 #navit: < jkoan> agree 18:20 #navit: < jkoan> if you have time see progress :D https://github.com/navit-gps/website/compare/jekyll 18:20 #navit: < ilovekiruna> then I use the android file explorer to delete the old navit.xml file and then rename my new file to navit.xml again 18:21 #navit: < ilovekiruna> the resulting file has then the content of the old navit.xml file 18:21 #navit: < jkoan> ilovekiruna: after starting navit? then navit probably overrides the file 18:21 #navit: < ilovekiruna> i dont even start navit during that process 18:22 #navit: < jkoan> then the path is probaly not writable, or something probably navit is runing and rewrite the file 18:24 #navit: <@KaZeR> navit never writes in the navit.xml file, so something else is happening 18:25 #navit: <@KaZeR> how do you check for the content of navit.xml ? on the phone, via an app? looks like something might be caching the file 18:25 #navit: <@KaZeR> jkoan: website: wow that's a lot of changes. Do we really need all of this? do you have a preview URL ? 18:25 #navit: < jkoan> right now i dont have a preview, sorry 18:26 #navit: < jkoan> its is not so much, its is to help up to be flexible later, also a made a little mistake, wait a moment 18:27 #navit: < jkoan> so check the link again (most of it just moved, only some files added 18:28 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 252 seconds] 18:34 #navit: < jkoan> KaZeR: preview will follow in a short time 18:36 #navit: <@KaZeR> ok thanks. i'm just surprised by the amount of files that we have tehre 18:36 #navit: < jkoan> but most of it just moved 18:38 #navit: < jkoan> https://preview.c9users.io/jkoan/navit-website/_site/index.html 18:38 #navit: < jkoan> thats the link while the online ide is up 18:39 #navit: < jkoan> KaZeR: if you have an cloud 9 account i can add you and we can work together 18:39 #navit: < jkoan> probably mail is also possible 18:39 #navit: < jkoan> only if you want 18:45 #navit: <@KaZeR> i think i'll probably let you take care of it if you don't mind :) 18:46 #navit: < jkoan> okay ^^ 18:46 #navit: < jkoan> wher do you want to host the site later? github pages? 18:46 #navit: <@KaZeR> what's the scope of the changes you pushed? the website looks like the one we already have, with some links removed 18:46 #navit: <@KaZeR> yeah github pages are fine. It's already hosted there :) 18:47 #navit: <@KaZeR> http://navit-gps.github.io/website/ 18:47 #navit: < jkoan> even the website at navit-project.org??? 18:47 #navit: <@KaZeR> ah no, not this one 18:47 #navit: <@KaZeR> once we feel that the new one is ready i'll just update the dns 18:48 #navit: < jkoan> okay, to fit into github pages? 18:49 #navit: < jkoan> the scope is to build a template/layout so that we can add pages and even blog into jekyll 19:04 #navit: < ilovekiruna> KaZeR: can i automate running the test cases on the test farm? Any ideas? 19:12 #navit: <@KaZeR> ilovekiruna: yes we can trigger runs from circleci using the aws api 19:12 #navit: <@KaZeR> jkoan: i see 19:14 #navit: < jkoan> KaZeR: do you know why this simple site has so much js in it? 19:15 #navit: <@KaZeR> the one that is currently in the repo? 19:15 #navit: < jkoan> yep 19:16 #navit: <@KaZeR> crappy code? :) 19:16 #navit: <@KaZeR> it was built from an all-purpose template, so it's probably bloated 19:16 #navit: < jkoan> i kno because of fancy pictures, but for example: contact-form.js 19:16 #navit: < jkoan> i think we dont even have one 19:17 #navit: < jkoan> okay, will look into it later 19:17 #navit: < jkoan> first convert the template, then we can optimize it 19:17 #navit: <@KaZeR> works for me. And thanks for your help on this. it's about time we get this done :) 19:18 #navit: < jkoan> issues already created? ^^ 19:19 #navit: < jkoan> yep, its one if the things we should do in front of the release. But its not braking the release, but could help the marketing :D 19:21 #navit: < ilovekiruna> KaZeR: I guess my test cases will be a bit ugly :8 19:21 #navit: < ilovekiruna> :( 19:24 #navit: < ilovekiruna> at least I can start navit without errors right now on Samsung Galaxy S5 (T-Mobile) 19:37 #navit: <@KaZeR> ilovekiruna: ugly isn't a concern for now, we can fix that later :) 19:37 #navit: < ilovekiruna> KaZeR: ugly in the sense, that I just "handle" any error by an empty try catch statement 19:38 #navit: < ilovekiruna> i guess i will need that, because every device on the farm depending on manufacturer, might have a different set of starting windows 19:38 #navit: <@KaZeR> well if we get some tests to trigger on the farm that's already a big step forward! 19:38 #navit: <@KaZeR> we can also start with a really restricted set of devices and expand from there 19:39 #navit: < ilovekiruna> have you seen the latest clip? 19:40 #navit: < ilovekiruna> i guess next step is to also upload a map during test setup 19:48 #navit: <@KaZeR> haven't seen it yet let me check 19:50 #navit: <@KaZeR> wow super nice ilovekiruna :) 19:50 #navit: <@KaZeR> what was the trick to handle the menu? is it hardcoded or does it react to the actual menu? 19:50 #navit: < ilovekiruna> KaZeR: which menu? 19:52 #navit: <@KaZeR> the TTS selection 19:53 #navit: < ilovekiruna> basically i used the wrong command descriptioncontains instead of textcontains 19:53 -!- youte [~youte@32.ip-37-187-37.eu] has quit [Ping timeout: 240 seconds] 20:00 #navit: <@KaZeR> ilovekiruna: but in this video, the menu is detected and handled programatically, right? 20:01 #navit: < ilovekiruna> actually the menus as such are not detected. Everything is hardcoded. If an unexpected menu showed up, it would not be handled yet 20:01 #navit: <@KaZeR> ah ok. so the click events are sent to an item, or to a given set of coordinates? 20:02 #navit: < ilovekiruna> at first i try to find an element by uiatomator, for example one which contains "Google" 20:03 #navit: < ilovekiruna> then I activate that element by running a "click" command 20:03 #navit: <@KaZeR> oh, so it's not completely hardcoded. Nice work ilovekiruna ! 20:03 #navit: < ilovekiruna> hardcoded in the sense, that I need to know the texts to search for beforehand 20:04 #navit: < ilovekiruna> and best also in the right order 20:04 #navit: <@KaZeR> that's really promising, i love it 20:04 #navit: < ilovekiruna> what do you think, how should i handle maps? 20:04 #navit: < ilovekiruna> upload as an additional file, or download in app? 20:05 #navit: <@KaZeR> that's a good question. downloading from the app would help catch some issues, but tests might fail because of a server side error 20:05 #navit: < ilovekiruna> in both cases could be quite large amounts of data :( 20:06 #navit: <@KaZeR> i'd probably start by downloading from the app, to be as close as possible from a real user experience. we can revisit if we get errors 20:06 #navit: <@KaZeR> we could download a small area only, as we can set the fake GPS coordinates anyway 20:06 #navit: <@KaZeR> like a small island or something 20:06 #navit: < ilovekiruna> any place u desire? 20:06 #navit: <@KaZeR> so many places to choose from :) 20:07 #navit: <@KaZeR> how about guam? i remember that it was a default test case for garmin 20:08 #navit: < ilovekiruna> do we have it as a defined area on the mapserver? 20:09 #navit: <@KaZeR> i can add it if needed 20:09 #navit: < ilovekiruna> would that then be also automatically in the app? 20:09 #navit: <@KaZeR> we can also use Taiwan : https://github.com/navit-gps/navit/pull/348 20:09 #navit: <@KaZeR> yes 20:11 #navit: < ilovekiruna> then Taiwan it is 20:11 #navit: < ilovekiruna> despite its politics ;-) 20:12 #navit: <@KaZeR> we can revisit at anytime :) 20:17 #navit: < ilovekiruna> I think once we know which commands to use for what, making new cases should be easy, as long as device differences are not so huge 20:18 #navit: < ilovekiruna> KaZeR: what are the standard coordinates of navit near Munich? 20:23 #navit: <@KaZeR> ilovekiruna: https://github.com/navit-gps/navit/blob/trunk/navit/navit_shipped.xml#L36 20:23 #navit: <@KaZeR> center="11.5666 48.1333" 20:25 #navit: < ilovekiruna> hope this time i c munich on the new video 20:28 #navit: <@KaZeR> fingers crossed 20:32 #navit: < ilovekiruna> not this time 20:32 #navit: < ilovekiruna> need to check a little more again 20:32 #navit: < ilovekiruna> as always 20:32 #navit: <@KaZeR> :) 21:08 -!- youte [~youte@32.ip-37-187-37.eu] has joined #navit 21:27 #navit: < ilovekiruna> KaZeR: how much time is left this month? 21:40 #navit: <@KaZeR> You have 878 free trial minutes remaining. 21:41 #navit: <@KaZeR> Found it under "Device farm settings", top right corner above the two projects name. Do you have this menu? 21:41 #navit: < ilovekiruna> wow 21:42 #navit: < ilovekiruna> found it now 21:42 #navit: < ilovekiruna> but honestly wonder how they count 21:43 #navit: < ilovekiruna> i would guess we should have used quite a bit more 21:43 #navit: <@KaZeR> well that's good for us :) 21:44 #navit: < ilovekiruna> ofc i dont mind 21:44 #navit: < ilovekiruna> but always curious as well ;-) 21:44 #navit: <@KaZeR> usage can be a bit delayed, but usually not by much 21:44 #navit: <@KaZeR> of course 21:44 #navit: <@KaZeR> we might be paying for the actual time the test is running, and this would not include start up time and things like that 21:47 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 22:02 #navit: < ilovekiruna> saw, unlimited plans are insane :-o 22:12 #navit: <@KaZeR> yeah :) 22:17 #navit: < ilovekiruna> can u check my latest run? for me it seems like to run for ages 22:23 #navit: <@KaZeR> sure 22:24 #navit: <@KaZeR> it says "start downloading map" 22:24 #navit: < ilovekiruna> that is the title i chose 22:24 #navit: <@KaZeR> ah ok 22:25 #navit: <@KaZeR> Scheduled at: Oct 24, 2017 2:49:47 PM 22:25 #navit: <@KaZeR> that's a 1/2h ago odd 22:26 #navit: < ilovekiruna> exactly 22:27 #navit: < ilovekiruna> that's why i asked you 22:27 #navit: < ilovekiruna> if u see anything more 22:27 #navit: <@KaZeR> no i don't see much, it only says that it's running 22:27 #navit: <@KaZeR> really odd 22:27 #navit: <@KaZeR> did you configure a max execution time? 22:27 #navit: < ilovekiruna> standard value 22:27 #navit: < ilovekiruna> so would be 150 mins 22:28 #navit: < ilovekiruna> maybe i just stop and restart with shorter time 22:31 #navit: < ilovekiruna> also stopping seems to take pretty long 22:31 #navit: < ilovekiruna> any ideas? 22:33 #navit: < ilovekiruna> i will try tomorrow again, hope at least after 150 minutes it will really stop 23:03 #navit: <@KaZeR> oh wow we should definitely lower that :) i don't think that we need more than 5-6 minutes now 23:03 #navit: <@KaZeR> and it'll prevent eating up all our time credits if something fails 23:35 -!- Horwitz [~mich1@p200300800E004D01022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 23:47 -!- Horwitz [~mich1@p200300800E001D00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 23:47 -!- mode/#navit [+o Horwitz] by ChanServ --- Log closed Wed Oct 25 00:00:50 2017