--- Log opened Fri Jan 13 00:00:06 2017 02:29 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 03:54 -!- jjelen [jjelen@nat/redhat/x-mndoectuxnpvdauz] has joined #navit 04:41 -!- kazer [~kazer@2601:643:8104:ba60:eea8:6bff:fef8:449] has quit [Ping timeout: 245 seconds] 04:56 -!- kazer [~kazer@2601:643:8104:ba60:eea8:6bff:fef8:449] has joined #navit 10:19 -!- jjelen [jjelen@nat/redhat/x-mndoectuxnpvdauz] has quit [Ping timeout: 240 seconds] 10:58 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 11:43 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 12:06 -!- noradtux [~noradtux@2a02:2028:54d:6200::1] has quit [Ping timeout: 240 seconds] 12:12 -!- noradtux [~noradtux@2a02:2028:867:c400::1] has joined #navit 12:45 -!- jandegr [50c84d9c@gateway/web/freenode/ip.80.200.77.156] has joined #navit 12:49 -!- jandegr [50c84d9c@gateway/web/freenode/ip.80.200.77.156] has quit [Client Quit] 13:19 #navit: < kazer> hi there 13:21 #navit: < kazer> 7~ 13:37 -!- circleci-bot [~circleci-@ec2-54-167-79-107.compute-1.amazonaws.com] has joined #navit 13:37 #navit: < circleci-bot> Failed: pgrandin's build (#1564; push) in navit-gps/navit (trunk) -- https://circleci.com/gh/navit-gps/navit/1564?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc 13:37 -!- circleci-bot [~circleci-@ec2-54-167-79-107.compute-1.amazonaws.com] has quit [Client Quit] 13:45 -!- jandegr [50c84d9c@gateway/web/freenode/ip.80.200.77.156] has joined #navit 13:50 #navit: < kazer> hi jandegr 13:53 #navit: < jandegr> hi kazer 14:04 #navit: < kazer> 'sup jandegr ? 14:08 #navit: < jandegr> all calm after snow and wind, 120km/h++ in dieppe last night 14:14 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit 14:14 #navit: < zintor> hi @all 14:24 #navit: < zintor> the part on the wiki-page of building navit in SailfishOS SDK is ok now. I installed a fresh SDK and updated the steps. 14:25 #navit: < zintor> I also worked a bit on the OSD, but unfortunately I can't copy new configurations easily to the SDK :( 14:26 #navit: < zintor> I use scp to copy the xml file. but then navit compaints about wrong char in first place 14:27 #navit: < zintor> another issue is, then I use "include" in navit.xml, I can't drag&drop in the map 14:36 -!- jandegr [50c84d9c@gateway/web/freenode/ip.80.200.77.156] has quit [Quit: Page closed] 14:39 #navit: < kazer> hi zintor 14:39 #navit: < zintor> hi kazer 14:39 #navit: < kazer> thanks for your PR on github. Git in command line is not difficult, so if you have questions just ask :) 14:39 #navit: < kazer> thanks for the wiki update. Let me have a look to get some context 14:41 #navit: < zintor> I have to understand clearly how git works. fork, change, push, commit, PR,... 14:42 #navit: < zintor> my first PR worked :) thanks 14:42 #navit: < zintor> normally, I you install SailfishOS SDK, you should compile and run it. 14:46 #navit: < zintor> Now, I am working on OSD for "Jolla-look" for Navit and will post it on the wiki page. do you get a info, if the page change or a new file is uploaded? 14:56 #navit: < kazer> i'll have to check my watchlist. will definitely add this one 14:57 #navit: < zintor> ok 14:59 #navit: < zintor> do I understand it right, that I should work with metalstrolchs fork for SailfishOS unless you (or others) give me other instructions for testing? 15:00 #navit: < kazer> mmm i'm not sure. We want to foster collaboration within the navit repo itself 15:00 -!- Basilic_ [~Basilic@228-221-190-109.dsl.ovh.fr] has joined #navit 15:00 #navit: < kazer> one way to integrate metalstrolch's changes would be for me to fork his fork, and then submit a PR from my fork against the official repo 15:01 #navit: < kazer> it's getting complicated, so instead i think that we should just use a branch in the official repo for the work in progess 15:02 #navit: < zintor> you know better than me 15:02 #navit: < kazer> i'm reviewing the instructions for sailfishOS. If we can find a way to do it without the virtual machine we could have the builds running in CircleCI (so, fully automated) 15:02 #navit: < kazer> are you in touch with metalstrolch, or just using his repo? 15:02 #navit: < zintor> I am just using his repo 15:03 -!- Basilic [~Basilic@228-221-190-109.dsl.ovh.fr] has quit [Ping timeout: 240 seconds] 15:03 #navit: < kazer> ok 15:03 #navit: < kazer> maybe we can start with something easier, your scp issue :) 15:05 #navit: < kazer> can you post the xml file on http://navit.pastebin.com/ ? 15:06 #navit: < zintor> well, I get following message then I try to use scp'ed xml 15:06 #navit: < zintor> error:navit:main_real:Error parsing config file '/home/nemo/.navit/navit.xml': Error on line 1 char 1: Document must begin with an element (e.g. ) at line 1, char 1 15:06 #navit: < zintor> there is a char in first place, but only then I scp it 15:07 #navit: < zintor> with c&p in nano running in SDK, it works! 15:08 #navit: < kazer> that is really really strange. if you md5 the file before and after, the checksum changes? 15:09 #navit: < kazer> can you share the exact command you use for the scp? 15:09 #navit: < zintor> no checksum was the same 15:11 #navit: < zintor> scp -P 2223 -i ~/SailfishOS/vmshare/ssh/private_keys/SailfishOS_Emulator/nemo /home/steffen/navit/SailfishOS/navit.xml nemo@localhost:/home/nemo/.navit/ 15:13 #navit: < kazer> can you show me the result of "head -n1 /home/steffen/navit/SailfishOS/navit.xml 15:16 #navit: < zintor>