--- Log opened Tue Dec 05 00:00:03 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
00:52 -!- Horwitz [~mich1@p200300800E035D00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
01:00 -!- Fester_ [5ed867dd@gateway/web/freenode/ip.94.216.103.221] has quit [Quit: Page closed]
01:05 -!- Horwitz [~mich1@p200300800E026700022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
01:05 -!- mode/#navit [+o Horwitz] by ChanServ
01:49 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds]
02:06 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
02:56 -!- gegolo [~gegolo@pool-108-26-192-67.bstnma.fios.verizon.net] has quit [Quit: Leaving]
05:36 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 268 seconds]
05:39 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
05:57 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
07:04 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
07:08 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 248 seconds]
10:09 #navit: <@KaZeR> hi there
10:09 #navit: < jkoan> hi KaZeR
10:15 #navit: <@KaZeR> 'sup jkoan ?
10:15 #navit: < jkoan> fixing datecode
10:16 #navit: <@KaZeR> sweet
10:17 #navit: <@KaZeR> i'll have a look at trac today to check if there's any blocker left for the rc1 release
10:17 #navit: < jkoan> i think its not
10:21 #navit: <@KaZeR> cool
10:30 #navit: < jkoan> version code is now working
10:35 #navit: <@KaZeR> that was fast :)
10:35 #navit: < jkoan> took more than a hour
10:57 #navit: < jkoan> KaZeR: https://github.com/navit-gps/navit/pull/376 should now work
11:03 #navit: <@KaZeR> 8thanks
11:04 #navit: < jkoan> 7no 6problem
11:04 #navit: < jkoan> :P
11:08 #navit: < jkoan> KaZeR: btw did you noticed that its only one commit (plus one merge)? now i understood how i can make this with less problems :)
11:09 #navit: <@KaZeR> ha, nice :) did you rebase?
11:09 #navit: < jkoan> probably next time i will be able to even skip the merge commit
11:09 #navit: < jkoan> yep
11:12 #navit: <@KaZeR> way to go :)
11:12 #navit: < jkoan> but one question, if i do a rebase after i pushed commits online which are included in the rebase i need to force all times of is there another way to do so?
11:14 #navit: <@KaZeR> you shouldn't need to force push if you rebase on the tip of your branch
11:16 #navit: < jkoan> oh i did not mean normal rebase, i meant rebase with a squash 
11:17 #navit: < jkoan> where some commits alreaddy pushed and others are not
11:17 #navit: <@KaZeR> if they are pushed to your remote branch but not merged into trunk, it should work too i think
11:18 #navit: < jkoan> hm okay... but this is not so relevant because i work on my own repo and only send pull request from that
11:19 #navit: <@KaZeR> ah, right
11:19 #navit: < jkoan> yesterday i discovered that the edit function of github itself is also very nice if wou only need to edit simple and a few files :D
11:19 #navit: <@KaZeR> yep :)
11:19 #navit: < jkoan> this PR was totaly done this way https://github.com/navit-gps/navit/pull/384 :)
11:20 #navit: < jkoan> and also the not finished update of the docker images
11:20 #navit: < jkoan> ah btw, could you add me to the navit docker organisation?
11:20 #navit: <@KaZeR> well there's still 5 commits in PR#384 :)
11:21 #navit: < jkoan> yes, but i squashed them while merging (online)
11:21 #navit: <@KaZeR> yep sure. what's your hub.docker.com handle?
11:21 #navit: < jkoan> jkoan
11:21 #navit: < jkoan> :D
11:21 #navit: <@KaZeR> :D
11:22 #navit: <@KaZeR> done. added you to the owner team
11:22 #navit: < jkoan> :) thx
11:22 #navit: <@KaZeR> np
11:22 #navit: < jkoan> what do you think about an own image for android? ;)
11:32 #navit: < jkoan> then we would not need the setup*.sh scripts which comsume so much time. but even if we dont need them i would keep them to update those files if the image itself is outdated
11:37 #navit: < jkoan> KaZeR: changed the PR, now its fixed
11:38 #navit: < jkoan> KaZeR: only one idea: should we add a variable to not have hard coded "/bin/date"? 
14:12 -!- pmckinley [~peter@88-110-193-6.dynamic.dsl.as9105.com] has joined #navit
14:12 #navit: < pmckinley> 8-)
14:12 #navit: < jkoan> hm pmckinley
14:12 #navit: < jkoan> whats up?
14:12 #navit: < pmckinley> well, Tyco shares
14:13 #navit: < jkoan> "Tyco shares"?
14:13 #navit: < pmckinley> ever since they put L. Dennis Kozlowski in jail they've never looked back
14:13 #navit: < pmckinley> :P
14:15 #navit: < pmckinley> hey jkoan
14:15 #navit: < pmckinley> is KaZeR AK
14:15 #navit: < pmckinley> hey @KaZeR
14:17 #navit: < jkoan> probably he is away, yes
14:26 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:39 #navit: < pmckinley> yawn
15:26 #navit: < pmckinley> HEY
15:26 #navit: < pmckinley> wake up
15:26 -!- pmckinley [~peter@88-110-193-6.dynamic.dsl.as9105.com] has left #navit []
16:09 #navit: <@KaZeR> jkoan: the android image is actually in my todo list, we should definitely do it
16:10 #navit: < jkoan> but after 0.5.1
16:12 #navit: < jkoan> but should be easy ( is everything there) but are you okay if we put all docker image files in a own repo?
16:12 #navit: < jkoan> this would help when automate the build ;)
16:12 #navit: <@KaZeR> well you actually need one repo per image :)
16:13 #navit: < jkoan> no
16:13 #navit: <@KaZeR> well you could leverage tags that's true
16:13 #navit: < jkoan> on directory in main brache is enought
16:13 #navit: <@KaZeR> but an image to build android would be really different than an image to build tomtom
16:13 #navit: < jkoan> like that one: https://github.com/codenvy-legacy/dockerfiles 
16:14 #navit: <@KaZeR> oh you meant git repo
16:14 #navit: < jkoan> yes, not docker repo :D
16:14 #navit: < jkoan> sorry
16:14 #navit: <@KaZeR> i thought you were talking about image repo
16:14 #navit: <@KaZeR> :)
16:14 #navit: < jkoan> nop, there it makes sense to have one for each
16:21 #navit: <@KaZeR> i've been thinking about the date PR. I'm wondering if we shouldn't set date to "" if it cannot be found. A date of "0000" doesn't mean much
16:22 #navit: <@KaZeR> and same for the hash. If it's not an existing git sha1 maybe we should just set it to empty.
16:22 #navit: <@KaZeR> what do you think?
16:22 #navit: < jkoan> the date must be int so it can not be empty
16:23 #navit: < jkoan> if it would be a non zero the build would fail
16:23 #navit: < jkoan> *android build
16:23 #navit: <@KaZeR> where is that restricting defined?
16:23 #navit: < jkoan> android
16:23 #navit: < jkoan> a installable package need a version code which needs to be an int
16:25 #navit: < jkoan> did you have seen the release date of 0.5.1-rc1?
16:26 #navit: <@KaZeR> oh right that's an android-specific restriction
16:27 #navit: < jkoan> yep
16:27 #navit: <@KaZeR> well we discussed tomorrow as a release date. today works also for me
16:27 #navit: <@KaZeR> you have something in mind?
16:29 #navit: < jkoan> the code as a int code is currently only used by android, but in the future i want to use it also for the specific path after the version for nightly repo packages like 0.5.2-YYMM... to be sure that the packages gets updated from the repos
16:30 #navit: < jkoan> 06.12 18:00 ^^ because of +6 addition
16:32 #navit: <@KaZeR> for the path i'd actually use the git sha. I'd use the git sha for googleplay too, but you can't
16:33 #navit: < jkoan> but did you then say it must be exactly the version 0.5.2-abc for example
16:33 #navit: < jkoan> ?
16:38 #navit: < jkoan> but of course this would also work
16:46 -!- gegolo [~gegolo@pool-108-26-199-85.bstnma.fios.verizon.net] has joined #navit
16:47 #navit: <@KaZeR> well the sha would work for *any* build, release or not 
16:48 #navit: <@KaZeR> also i'm not a big fan of the name "nightly build" as it imply a batch job that will build once a day
16:48 #navit: <@KaZeR> i personally prefer CI/CD where you build and release everytime you commit
16:49 #navit: < jkoan> okay, i try to say "ci build repo" from now on
16:51 #navit: <@KaZeR> :)
16:52 #navit: < jkoan> KaZeR: the fdroid version file on aws is finished? even with webhook and so on?
16:53 #navit: < jkoan> if not please update it to the version code "6461" and version "0.5.0" please, thats the actually last release ;)
16:55 #navit: <@KaZeR> no some work is still required
16:55 #navit: < jkoan> then it would be nice if you could update it to match the data from my last commit ;) 
16:56 #navit: < jkoan> this is the real data from this: https://github.com/navit-gps/navit/releases/tag/v0.5.0
16:58 #navit: <@KaZeR> jkoan: want to do it with me? just to make sure that i'm not the only one who knows how to
16:58 #navit: <@KaZeR> static config is here : https://github.com/navit-gps/infrastructure/blob/master/terraform/lambda/fdroid.py
16:58 #navit: <@KaZeR> so we need a PR, then we need to push the change
17:00 #navit: < jkoan> you told me some time ago thet we can make it that the aws recives data over post for example. this data will be send by an webhook from github or circleci once we push a release
17:00 #navit: <@KaZeR> yep, that part isn't done yet
17:02 #navit: < jkoan> right now i only ask you to update this: https://epu5hjnir7.execute-api.us-west-2.amazonaws.com/prod/fdroid to have the following content:
17:02 #navit: < jkoan> {"version_name": "0.5.0", "version_code": "6461"}
17:02 #navit: < jkoan> how this is done i actually dont know because i never worked with aws
17:04 #navit: <@KaZeR> exactly my point :)
17:04 #navit: <@KaZeR> look at line 15 and 16 of fdroid.py
17:05 #navit: <@KaZeR> if we replace the "live" string with the actual content, we can then deploy the change to aws easily
17:05 #navit: <@KaZeR> i could do it directly but i'd rather do it with you so you know at least some of the steps
17:06 #navit: < jkoan> okay, that was what i understand, but where should the data came from?
17:06 #navit: <@KaZeR> soon, from circleci
17:07 #navit: <@KaZeR> right now, from you :)
17:07 #navit: < jkoan> that was actually not what i was meaning, what i was meaning is there from in the script, variable, db or so on?
17:08 #navit: <@KaZeR> right now it's hardcoded but soon we'll pull that from dynamodb
17:09 #navit: < jkoan> but aws is actually costing mony, wouldent it be more easy to have a file in github and use that one? the ci could also edit that one
17:10 #navit: <@KaZeR> https://aws.amazon.com/dynamodb/pricing/#free-tier
17:10 #navit: <@KaZeR> we could also have a file in github yes
17:11 #navit: < jkoan> is the free tier only once like the device farm or is it every month?
17:12 #navit: <@KaZeR> it depends of the resource. . DynamoDB’s free tier does not expire at the end of your 12 month AWS Free Tier term and is available to all AWS customers.
17:13 #navit: < jkoan> okay
17:13 #navit: < jkoan> btw, did you read this one? : https://github.com/navit-gps/navit/releases/tag/untagged-cbbae24e23eb76d425c9
17:14 #navit: <@KaZeR> "Navigators" i  like that :)
17:15 #navit: <@KaZeR> i think that it's too early to advertise readthedocs we need more content
17:15 #navit: < jkoan> oh, the link changes every time somebody edits something :X
17:15 #navit: < jkoan> but its only draft as you have probably seen.
17:16 #navit: < jkoan> its also to early to announce not existent repo servers ;)
17:16 #navit: < jkoan> but i dont have any access to set them up :P
17:16 #navit: <@KaZeR> oh right :)
17:17 #navit: < jkoan> apt will be easy, the docker image is already very good. :)
17:22 #navit: <@KaZeR> could you share your pubkey again? i don't see it in our pms
17:22 #navit: < jkoan> done
17:46 -!- noradtux [~noradtux@port-53181.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
17:47 -!- noradtux [~noradtux@2a02:2028:546:9601:ec4:7aff:fe33:3dc1] has joined #navit
17:55 -!- mvglasow [~mvglasow@94.135.166.42] has joined #navit
17:57 #navit: < mvglasow> hi KaZeR, hi jkoan, hi everyone else
17:57 #navit: < jkoan> hi mvglasow
18:08 #navit: < mvglasow> I'm just working on the traffic module and need a second opinion or two on a design decision...
18:09 #navit: < jkoan> i could read something if you want
18:09 #navit: < mvglasow> Context is matching locations from a traffic report to the map
18:09 #navit: < jkoan> yes, probably one of the most annoying thinks
18:09 #navit: < jkoan> *things
18:10 #navit: < mvglasow> we have two approximate locations (beginning and end) as well as some attributes for the road affected
18:10 #navit: < mvglasow> to match them to the actual segments, I will probably need to borrow some routing functionality
18:10 #navit: < mvglasow> such as building a route graph
18:11 #navit: < mvglasow> similar to what route.c does, though not exactly the same, but some functions can be reused
18:11 #navit: < mvglasow> now: currently traffic is its own core module with a source file, traffic.c, and its header file, traffic.h
18:12 #navit: < mvglasow> the routing stuff I would need to use is in route.c but not exported through the header
18:12 #navit: < mvglasow> which basically leaves me with three options:
18:13 #navit: < mvglasow> 1. export everything I need, i.e. structs and function prototypes, through route.h
18:13 #navit: < mvglasow> would do the trick but may not be the cleanest part
18:13 #navit: < mvglasow> 2. move all the traffic functionality into route.c/route.h
18:14 #navit: < mvglasow> not very clean either, as traffic and route are two quite distinct functionalities that just happen to share some code
18:15 #navit: < mvglasow> 3. define a new header file, route_protected.h or the like, from which I export these delarations and which both route.c and traffic.c would include
18:15 #navit: < mvglasow> probably cleanest but I'm not sure if this is in any way unexpected for fellow Navit devs
18:16 #navit: < mvglasow> or do we have any other cases where core modules are closely interlinked and need to share some code between each other, but not necessarily with the outside world
18:16 #navit: < mvglasow> ?
18:16 #navit: < mvglasow> opinions?
18:17 #navit: < jkoan> for the last question you must probably wait for KaZeR
18:17 #navit: < jkoan> but i would also prefer the option 3 this sound the most logic one.
18:18 #navit: < jkoan> i dont like 2 at all, and 1 could be a good compromise 
18:22 -!- mvglasow [~mvglasow@94.135.166.42] has quit [Ping timeout: 258 seconds]
18:35 -!- mvglasow [~mvglasow@94.135.166.42] has joined #navit
20:22 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
20:46 #navit: < jkoan> KaZeR: do we like letsencrypt? the question is about if i should add automatic renew of the certs to the containers (main container). I will explain my structure of the containers and so on (everything should been structured)
22:19 -!- mvglasow [~mvglasow@94.135.166.42] has quit [Quit: Leaving]
23:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 255 seconds]
23:42 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
--- Log closed Wed Dec 06 00:00:05 2017