--- Log opened Sat Mar 31 00:00:05 2018
00:29 #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:29 #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:29 #navit: < Navit> See compile results history at http://legacy.navit-project.org/logs/navit/stats.html
00:33 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 260 seconds]
00:38 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
01:12 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has quit [Ping timeout: 268 seconds]
02:35 -!- noradtux [~noradtux@2a04:4540:8c02:9501::1] has quit [Ping timeout: 255 seconds]
02:40 -!- noradtux [~noradtux@2a04:4540:8c00:f01:115a:7cd0:2ae2:6b7d] has joined #navit
03:56 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
03:56 -!- mode/#navit [+v xenos1984] by ChanServ
06:24 #navit: < jkoan_> Hi aerostitch I hope you read the log :X
06:26 #navit: < jkoan_> Basically we are ready to publish 0.5.1 just now. And also Kazer would be happy with it (we actually wanted to release it last year)
06:26 #navit: < jkoan_> Only some side projects would be nicer if they got finished before the release
07:07 -!- jkoan_ is now known as jkoan
07:11 -!- mode/#navit [+v jkoan] by ChanServ
08:43 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Remote host closed the connection]
08:46 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
08:52 #navit: <+jkoan> For fib I know that we got it from somewhere, and I also was on the website some time ago, but I don't know where it was
08:53 #navit: <+jkoan> But good hint to look into this also, probably we can use a system library for this
08:56 #navit: <+jkoan> Found it: https://www.funkthat.com/%7Ejmg/jmpc/fib.html
10:31 -!- iTommix_ [~thomas@p2E5B0473.dip0.t-ipconnect.de] has joined #navit
10:33 #navit: <+jkoan> Hi iTommix_
10:34 -!- iTommix_ [~thomas@p2E5B0473.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
11:17 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
12:48 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has joined #navit
12:52 #navit: < aerostitch> hi jkoan
12:52 #navit: <+jkoan> Hi aerostitch
12:52 #navit: < aerostitch> how are you?
12:52 #navit: <+jkoan> Good, mutch to do
12:53 #navit: < aerostitch> well, that's good to be busy! ;)
12:53 #navit: <+jkoan> Yeah
12:53 #navit: < aerostitch> So for https://github.com/navit-gps/navit/pull/421 I can't find the png version of the icons. Aren't the png generated from the svg?
12:53 #navit: < aerostitch> the svg have already been renamed in the PR: navit/icons/forbiden_area.svg → navit/icons/forbidden_area.svg
12:54 #navit: < aerostitch> and navit/icons/goverment_building.svg → navit/icons/government_building.svg
12:54 #navit: <+jkoan> Oh them I missed that, let me take another look :X
12:56 #navit: < aerostitch> Also I was wondering if the configure and configure.ac in the navit/fib-1.1 folder were of any use. I'm pretty sure they are useless and I was going to do a PR to remove them but I meant to ask you 1st! ;)
12:56 #navit: <+jkoan> yes, thy are not used anymore
12:58 #navit: < aerostitch> ok thx
12:58 #navit: < aerostitch> incoming :D
12:59 #navit: <+jkoan> because we use cmake and include the c file over this function https://github.com/navit-gps/navit/blob/trunk/cmake/navit_macros.cmake#L78
13:00 #navit: <+jkoan> after that we can make the release. Do you want to include the cmake rework into the release?
13:01 #navit: < aerostitch> No, I'd like to make to releases close to one another
13:01 #navit: < aerostitch> the one with the cmake rework should be a 5.1.0 instead of a 5.0.2
13:02 #navit: < aerostitch> I think it's better to do 5.1.0 in a week
13:02 #navit: < aerostitch> what do you think?
13:02 #navit: < aerostitch> :)
13:02 #navit: < aerostitch> https://github.com/navit-gps/navit/pull/422
13:02 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 256 seconds]
13:02 #navit: <+jkoan> i think 0.5.1 was our intention as next release. we never planed a 0.5.0.2
13:03 #navit: < aerostitch> yeah sorry 5.0.1
13:03 #navit: < aerostitch> but the cmake rework introduces somewhat big changes visible to the end user
13:03 #navit: < aerostitch> so it should not be a patch version
13:04 #navit: < aerostitch> Thank you sir!
13:04 #navit: < aerostitch> Shit it's already 6:13AM, I have to go to do some cardio so I'm not late for the rest of the day. I'll catch you up later
13:04 #navit: < aerostitch> And thank you for all these reviews! ;)
13:07 #navit: <+jkoan> right now we are on 0.5.0 and next will be 0.5.1 at least from what we released as a rc so what about release 0.5.1 NOW and make the cmake rework in 0.6 (in about an month)? ^^
14:11 #navit: < aerostitch> lgtm
14:11 #navit: < aerostitch> are you sure you want to do a -rc instead of releasing directly and when bugs are found, releasing patch versions?
14:12 #navit: <+jkoan> We already did two rc's
14:13 #navit: <+jkoan> https://github.com/navit-gps/navit/releases (if you are logged in skip the draft for the release)
14:15 #navit: <+jkoan> For the future I would like to do the Workflow without rc's because it's faster
14:17 #navit: < aerostitch> sounds good
14:18 #navit: < aerostitch> sorry for the messup in the tags naming I'm a bit tired :)
14:19 #navit: < aerostitch> I was thinking about doing a tool to autogenerate the changelog and run that every months
14:19 #navit: < aerostitch> and try to push for a monthly release
14:19 #navit: < aerostitch> I mean the project is pretty active but the absence of frequent releases make it look bad :9
14:19 #navit: < aerostitch> :(
14:22 #navit: <+jkoan> I would like the idea of the change log generator and also the idea of automated nightly releases. But I think real releases should be made by hand
14:24 #navit: < aerostitch> Oh totally, the idea of the changelog generator was to run it on my side, review and then generate a PR with it
14:25 #navit: < aerostitch> The idea would be to detect words like "fix", "cleanup", "delete", "add" to put the commits in the right categories
14:25 #navit: < aerostitch> I got to look around and see how other do it
14:25 #navit: < aerostitch> maybe use the PR labels too
14:26 #navit: < aerostitch> Maybe a bot we could plug to github
14:26 #navit: <+jkoan> Why not with circleci Workflows? Generate the changelog ad add a manually review. If the review is approved the ci automatically merges it to trunk
14:27 #navit: < aerostitch> I don't know circleci very well but if it's doable this way, sure, that's a good idea
14:27 #navit: < aerostitch> would that be triggered by each commit?
14:27 #navit: <+jkoan> I can do the circleci path if you could provide the generator.
14:27 #navit: < aerostitch> sure
14:27 #navit: < aerostitch> I'll try to do something this week
14:28 #navit: < aerostitch> is it ok if I write it in go?
14:28 #navit: <+jkoan> Go is a compiler language, right?
14:28 #navit: < aerostitch> Yeah I can provide the binary directly if you want
14:29 #navit: < aerostitch> the machine you use for circleci is an Ubuntu 64bits right?
14:29 #navit: <+jkoan> I would personally like more if we would use a script language like python
14:29 #navit: < aerostitch> ok, I'll see what I can do
14:30 #navit: <+jkoan> The machine we use to generate the changelog could be any Docker image we want to
14:30 #navit: <+jkoan> What about working together on it?
14:30 #navit: < aerostitch> sure
14:30 #navit: < aerostitch> I'm looking at what's existing out there: https://github.com/skywinder/github-changelog-generator
14:32 #navit: < aerostitch> they even did a big list of changelog generators: https://github.com/skywinder/Github-Changelog-Generator/wiki/Alternatives
14:32 #navit: < aerostitch> :D
14:33 #navit: <+jkoan> The first one looks nice but relays on GitHub issues
14:36 #navit: < aerostitch> yeah and the 1st one is the only one that seems to have a decent changelog
14:37 #navit: < aerostitch> I'm amazed to see changelog generators without proper changelogs! :D
14:37 #navit: <+jkoan> thats dumb :D
14:37 #navit: < aerostitch> lol
14:38 #navit: < aerostitch> So the 1st link uses both PR and issues
14:38 #navit: <+jkoan> so the changelog generators could not be good ^^
14:38 #navit: <+jkoan> but we dont only use PR's 
14:39 #navit: < aerostitch> it relies on labels to separate out the stuffs in different categories apparently
14:40 #navit: < aerostitch> what's the problem with taking the issues in account?
14:40 #navit: < aerostitch> Oh you mean the changes that don't go through PR?
14:41 #navit: <+jkoan> i would like a changelog generator which uses git commits and no github.
14:44 #navit: < aerostitch> lg
15:06 #navit: <+jkoan> thx aerostitch
15:14 #navit: < aerostitch> I created 2 new issues on github with changes proposal
15:14 #navit: < aerostitch> if you all can have a look and propose your feedback on https://github.com/navit-gps/navit/issues/424
15:15 #navit: < aerostitch> and https://github.com/navit-gps/navit/issues/425
15:15 #navit: <+jkoan> i saw them, that was why i was writing thx :D
15:15 #navit: < aerostitch> please that would be awesome
15:15 #navit: < aerostitch> thx :)
15:15 #navit: < aerostitch> oh great:)
15:15 #navit: < aerostitch> So I couldn't assign more than 10 people to the issue so I only took the 1 biggest contributors
15:16 #navit: < aerostitch> but everybody is welcome to push a feedback
15:16 #navit: <+jkoan> i would also like to have both more up to date ;) 
15:17 #navit: <+jkoan> but for wiki i dont know what would be the best because it must be enduser friendly
15:18 #navit: <+jkoan> i think you dont mean track.debian.org  in #424
15:20 #navit: < aerostitch> sorry for that, old habits! :D
15:20 #navit: < aerostitch> hold on a sec I'm finishing an issue summarizing what we talked about on the changelogs
15:21 #navit: <+jkoan> move from trac to github issues is not as easy as it should be. i invested some time into it but would need a database backup from trac to test the import on github
15:21 #navit: <+jkoan> okay :D
15:21 #navit: <+jkoan> much stuff moving on navit, i like that
15:24 #navit: < aerostitch> :)
15:25 #navit: < aerostitch> There's not that many stuffs open on trac
15:25 #navit: < aerostitch> I can do a manual migration, no biggie
15:26 #navit: <+jkoan> with hundreds of tickets?
15:28 #navit: <+jkoan> actually we have 301 tickets
15:30 #navit: < aerostitch> I can do it in a few hours I'm pretty sure
15:30 #navit: < aerostitch> maybe not doing all at a time
15:31 #navit: < aerostitch> but I don't really mind
15:31 #navit: <+jkoan> if you want to just do it, i would be so happy :D
15:31 #navit: < aerostitch> it's just a 1-off. Writing a script, testing it, doing the db backup and all might take longer and be scarrier
15:31 #navit: < aerostitch> :)
15:31 #navit: < aerostitch> lol
15:32 #navit: <+jkoan> what about: https://github.com/yegor256/trac2github ?
15:34 #navit: < aerostitch> OMG I have to get a box with php
15:35 #navit: < aerostitch> That would break my 5 years streak without touching php
15:35 #navit: < aerostitch> :D
15:35 #navit: < aerostitch> How can I get access to the trac DB?
15:35 #navit: <+jkoan> then dont do it
15:35 #navit: <+jkoan> KaZeR :D
15:36 #navit: < aerostitch> https://github.com/robertoschwald/migrate-trac-issues-to-github
15:36 #navit: < aerostitch> this one is python...
15:37 #navit: <+jkoan> way better
15:39 #navit: < aerostitch> or https://github.com/mavam/trac-hub in ruby
15:40 #navit: < aerostitch> KaZeR is in vacations with his other half and his mini-KaZeR, but he'll be back in a few days :)
15:40 #navit: <+jkoan> the python thing looks good exept i need a account on trac... a real account with user and password
15:41 #navit: <+jkoan> i know kazer is away :D he toled us to be away around a week
15:41 #navit: < aerostitch> :D
15:41 #navit: < aerostitch> the ruby thing seems to do it directly from the DB
15:42 #navit: < aerostitch> Could you do a dump of the DB and push it somewhere I could access it? Like somewhere with a private access :)
15:42 #navit: <+jkoan> i dont have access to the servers :(
15:44 #navit: < aerostitch> I'll bug KaZeR then :)
15:44 #navit: <+jkoan> now or when hes back?
15:44 #navit: <+jkoan> *he is
15:48 #navit: < aerostitch> I just texted him but we'll probably do that when he's back. I'll do it 1st on a test repo
15:49 #navit: <+jkoan> yes, that was exactly my idea, only problem is that xmlrpc is not installed on our trac :
15:49 #navit: <+jkoan> :(
15:52 #navit: < aerostitch> and we need that for? :)
15:53 #navit: <+jkoan> normaly access to the server but i just build an egg file  and installed it to our trac :D
15:55 #navit: <+jkoan> aerostitch: !!! https://github.com/jkoan/test/issues
15:57 #navit: <+jkoan> it works, but i trigged the github abuse rate limit because i dident give my api key enought right (i think)
16:23 #navit: < aerostitch> HAHAHA
16:23 #navit: < aerostitch> nice jkoan
16:23 #navit: < aerostitch> that's why https://github.com/mavam/trac-hub seemed better
16:24 #navit: < aerostitch> as it uses the issue import api
16:24 #navit: < aerostitch> KaZeR told me he's going to give me access to the trac server today
16:24 #navit: <+jkoan> the python one uses the api also
16:24 #navit: < aerostitch> the import api?
16:25 #navit: <+jkoan> wait import api
16:25 #navit: <+jkoan> ?
16:26 #navit: < aerostitch> issue import api
16:26 #navit: < aerostitch> https://gist.github.com/jonmagic/5282384165e0f86ef105
16:27 #navit: < aerostitch> wait why do I see "status": "closed",  on some of the issues you imported?
16:27 #navit: < aerostitch> like https://github.com/jkoan/test/issues/23
16:27 #navit: < aerostitch> you're importing the complete history? :o
16:28 #navit: <+jkoan> it looks like the script is trying to do so but it never compleeds because of the rate limit right now
16:29 #navit: <+jkoan> nice thing about this: ids match when its a new repo
16:29 #navit: < aerostitch> :)
16:29 #navit: <+jkoan> but thats a thing we dont have for navit
16:30 #navit: < aerostitch> well and we probably don't want to have all the closed ones either
16:31 #navit: <+jkoan> yes
16:32 #navit: < aerostitch> I got to go. I'll be AFK all day but I'll try the other tool tonight if I have the proper access
16:32 #navit: <+jkoan> nice
16:32 #navit: <+jkoan> whats your time now?
16:32 #navit: <+jkoan> *local time
16:32 #navit: < aerostitch> 9:42 in the morning
16:33 #navit: <+jkoan> oh okay :D 
16:34 #navit: <+jkoan> thought its night but makes sense that its not :D for me its 18:44 (6:44 PM) so i will probably offline when you are back
16:46 #navit: < aerostitch> well have a good night then! ;)
16:46 #navit: <+jkoan> okay :)
16:46 #navit: <+jkoan> thx
16:46 #navit: <@KaZeR> hi there
16:47 #navit: <+jkoan> hi KaZeR
16:47 #navit: <+jkoan> good holidays? ^^ 
16:48 #navit: <@KaZeR> yep! still have today left "
16:48 #navit: <+jkoan> yes, i know :D
16:48 #navit: <@KaZeR> :D
16:48 #navit: <+jkoan> aerostitch: told me
16:49 #navit: <+jkoan> your here because of trac? :D
16:58 #navit: <@KaZeR> yeah he texted me :) i just granted aerostitch access to the server
16:58 #navit: <@KaZeR> going to have a quick look at the PR too
16:59 #navit: <+jkoan> which PR? thats all done :D
16:59 #navit: <@KaZeR> didn't read the backlog yet, but did he tell you that he's now an official co-maintainer for navit's debian package?
16:59 #navit: <@KaZeR> damn i'm late for the battle :)
16:59 #navit: <@KaZeR> thanks :D
17:00 #navit: <+jkoan> that he is a co maintainer is really nice :) but he didn’t told me
17:33 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
20:22 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
21:04 -!- tryagain [~quassel@217.107.194.38] has joined #navit
21:04 -!- mode/#navit [+o tryagain] by ChanServ
22:08 -!- tryagain [~quassel@217.107.194.38] has quit [Remote host closed the connection]
23:06 -!- Horwitz [~mich1@p200300800E760500022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
23:19 -!- Horwitz [~mich1@p200300800E6D5100022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:19 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Sun Apr 01 00:00:07 2018