--- Log opened Thu Apr 12 00:00:26 2018 00:04 -!- Horwitz [~mich1@p200300800E031200022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:04 -!- mode/#navit [+o Horwitz] by ChanServ 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:36 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 264 seconds] 00:43 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 04:48 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 04:48 -!- mode/#navit [+v xenos1984] by ChanServ 05:08 -!- noradtux [~noradtux@port-7430.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds] 05:09 -!- noradtux [~noradtux@2a04:4540:8c05:e401:7418:b072:a131:649f] has joined #navit 06:30 -!- ilovekiruna [~ilovekiru@ip1f129b37.dynamic.kabel-deutschland.de] has quit [Ping timeout: 276 seconds] 07:15 -!- ColdFyre_ [~lenny@24-113-172-199.wavecable.com] has quit [Ping timeout: 264 seconds] 07:46 -!- ColdFyre [~lenny@24-113-172-199.wavecable.com] has joined #navit 11:58 -!- ilovekiruna [~ilovekiru@wlanstaff477.wlan.tu-clausthal.de] has joined #navit 11:58 -!- mode/#navit [+v ilovekiruna] by ChanServ 13:00 -!- ilovekiruna [~ilovekiru@wlanstaff477.wlan.tu-clausthal.de] has quit [Ping timeout: 260 seconds] 13:31 -!- ilovekiruna [~ilovekiru@wlanstaff477.wlan.tu-clausthal.de] has joined #navit 13:31 -!- mode/#navit [+v ilovekiruna] by ChanServ 13:48 -!- ilovekiruna [~ilovekiru@wlanstaff477.wlan.tu-clausthal.de] has quit [Ping timeout: 264 seconds] 14:02 -!- ilovekiruna [~ilovekiru@wlanstaff477.wlan.tu-clausthal.de] has joined #navit 14:02 -!- mode/#navit [+v ilovekiruna] by ChanServ 14:25 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 14:47 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 14:47 -!- mode/#navit [+v xenos1984] by ChanServ 16:00 #navit: < aerostitch> How guys would you feel to make me your release master? 16:01 #navit: < aerostitch> I'd take care about assigning the PR to milestones and cutting the releases 16:01 #navit: < aerostitch> jkoan, KaZeR ? 16:01 #navit: < aerostitch> ilovekiruna? 16:01 #navit: <+jkoan> Hi aerostitch 16:02 #navit: <+jkoan> Sounds perfect 16:02 #navit: < aerostitch> <# 16:02 #navit: < aerostitch> <3 16:02 #navit: < aerostitch> :) 16:02 #navit: <+jkoan> Trunk should be fine for release 16:03 #navit: < aerostitch> K. I will check with KaZeR (if he's fine with it) what's the current release process 16:05 #navit: <+jkoan> i think we dont have one, only make do the release via this: https://github.com/navit-gps/navit/releases you should see a draft for the release 16:05 #navit: <+jkoan> from the draft we need to remove the repo things 16:05 #navit: <+jkoan> probably you also need to update the changelog to the last state? 16:06 #navit: <+jkoan> (the v0.5.1 tag will be automatically generated when you press release from the draft) 16:08 #navit: <+jkoan> we also need to push trunk to master (manually) 16:09 #navit: < aerostitch> yup 16:19 -!- jandegr [d5db95b3@gateway/web/freenode/ip.213.219.149.179] has joined #navit 16:25 #navit: <@KaZeR> hi there 16:25 #navit: <+jkoan> hi KaZeR 16:25 #navit: <@KaZeR> hey jandegr ! 16:25 #navit: <@KaZeR> aerostitch: i love this idea 16:25 #navit: < jandegr> hi all 16:26 #navit: < aerostitch> Hi jandegr 16:26 #navit: <@KaZeR> jandegr: what's your take on the google thing? 16:26 #navit: < jandegr> I'm taking it 16:26 #navit: <@KaZeR> jandegr: awesome thanks 16:27 #navit: <@KaZeR> aerostitch: we probably should start documenting it in the wiki. In a nutshell, tag and release on github, attach relevant binaries from circleci and publish on social media 16:27 #navit: < jandegr> but first I am making a gradle ci android build 16:27 #navit: <+jkoan> KaZeR: i had the same idea of release when i wrote "Kazer?" yesterday :D but forgot when you arrived ^^ 16:31 #navit: <@KaZeR> jkoan: ha :) 16:31 #navit: <@KaZeR> jandegr: out of curiosity, what's the benefit? 16:32 #navit: < jandegr> it is the only officially supported way 16:33 #navit: < jandegr> so do a lot of work once to convert, and relax for a few years 16:33 #navit: < jandegr> for those old acra's I could still find a jar 16:33 #navit: <@KaZeR> ok that works for me. The only constraint is that we have about a week left to solve the google warning 16:34 #navit: < jandegr> won't make it in time :( 16:37 -!- Mineque [~mineque@62-210-136-72.rev.poneytelecom.eu] has quit [Quit: The Lounge - https://thelounge.github.io] 16:39 #navit: <@KaZeR> as a quick workaround, how about removing ACRA temporarily? 16:39 #navit: <@KaZeR> if we don't comply in time they're going to remove the app from the store 16:41 #navit: < jandegr> ok, will take a look 16:42 #navit: <@KaZeR> thank you 16:44 -!- Mineque [~mineque@62-210-136-72.rev.poneytelecom.eu] has joined #navit 16:53 #navit: < jandegr> first attempt https://github.com/navit-gps/navit/pull/438 ????????? 16:54 #navit: <+jkoan> jandegr: you man not cancel builds because github then said they are failed 16:55 #navit: < jandegr> when I have more to change I'm not going to wait for useless builds and CI is slow now, US already awake 16:58 #navit: <@KaZeR> we can enable a feature in circleci that'll auto-cancel redundant builds so that we don't have to do it ourselves. So if you push again on the same branch, old builds get cancelled 16:59 #navit: < jandegr> I noticed in the past it worked like that 17:00 #navit: <@KaZeR> Auto-cancel redundant builds (Does not apply to workflows) 17:00 #navit: <@KaZeR> it's actually already activated 17:00 #navit: <@KaZeR> but maybe it doesn't work because we use workflows now. we'll have to test 17:00 #navit: < jandegr> anyway, if you find somebody to test the apk from this one https://circleci.com/gh/navit-gps/navit/5797 17:01 #navit: <+jkoan> i will test now :) 17:01 #navit: < jandegr> we can finish this 'temporary remove ACRA' business 17:03 #navit: <+jkoan> why? :D 17:04 #navit: < jandegr> cause kazer asked a temporary quick solution 17:04 #navit: <@KaZeR> yeah, getting removed from the store until we cleanly fix the issue would be bad 17:04 #navit: < jandegr> it is built :) 17:06 #navit: <+jkoan> KaZeR, jandegr: https://github.com/navit-gps/navit/issues/436 what do you think about this? 17:11 #navit: <@KaZeR> jkoan: i actually like it. It's legible and unique. Also we need someone with design skills as youte doesn't have a lot of time. Would be awesome to rope redmusic27 into helping us with new icons for the ui 17:11 #navit: <@KaZeR> the qml2 UI could be soooooo pretty! 17:33 #navit: <+jkoan> jandegr: navit starts with your PR, just gut an error which i also got earlier 17:34 #navit: < Mineque> jkoan really nice but maybe more strong? 17:34 #navit: < Mineque> mean wider/bolder 17:34 #navit: < jandegr> can you be more specific about the error jkoan ? 17:35 #navit: <+jkoan> jandegr: yes, just prepare the logcat 17:38 #navit: <@KaZeR> Mineque: feel free to comment in the PR, this is up for community review 17:38 #navit: < jandegr> works on jelly bean, this just removes ACRA, does not address other issues 17:38 #navit: <+jkoan> jandegr: https://pastebin.com/9Tb8kJN2 17:38 #navit: < Mineque> KaZeR thanks for permission :P 17:39 #navit: <+jkoan> jes, removing acra works :D 17:52 #navit: <@KaZeR> coverity upped their game. It now takes only 10 mins to get the scan results 17:52 #navit: <@KaZeR> Analysis Summary: 17:52 #navit: <@KaZeR> New defects found: 0 17:52 #navit: <@KaZeR> Defects eliminated: 0 17:52 #navit: <+jkoan> nice 17:52 #navit: <+jkoan> do they also have a irc bot? 17:58 #navit: <@KaZeR> i don't think so. I think it's email only 18:00 #navit: <@KaZeR> yep 18:22 #navit: <+jkoan> KaZeR: any idea how to debug a device (tomtom) without real display output and without uart debugging port? 18:24 #navit: <@KaZeR> it 18:24 #navit: <@KaZeR> it's going to be tough 18:27 #navit: <+jkoan> I don't understand what you want to say 18:33 -!- ilovekiruna [~ilovekiru@wlanstaff477.wlan.tu-clausthal.de] has quit [Ping timeout: 264 seconds] 18:39 #navit: <@KaZeR> i meant, if you don't have a display and no way to access the uart... i don't see how you can debug it 18:45 #navit: <+jkoan> okay :( 18:46 #navit: <+jkoan> then i try to get the display running 18:49 #navit: <@KaZeR> good luck :) let us know if we can help... 18:50 #navit: <+jkoan> i dont think so :/ yesterday i read most of the buildroot doc, so i hope to figure it out soon... 18:51 -!- ilovekiruna [~ilovekiru@ip1f129b37.dynamic.kabel-deutschland.de] has joined #navit 18:51 -!- mode/#navit [+v ilovekiruna] by ChanServ 19:19 -!- jandegr [d5db95b3@gateway/web/freenode/ip.213.219.149.179] has quit [Quit: Page closed] 19:30 #navit: <+ilovekiruna> aerostitch: I also like the idea 19:30 #navit: <+ilovekiruna> @all: recently already coding all day for work, so so little time for navit :( 19:40 #navit: <@KaZeR> ilovekiruna: no worries it happens to everybody. want to resume your c++11 compliancy question? 19:40 #navit: <+ilovekiruna> KaZeR: actually I found a neat workaround 19:40 #navit: <+jkoan> KaZeR: could you read this? https://web.archive.org/web/20120820140845if_/http://www.opentom.org/wiki/images/thumb/8/8e/TomTomStart20PCBtop.jpg/400px-TomTomStart20PCBtop.jpg i cant :/ 19:41 #navit: <+ilovekiruna> jkoan: which part? 19:41 #navit: <+jkoan> the red text 19:41 #navit: <+ilovekiruna> holy crap, that is text??? 19:41 #navit: <+jkoan> yes... 19:42 #navit: <+ilovekiruna> I am trying to port a library on another similar cfd framework 19:43 #navit: <+jkoan> cfd? 19:43 #navit: <+ilovekiruna> computational fluid dynamics 19:44 #navit: <+ilovekiruna> there exist different forks of the same framework, I port a library from one fork to another 19:46 #navit: <+jkoan> sounds fragmented 19:47 #navit: <+ilovekiruna> it is a bit 19:47 #navit: <+ilovekiruna> would be like if i try to port sth from navit to zanavi, I guess 19:49 #navit: <@KaZeR> ilovekiruna: or the other way around, which would be better ;) 19:49 #navit: <+ilovekiruna> KaZeR: agreed. 19:50 #navit: <@KaZeR> jkoan: nop can't read that. but a serial port is just TX/RX.. you could try and if it doesn't work just swap the pins. If this is supposed to be a UART, you can't fry anything 19:50 #navit: <+jkoan> this is not my board... :/ 19:52 #navit: <@KaZeR> you mean that yours is really different from this one? 19:52 #navit: <+jkoan> yes 19:52 #navit: <+jkoan> also its shielded :/ 19:52 #navit: <@KaZeR> do you have the board revision/version ? 19:53 #navit: <+jkoan> https://github.com/navit-gps/NavitTom#tested-devices 19:56 #navit: <@KaZeR> thanks. your device doesn't have the dock connector, right? 19:56 #navit: <+jkoan> no :( 19:56 #navit: <@KaZeR> could you share a high-res picture of the PCB ? 19:57 #navit: <+jkoan> not right now, its currently put together 20:01 #navit: <@KaZeR> ok. your device has a USB port right? 20:01 #navit: <+jkoan> yes 20:01 #navit: <@KaZeR> it could be that they moved the UART to UART over USB to reduce the number of connectors. In that case there's probably something needed to enable UART over USB 20:02 #navit: <@KaZeR> which device are you focusing on? there's 2 in your list 20:02 #navit: <+jkoan> i dont have a prefered one 20:02 #navit: <@KaZeR> so same issue with both? 20:02 #navit: <+jkoan> yep 20:02 #navit: <@KaZeR> ok 20:05 #navit: <+jkoan> i try to fetch all crawls from the way back machine to be able to grep over everything. hopefully it will work 20:07 #navit: <@KaZeR> i'm afraid that what they have there is only about the docking connector though 20:11 #navit: <+ilovekiruna> KaZeR: about c++11, __cplusplus is my friend :) 20:13 #navit: <@KaZeR> ilovekiruna: nice 20:15 #navit: <@KaZeR> jkoan: i trust that you tested this ? http://opentom.free.fr/index.php?title=Main_Page 20:17 #navit: <+jkoan> the opentom thing works, but i try to move to current kernel with buildroot 20:17 #navit: <+ilovekiruna> KaZeR: are we also supporting building on different compilers where such things could matter? 20:18 #navit: <+ilovekiruna> KaZeR: have you seen the concept logo? What is your opinion? 20:20 #navit: <@KaZeR> jkoan: fetching some infos about the hardware using opentom could help. Like infos about the framebuffer driver or the usb serial port 20:20 #navit: <@KaZeR> ilovekiruna: not sure i understand your question about compilers 20:20 #navit: <+jkoan> i grep everything from opentom, so i should have all informations ;) 20:20 #navit: <+ilovekiruna> for example, depending on which language standards the compiler might need different keywords, like my nullptr example 20:21 #navit: <@KaZeR> ilovekiruna: i like it. It's more modern. Also this guy is obviously skilled in design, and we need someone like him. So we need to lure him into contributing more :) 20:21 #navit: <@KaZeR> ilovekiruna: ha! yeah we aim to make the code as portable as possible. That's why we have a bunch of #ifdef 20:21 #navit: <+ilovekiruna> KaZeR: I work now a lot with those 20:21 #navit: <+ilovekiruna> KaZeR: I am happy to get new people onboard. However, I find the resemblence of the N a bit weak 20:21 #navit: <@KaZeR> jkoan: i meant from a running system, it could help locate which specific driver is used for your specific device as a first step 20:22 #navit: <@KaZeR> ilovekiruna: please feel free to comment in the PR. everybody's opinion is welcome 20:25 #navit: <+jkoan> KaZeR: i tryed to find the debug port with a running system but no success 20:26 #navit: <@KaZeR> it's probably because something else is required to enable it at boot time. but using opentom we might be able to find what's required to get the display to work.. which could make things easier 20:28 #navit: <+jkoan> i think display is harder than uart, at least if i would find the ports 20:29 #navit: <@KaZeR> well it depends. we just need a basic framebuffer to see what's going on 20:30 #navit: <+jkoan> and thats the point which is failing 20:31 #navit: <+jkoan> i always get a really random display. Probably because the orientation ist fliped by 90° and the software sends the pixels in the false order 20:32 #navit: <@KaZeR> but this is failing for your kernel built with buildroot, not opentom, right? 20:32 #navit: <+jkoan> yes, because opentom uses a much older kernel 20:33 #navit: <+jkoan> but i cant use the old kernel with buildroot because its to old 20:39 #navit: <@KaZeR> but the dmesg from the old kernel could help for example 21:04 #navit: <+jkoan> theirs not much to see :/ but i will sleep now 21:38 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 22:24 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 260 seconds] 22:32 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 23:50 -!- Horwitz [~mich1@p200300800E031200022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] --- Log closed Fri Apr 13 00:00:28 2018