--- Log opened Mon Apr 16 00:00:33 2018
00:28 #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:28 #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:28 #navit: < Navit> See compile results history at http://legacy.navit-project.org/logs/navit/stats.html
00:41 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 256 seconds]
00:44 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
03:11 #navit: <+jkoan> KaZeR: hint: looking at the @Navit output there is still something left with download.navit-project.org instead of legacy.navit-project.org here in irc.
03:37 -!- noradtux [~noradtux@port-40776.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
03:38 -!- noradtux [~noradtux@2a04:4540:8c01:7001:9160:6ab6:ea8a:d78a] has joined #navit
04:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 265 seconds]
04:44 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
04:49 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
04:49 -!- mode/#navit [+v xenos1984] by ChanServ
11:17 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
13:05 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
13:05 -!- mode/#navit [+v xenos1984] by ChanServ
15:52 -!- aerostitch [~aerostitc@VEVO-LLC.bar2.SanFrancisco1.Level3.net] has joined #navit
16:09 #navit: <@KaZeR> hi there
16:09 #navit: <+jkoan> hi KaZeR
16:15 #navit: <@KaZeR> 'sup jkoan ?
16:17 #navit: <+jkoan> try to reproduce the tomtom build and get the display running with the up to date kernel
16:31 #navit: <@KaZeR> nice
19:51 -!- robertp_ [543a996b@gateway/web/freenode/ip.84.58.153.107] has joined #navit
19:54 #navit: <@KaZeR> hey robertp_ !
19:54 #navit: < robertp_> hi kazer
19:58 #navit: < robertp_> how is qt dev going? 
20:02 #navit: <@KaZeR> not making progress as fast as expected.. but i
20:02 #navit: <@KaZeR> but i've thought of a nice way to incorporate our audio framework with navit
20:03 #navit: <@KaZeR> have you made any changes to your own setup lately?
20:03 #navit: <@KaZeR> btw : i believe that your screen is 320x240, is that right?
20:06 #navit: < robertp_> right. I had to move house during the past year. So no real development...
20:09 #navit: <@KaZeR> oh ok. i'm asking because i'd be interested in your OSD layout and map settings for such a small screen
20:09 #navit: <@KaZeR> btw : i made some really good progress using buildroot to build images for the raspberry. it's pretty much fully automated, and the resulting image is ~300M
20:11 #navit: < robertp_> I have the config with OSDs on github. https://github.com/pohlinkzei/Pi_MFD_Layout/blob/audio_framework_test/navit.xml
20:12 #navit: < robertp_> But it is qutite messy there.. -.-
20:13 #navit: <@KaZeR> :D
20:13 #navit: < robertp_> Do not - never - play and develop on multiple machines.
20:14 #navit: <@KaZeR> yeah it'd be easier to read and reuse if we could move that into its own file and leverage xi:include ;)
20:14 #navit: <@KaZeR> haha
20:14 #navit: < robertp_> That really messes up the github flow. especially if one device has a wrong time setting
20:15 #navit: <@KaZeR> mm that's odd. what issue did you face?
20:15 #navit: < robertp_> kazer, do you have a documentation for the buildroot stuff? never used it
20:16 #navit: < robertp_> erm... mixed up commits. complete chaos. github takes some kind of timestamp from the files you commit. If the time server on the machine didnt get the real time ... It will set your commits between older ones...
20:18 #navit: < robertp_> The point is: I am programming in multiple VMs on different PCs. Then final testing on a Pi in a test environment. Finally final test in my car.
20:19 #navit: < robertp_> Huh... so many final tests... -.-
20:20 #navit: < robertp_> On the very last stage I get, that something is not working. So I change the missing peace of code and commit. During that time NTP didnt update the time so everything messes up.
20:29 #navit: <@KaZeR> ah i see. annoying indeed. although i would have expected git to base the history on commits chains instead of timestamps...
20:29 #navit: <@KaZeR> i need to write the buildroot doc. but in the end it's quite easy. when you'll have some time we could schedule to build your own fork/code with buildroot to make it easier for you to test things
20:31 #navit: < robertp_> I guess git expects the time stamps to be ok for machines which are connected to the internet...
20:36 #navit: <@KaZeR> that's weird, but we can probably clean it up and fix your history with rebase or patches
20:38 #navit: < robertp_> For me it is no real problem as long as it is working. At some time I need to rebase to get rid of all the stupid I-forgot-to-check-the-syntax-commits
20:54 #navit: <@KaZeR> haha
21:01 -!- robertp_ [543a996b@gateway/web/freenode/ip.84.58.153.107] has quit [Ping timeout: 260 seconds]
22:25 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds]
22:41 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
23:02 -!- Horwitz [~mich1@p200300800E796D00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
23:15 -!- Horwitz [~mich1@p200300800E0C7B00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:16 -!- mode/#navit [+o Horwitz] by ChanServ
23:17 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Tue Apr 17 00:00:35 2018