--- Log opened Fri Jul 28 00:00:06 2017 05:02 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 05:07 -!- noradtux [~noradtux@2a02:2028:521:ab01::1] has quit [Ping timeout: 240 seconds] 05:10 -!- noradtux [~noradtux@port-8376.pppoe.wtnet.de] has joined #navit 08:28 -!- jfitie [5c6e9fbe@gateway/web/freenode/ip.92.110.159.190] has joined #navit 08:28 #navit: < jfitie> hi 08:30 #navit: < jfitie> @kazer I've updated the Android screenshot in README.md to https://raw.githubusercontent.com/navit-gps/navit/trunk/contrib/images/androidtablet.png to show off all the recent changes (polys, icons, pitch) I did @ https://github.com/navit-gps/navit . Old one image was https://camo.githubusercontent.com/bc19559303f3987a7770bb6395ea01f5c096299b/687474703a2f2f77696b692e6f70656e7374726565746d61702e6f72672f772f696d616765732f322f32352f4e617 08:47 -!- jfitie [5c6e9fbe@gateway/web/freenode/ip.92.110.159.190] has quit [Quit: Page closed] 14:57 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:23 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:29 -!- noradtux [~noradtux@port-8376.pppoe.wtnet.de] has quit [Quit: Bye] 15:31 -!- noradtux [~noradtux@port-8376.pppoe.wtnet.de] has joined #navit 15:31 #navit: <@KaZeR> hi there 15:35 -!- noradtux [~noradtux@port-8376.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds] 15:37 -!- noradtux [~noradtux@2a02:2028:521:ab01:b899:86ff:feb1:b813] has joined #navit 15:41 #navit: < jkoan> Hi Kazer are you here right now? 16:03 #navit: <@KaZeR> yep 16:03 #navit: <@KaZeR> hi jkoan 16:58 #navit: < jkoan> Probably for the Navi device thing we could look for systems on a module (som) then we only need some little things around to build a full device. 16:59 #navit: < jkoan> The question is what do you think what navit needs to be sustainable in a good way for navigating (included full Linux, gpsd and so on in some minimal configuration like the tomtom OS) 17:15 #navit: <@KaZeR> jkoan: actually there might be something available soon. Can't say more until some things are confirmed, but I promise that you'll be one of the first to know! 17:16 #navit: < jkoan> Wait, are you talking about the same thing then me? 17:16 #navit: < jkoan> I was speaking about the crazy idea with the Navit device 17:23 #navit: <@KaZeR> yup :) 20:52 #navit: < jkoan> KaZeR: spam? https://wiki.navit-project.org/index.php?title=How_To_Brighten_Your_Area_With_Cushions&diff=17334&oldid=0 21:04 #navit: <@KaZeR> yep definitely. You have admin rights? 21:06 #navit: < jkoan> Yes, but I haven't a PC here 21:06 #navit: <@KaZeR> haha, searching for "navit" in the raspberry forums breaks it : https://www.raspberrypi.org/forums/search.php?keywords=navit 21:06 #navit: <@KaZeR> ok no worries i'll clean it then. It's quite simple : delete the edit and block the user 21:07 #navit: < jkoan> Yes, I know that it's easy :D 21:07 #navit: < jkoan> Wait, raspberry pi forum is still loading 21:08 #navit: < jkoan> For me it said "We are currently experiencing high traffic. 21:08 #navit: < jkoan> We'll be back shortly." 21:09 #navit: <@KaZeR> yeah, but if you search for something else than navit, it works for me 21:09 #navit: <@KaZeR> everytime i try to search for navit, i get this 21:10 #navit: < jkoan> They don't like navit :0 21:11 #navit: <@KaZeR> makes me sad! 21:12 #navit: < jkoan> For me other searches also not working 21:13 #navit: <@KaZeR> interesting. just searched "adafruit" and it worked 21:14 #navit: < jkoan> Also in error I searched for "navitf*" and it also worked (but nothing found) 21:18 #navit: < jkoan> Kazer what do you think we should do about this one? https://gitlab.com/fdroid/fdroiddata/issues/614 nobody seems to take part of it 21:37 #navit: < tryagain> jkoan I had success pubshing navit updates to fdroid by posting a pull request on fdroid-data repo, referencing a successfull automated build 21:38 #navit: < tryagain> my pull request was for https://gitlab.com/tryagain/fdroiddata/commit/57a547531d683be752735301b70b6a2e6d607b74 21:39 #navit: < tryagain> and automated test are done with https://gitlab.com/tryagain/Navit-fdroid/tree/no-makebuildserver 21:40 #navit: < jkoan> tryagain: but do you know how they detect the build ID? Must that been done before building or is it only detected after? 21:40 #navit: < tryagain> what i was done were manual updates 21:41 #navit: < jkoan> Yes, if seen :/ but did you know? :X 21:41 #navit: < tryagain> but i was going to make them automatic by making a pull request on gitlab on some event from cirecleci 21:43 #navit: < jkoan> But that is not that nice to them because someone must always merge it, so use there update tool would be better 21:44 #navit: < tryagain> iirc they want some tag on github to start automatic merge. But i'm unsure if it's really automatic, maybe they always check new version manually. 21:45 #navit: < jkoan> Probably we must change the logic in the cmake scripts also to use the latest commit instead of the current date... The Fdroid thing is really strange 21:45 #navit: < tryagain> if we have some tagging schema ready, we could try to pull-request appropriate change to fdroid-data 21:45 #navit: < jkoan> I think its really automatic 21:46 #navit: < tryagain> fdroid do not like pulling each commit as a new release. They want a tag which we have tested. 21:47 #navit: < jkoan> Yeah I know, but I was hoping they help us with there system, that was the reason for the issue. 21:47 #navit: < jkoan> Yes, I also think we should release tags to let them know 21:48 #navit: < jkoan> That was the reason we removed all those R0000 tags 21:48 #navit: < tryagain> https://gitlab.com/tryagain/fdroiddata/blob/57a547531d683be752735301b70b6a2e6d607b74/metadata/org.navitproject.navit.txt#L619 21:48 #navit: < jkoan> Yes, I know that 21:49 #navit: < jkoan> We must set update mode and check mode, but I don't know what would be the right value 21:50 #navit: < tryagain> i think i've seen some docs for that file somewhere... 21:51 #navit: < jkoan> Yes, but it's not really much everything we must know 21:52 #navit: < jkoan> It would be great if you could take part of the Fdroid problem. I think new tags would be v.* so this should be detected. 21:53 #navit: < jkoan> But I must leave now, good night 21:53 #navit: < tryagain> gn... 21:58 #navit: < tryagain> i'll drop here a few links and thoughts... 21:58 #navit: < tryagain> https://f-droid.org/docs/Build_Metadata_Reference/#Update-Check-Mode 22:00 #navit: < tryagain> Tags method is not suitable for us, as it requires AndroidManifest.xml to be present in repo. We have it autogenerated during build process. 22:05 #navit: < tryagain> HTTP method seems to be quite promising... 22:13 #navit: < tryagain> we could pull required info from https://api.github.com/repos/navit-gps/navit/tags 22:35 #navit: < tryagain> we'll have to add version code (i.e. integer number) to the tag description so fdroid can fetch it with regex from the above file 22:37 #navit: < tryagain> or maybe easier would be to host a single file with current fdroid version name (matching a tag in our github repo) and fdroid integer version code 22:38 #navit: < tryagain> we could update that file automatically from circleci when new release is posted 22:51 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 23:17 -!- Horwitz [~mich1@p200300800E6FD100022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 23:31 -!- Horwitz [~mich1@p200300800E718A00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 23:31 -!- mode/#navit [+o Horwitz] by ChanServ --- Log closed Sat Jul 29 00:00:08 2017