--- Log opened Fri Oct 27 00:00:53 2017
00:18 #navit: <@KaZeR> Number6: i put your name on the wince build. There's no escape :)
00:18 #navit: <@KaZeR> https://trac.navit-project.org/ticket/1253#comment:14
02:48 -!- noradtux [~noradtux@port-1775.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
02:50 -!- noradtux [~noradtux@port-23849.pppoe.wtnet.de] has joined #navit
05:03 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:24 -!- wondiws [~Jasper@5ED7DF59.cm-7-8d.dynamic.ziggo.nl] has quit [Quit: Leaving]
07:49 -!- wondiws [~Jasper@D57E4E6A.static.ziggozakelijk.nl] has joined #navit
07:51 #navit: < wondiws> hi there
07:57 #navit: < wondiws> hi jkoan KaZeR 
07:57 #navit: < jkoan> hi wondiws
07:58 #navit: < jkoan> KaZeR: is probably sleeping (-7h from germany)
07:59 #navit: < wondiws> jkoan, I'm still trying to get this GPS receiver to work. Maybe you know the tool "gpsmon"? When I do "gpsmon /dev/ttyUSB0" I get my coordinates, so that seems to work as easy as that. How can I get it to work in navit? :)
08:00 #navit: < jkoan> yes i know gpsmon
08:01 #navit: < jkoan> in gpsmon everything is right?
08:01 #navit: < wondiws> jkoan, as far as I can tell :)
08:01 #navit: < jkoan> okay
08:02 #navit: < jkoan> what do you configured in navit.xml?
08:03 #navit: < jkoan> search for vehicle 
08:04 #navit: < wondiws> <vehicle name="beitian" enabled="yes" active="1" source="file://dev/ttyUSB0"/>
08:04 #navit: < wondiws> and the Local GPS
08:04 #navit: < jkoan> do you see the problem?
08:04 #navit: < wondiws> and I uncommented the (windows) serial:COM4, but that doesn't seem to work
08:04 #navit: < wondiws> jkoan, I do not see the problem
08:05 #navit: < wondiws> jkoan, are you hinting towards a missing profile?
08:05 #navit: < wondiws> missing baudrate?
08:05 #navit: < wondiws> I thought 9600 was the default
08:05 #navit: < jkoan> do you have more then on enabled?
08:05 #navit: < jkoan> baurdrate is missing yes, default is something around 4k
08:05 #navit: < wondiws> jkoan, no, I can check that in settings
08:06 #navit: < wondiws> only one is enabled
08:07 #navit: < jkoan> okay, then add baudrate and everything should be fine
08:07 #navit: < wondiws> where and how?
08:08 #navit: < wondiws> I do have to use file://
08:08 #navit: < wondiws> ?
08:08 #navit: < wondiws> right?
08:08 #navit: < jkoan> yes, file is right
08:08 #navit: < jkoan> add baudrate="9600" to the vehicle
08:11 #navit: < wondiws> jkoan, right, now it says "no leading $", which makes sense if you start reading somewhere in the middle :P
08:11 #navit: < jkoan> again and again or only once?
08:12 #navit: < jkoan> https://github.com/navit-gps/navit/blob/trunk/navit/vehicle/file/vehicle_file.c#L968 here is the default baudrate ;)
08:13 #navit: < wondiws> again and again
08:13 #navit: < wondiws> and now buffer overflow, not it does have the leading $
08:14 #navit: < wondiws> nmea buffer overflow
08:15 #navit: < jkoan> are you sure that 9600 is right? :X
08:15 #navit: < wondiws> jkoan, 100%
08:16 #navit: < wondiws> jkoan, besides, I can read the ascii in the console
08:16 #navit: < jkoan> thats strange
08:21 #navit: < wondiws> jkoan, I can route it via gpsd, right?
08:22 #navit: < jkoan> for me it fixed that
08:35 #navit: < wondiws> now I have to find out how to use gpsd :S
08:40 #navit: < wondiws> jkoan, help! :P
08:40 #navit: < jkoan> dpkg-reconfigure gpsd ?
08:42 #navit: < wondiws> jkoan, nothing changes, "gpsd -N" is running
08:42 #navit: < wondiws> but what device does it use?
08:42 #navit: < wondiws> gpsdctl doesn't do anything either
08:43 #navit: < jkoan> look into: /etc/default/gpsd
08:44 #navit: < wondiws> jkoan, "use usb hotplugging to add new usb devices automatically", does that include USB terminals, like /dev/ttyUSB0?
08:45 #navit: < jkoan> i dont think so
08:45 #navit: < jkoan> add /dev/ttyUSB0 to /dev/ttyUSB0
08:45 #navit: < jkoan> fail
08:45 #navit: < jkoan> to DEVICES
08:46 #navit: < jkoan> and restart of cause
08:46 #navit: < wondiws> jkoan, already did ;)
08:46 #navit: < jkoan> after added?
08:47 #navit: < wondiws> jkoan, and I set navit back to gpsd, and YES, I see a blue circle now at my position ;)
08:48 #navit: < wondiws> a few meters off though, my desk is on the street, but close enough :P
08:48 #navit: < wondiws> thanks jkoan 
08:50 #navit: < jkoan> but this is probably not a navit bug. Its more or less depending on the GPS
08:53 #navit: < wondiws> jkoan, how do I rotate? I unintentionally rotated the map appearantly
08:55 #navit: < jkoan> this was probably automatically, it rotates it in the direction of moving. But you can set northing
08:58 #navit: < wondiws> jkoan, and now my position is set correctly, even within the outline of the building on the map
09:05 -!- wondiws2 [~Jasper@D57E4E6A.static.ziggozakelijk.nl] has joined #navit
09:05 -!- wondiws [~Jasper@D57E4E6A.static.ziggozakelijk.nl] has quit [Remote host closed the connection]
09:10 #navit: < jkoan> wondiws2: nice :)
11:34 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds]
13:08 -!- wondiws2 is now known as wondiws
14:44 -!- wondiws [~Jasper@D57E4E6A.static.ziggozakelijk.nl] has quit [Quit: Leaving]
15:08 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
16:02 -!- wondiws [~Jasper@5ED7DF59.cm-7-8d.dynamic.ziggo.nl] has joined #navit
16:04 #navit: <@KaZeR> hi tehre
16:04 #navit: < jkoan> hi KaZeR
16:05 #navit: < jkoan> little question, which ide do you use do develop navit?
16:12 #navit: < jkoan> also, questions about two api endpoints: first is the fdroid endpoint ready? second: do we have at mapserver a list (xml/json) of all predefined areas?
16:24 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
16:58 #navit: <@KaZeR> KaZeR: vim :)
16:58 #navit: < jkoan> hm okay
16:59 #navit: < jkoan> i spend some time today to setup eclipse again :D 
16:59 #navit: <@KaZeR> 1) is almost ready. we don't have 2), that's why i was so interested in your script
16:59 #navit: <@KaZeR> i've used eclipse in the past, it's quite good
16:59 #navit: < jkoan> yes, i know, but not for the android build
17:00 #navit: < jkoan> 2) the script is online and outputs csv data ;)
17:03 #navit: <@KaZeR> the script is in the repo, not online ;) and we should probably use json, much easier to manipulate
17:04 #navit: < jkoan> but the script only has countrys, no sub regions
17:04 #navit: <@KaZeR> well it's a start. we are missing many, many countries currently
17:05 #navit: < jkoan> also i want to remove the filesize out of the file list and use the size which is reportet by the server
17:05 #navit: <@KaZeR> we had a request a few days ago for Taiwan as a seperate download for example
17:05 #navit: <@KaZeR> btw : the country list is required to provide map download on linux too (except of just having it for android)
17:06 #navit: < jkoan> i know, i merged it
17:06 -!- MarcR [~MarcR@p5B00E033.dip0.t-ipconnect.de] has joined #navit
17:06 #navit: <@KaZeR> so this proves that there's a real need for it :)
17:06 #navit: < jkoan> yup, i gree
17:06 #navit: < MarcR> Hi everybody!
17:06 #navit: < jkoan> right now i look into android
17:06 #navit: < jkoan> hi M
17:06 #navit: < jkoan> *MarcR
17:07 #navit: < MarcR> Hi J ;)
17:07 #navit: < jkoan> :D
17:07 #navit: < jkoan> tab complete has not worked so good :D 
17:07 #navit: < MarcR> my gps neo is up and running fine again 
17:08 #navit: < MarcR> but it really runs at serial0 
17:09 #navit: < jkoan> MarcR: this info is not for me right? ^^
17:09 #navit: < MarcR> nope 
17:09 #navit: < MarcR> sorry ;)
17:09 #navit: < MarcR> for KaZeR
17:09 #navit: < jkoan> okay i already wondered 
17:10 #navit: < MarcR> I have seean a platine layout of the pi, today. the Pi3 really has only a small keramic bluetooth and wlan antenna?! 
17:11 #navit: <@KaZeR> hey MarcR 
17:11 #navit: < MarcR> hey
17:11 #navit: <@KaZeR> jkoan: talking about android there is an issue with version tagging
17:12 #navit: <@KaZeR> the version.cmake script doesn't seem to be called
17:13 #navit: < jkoan> where?
17:13 #navit: < jkoan> do you have a error log?
17:14 #navit: <@KaZeR> run cmake on your box, the git tag isn't displayed
17:15 #navit: < jkoan> for me it is (or we tak about different things)
17:16 #navit: <@KaZeR> wait it might be a brain fart
17:17 #navit: < jkoan> i must fix something else in the same file in the next time, so its no problem :D
17:21 #navit: <@KaZeR> MarcR: yeah that antenna is so small! but it works ok. Not worse than the super cheap, super small wifi dongles
17:23 #navit: < MarcR> KaZeR: thats right, there are nearly the same signal power. 
17:26 #navit: < MarcR> KaZeR: any update about Raspbian Jessie and qt5?
17:31 #navit: <@KaZeR> progress but no cigar yet. hopefully soon
17:32 #navit: < MarcR> KaZeR: no problem
17:32 -!- ColdFyre [~lenny@24-113-108-124.wavecable.com] has quit [Remote host closed the connection]
17:35 #navit: < youte> hi
17:36 #navit: <@KaZeR> hey youte 
17:39 #navit: < jkoan> hi youte
17:42 #navit: < jkoan> KaZeR: https://static.jkoan.de/cloud/index.php/s/JGvsEDL1E3QGm2E i think right is what it should look like? ;)
17:46 #navit: <@KaZeR> jkoan: not sure what i'm looking at
17:46 #navit: < jkoan> it should be a picture :D
17:47 #navit: <@KaZeR> it is, but it's the same menu twice.. about downloading a map
17:47 #navit: < jkoan> its the delete map dialog (current playstore is left, fixed is right) 
17:48 #navit: < jkoan> look at "Färöer 108MB" text
17:48 #navit: <@KaZeR> ah, i see now
17:48 #navit: <@KaZeR> nice
17:48 #navit: < jkoan> and even it is less code :D
17:50 -!- ColdFyre [~lenny@24-113-108-124.wavecable.com] has joined #navit
17:51 #navit: < jkoan> api level 1 is okay? :-P
17:51 #navit: < jkoan> (i only looked at the part i changed)
17:52 #navit: < Number6> Circle is running Ubuntu 14.04, yeah? 
17:52 #navit: < jkoan> we build on own docker images as far i know
17:53 #navit: < jkoan> https://github.com/navit-gps/navit/blob/trunk/.circleci/config.yml but Yes its 14.04
17:53 #navit: < jkoan> line 4
17:53 #navit: < Number6> IIRC it's a ununtu 14.04 image running on docker - at least that's what the YML looks like
17:53 #navit: < jkoan> yep
17:53 #navit: < Number6> Perfect. I'm gonna spin up a 14.04 box and try to get WinCE working again
17:54 #navit: < jkoan> nice :)
17:55 #navit: < jkoan> Number6: we working to bring 0.5.1-rc1 out soon ;)
17:56 #navit: <@KaZeR> Number6: circleci v1 was only 12.04/14.04, but with v2 we can pick any docker container (and can build our own)
17:56 #navit: <@KaZeR> Number6: are you familiar with docker?
17:57 #navit: < Number6> KaZeR: Yep, very familiar - use it every day in work
17:59 #navit: <@KaZeR> Number6: cool
18:02 #navit: < Number6> PR to truck branch? 
18:03 #navit: <@KaZeR> actually i just enabled branch protection
18:03 #navit: <@KaZeR> perfect timing
18:03 #navit: <@KaZeR> because i fucked up again and should have pushed to a branch
18:04 #navit: <@KaZeR> so now, trunk is protected
18:04 #navit: <@KaZeR> to protect us against myself :D
18:04 #navit: < Number6> :-D
18:04 #navit: < jkoan> recording to the last commit on trunk: the "exit -1" part is not important because in line 2 "set -e" is set
18:07 #navit: <@KaZeR> jkoan: https://circleci.com/gh/navit-gps/navit/3359 look at the android build output
18:08 #navit: < jkoan> hm okay, strange. i dont said something
18:11 #navit: < jkoan> KaZeR: Android Notifications in low versions are a mess...
18:12 #navit: < wondiws> MarcR, yes, I have the RPi3, so I can confirm about the bluetooth and Wlan
18:13 #navit: <@KaZeR> wondiws: are you planning on running navit on your pi or a computer?
18:13 #navit: < wondiws> KaZeR, I ran it on my Lenovo Yoga
18:14 #navit: < MarcR> wondiws: Ok 
18:17 #navit: <@KaZeR> wondiws: ok
18:17 #navit: <@KaZeR> wondiws: we'll have to look into your 'vehicle file' issue as it should have worked
18:18 #navit: < wondiws> KaZeR, oh, you mean my Beitian BN-880 should have worked without the gpsd intermediation?
18:19 #navit: < wondiws> KaZeR, I haven't tried it on the very last version of Navit I think, I will do that later this evening
18:21 #navit: <@KaZeR> wondiws: yes that's what i meant :) ok thanks. i could look into it but i want to finish the build for MarcR first
18:22 #navit: < wondiws> KaZeR, you mean his problem with compiling?
18:23 #navit: < MarcR> KaZeR: thx, but no need to rush for me
18:23 #navit: < MarcR> KaZeR: if there are more important things on your todo list - feel free to do them 
18:23 #navit: <@KaZeR> wondiws: partially, but mostly providing an image optimized for the pi
18:24 #navit: <@KaZeR> MarcR: well this is actually in my todo list, because it'll vastly reduce the pain for new users who want to try navit on pi
18:24 #navit: < jkoan> yes, and my is navit on android (first steps and also bugs and ugly design)
18:25 #navit: < wondiws> KaZeR, so navit is in debian, but not in the raspbian repo?
18:26 #navit: < wondiws> KaZeR, which one of the credited people in "About" are you? :)
18:26 #navit: < MarcR> KaZeR: Ok got you. :) 
18:29 #navit: < wondiws> KaZeR, it seems to work now in 0.5.1git
18:29 #navit: < wondiws> not in 0.5.0 debian
18:29 #navit: < wondiws> and now I have a nighttime map? :P
18:30 #navit: < wondiws> KaZeR, just to make sure you're not going to fix a bug that has already been fixed :P
18:30 #navit: <@KaZeR> wondiws: i'm the one with the French name :)
18:30 #navit: < wondiws> KaZeR, that's close enough
18:30 #navit: <@KaZeR> wondiws: i appreciate you double checking for the bug :)
18:43 #navit: < wondiws> KaZeR, so it works not in 0.5.0, but it does work in 0.5.1 ;)
18:43 #navit: < wondiws> and I see you have a nighttime theme or something? :P
18:44 #navit: < Number6> KaZeR: Oh wow, the WinCE docs are OLD!
18:55 #navit: <@KaZeR> wondiws: is your gps speaking nmea or something different? one of the latest change in that vehicle is that we added support for more than nmea
18:55 #navit: <@KaZeR> Number6: haha yeah
18:57 #navit: < wondiws> KaZeR, I think it's NMEA though, "gpsmon" understands it
18:57 #navit: < wondiws> it says NMEA 0183
19:04 #navit: <@KaZeR> ok thanks
19:08 #navit: < Number6> initial build job PR sent in :-D
19:08 #navit: < jkoan> jup, already seen :)
19:08 #navit: < Number6> cmake will fail, but at least it gets to the make stage
19:09 #navit: < Number6> I feel like I've jumped into a time machine back to 2010... If only I could have told my younger self some insights - like buy a lot of Bitcoin
19:09 #navit: < jkoan> :D
19:12 #navit: < wondiws> wow, I read that Catalonia has actually declared independence?
19:13 #navit: <@KaZeR> Number6: wow that was fast
19:13 #navit: <@KaZeR> haha Number6 
19:13 #navit: <@KaZeR> wondiws: lol i read California and was like wtf? 
19:15 #navit: < Number6> KaZeR: It'll fail, but at the make step - not the initial cmake step. Unless I FUBAR'd the way circle does compiles :-)
19:15 #navit: <@KaZeR> that's already progress :)
19:28 #navit: <@KaZeR> Number6: your "make sure to undo this" makes me think that we could have the CI skip some jobs based on a branch naming convention
19:31 #navit: < Number6> Yeah, like what would usually happen is that you'd have a master branch, with different envs per branch - so "master-linux", "master-android", etc. It's a nightmare to manage, though
19:33 #navit: <@KaZeR> oh i was thinking something in the line of having a branch 'platform/wince' and have the ci skip the jobs that don't match the platform name. no hardcoding that way, and we would only base the filter on the 'platform
19:33 #navit: <@KaZeR> keyword
19:34 #navit: < wondiws> KaZeR, I just remembered, it's not something I think about it everyday, but my country, the Netherlands also got its independence from Spain, so we have something in common with the Catalonians
19:35 #navit: < wondiws> so when my father said the Catalonians were insane, I said: no more insane than we were ;)
19:45 #navit: <@KaZeR> haha
19:46 #navit: < MarcR> working on auto pair with my phone via bluetooth right now .... 
19:48 #navit: < jkoan> KaZeR: default soft keyboard on android instead of navits one?
19:49 #navit: <@KaZeR> wondiws: actually the part of France i'm from was also under spanish ruling during the spanish netherland era!
19:49 #navit: <@KaZeR> jkoan: probably yeah. provides a more native user experience
19:50 #navit: < wondiws> KaZeR, where do you live now? According to jkoan you live in -7 hours time difference from Germany
19:50 #navit: <@KaZeR> Berkeley, CA. So probably more -9h :)
19:56 -!- mvglasow [5cd90b88@gateway/web/freenode/ip.92.217.11.136] has joined #navit
19:58 #navit: <@KaZeR> mvglasow \o/
19:59 #navit: < mvglasow> Hi KaZeR
19:59 #navit: < jkoan> hi mvglasow
19:59 #navit: < mvglasow> have there been any changes regarding commits to trunk?
19:59 #navit: < mvglasow> I just tried to push and got an error message
19:59 #navit: <@KaZeR> yep, i protected the branch. To protect us from me doing stupid things, mostly
19:59 #navit: < mvglasow> :-)
20:00 #navit: <@KaZeR> i did it like an hour ago
20:00 #navit: < mvglasow> so what's the correct way to commit changes now?
20:00 #navit: <@KaZeR> so now we should open a PR and have someone validate
20:00 #navit: <@KaZeR> the goal is also to ensure better cooperation
20:01 #navit: <@KaZeR> i'll send an email to all the devs
20:01 #navit: < mvglasow> All right. So that means even minor things (such as adding a doxygen comment) need to be validated now?
20:02 #navit: <@KaZeR> that's a good question. Right now because of the settings I applied, yes. If it's too much of a hassle we can of course revisit
20:02 #navit: <@KaZeR> what do you think?
20:04 #navit: < mvglasow> well... I’m the last who’d want to discourage people from documenting things
20:05 #navit: < mvglasow> so, as far as just adding comments is concerned, that's a bummer. Then again, preventing people from inadvertently breaking stuff is a valid point.
20:05 #navit: < mvglasow> but at the moment I don't know how we can separate harmless commits from the potentially fatal ones
20:06 #navit: < mvglasow> maybe I should first ask what kind of stupid things we're trying to keep ourselves from doing:
20:07 #navit: < mvglasow> breaking things so badly that navit won't even build any more?
20:07 #navit: <@KaZeR> tjat
20:07 #navit: <@KaZeR> that's exactly what i did this morning
20:07 #navit: < mvglasow> :-)
20:07 #navit: < MarcR> ha - its working :D 
20:08 #navit: <@KaZeR> mvglasow: i pushed a change that was intended to be a simple improvement and broke the android compilation
20:08 #navit: < mvglasow> what about breaking things in a way that will not prevent a successful build but cause errors at runtime?
20:08 #navit: <@KaZeR> hopefully we should catch them using the CI, but more work will be required
20:09 #navit: < mvglasow> yep
20:09 #navit: < Number6> oh, btw, if you move to Circle v2.0, no OSX or iPhone builds are possible - can't put OSX in a docker container
20:09 #navit: <@KaZeR> we used to actually run navit during the linux build and perform some tests, but this part hasn't been implemented in ci v2 yet. but it's coming
20:10 #navit: <@KaZeR> Number6: valid point.. there has to be a solution though as i don't see them ditch their osx/iphone support
20:10 #navit: <@KaZeR> Number6: after wince would you like to work on the iphone build maybe?
20:10 #navit: < mvglasow> my initial suggestion would have been to protect master (which we maintain as the stable branch and which should thus get only merges but no direct commits)
20:11 #navit: < mvglasow> while allowing commits to trunk
20:11 #navit: < mvglasow> then merge trunk into master after CI has passed
20:11 #navit: < MarcR> KaZeR: is it interesting for the wiki - or the car pi compatibilty - to let the people know how they can get the raspi to auto reconnect with a bluetooth device ? 
20:11 #navit: <@KaZeR> mvglasow: we can switch to that if the trunk protection is a problem, absolutely
20:11 #navit: <@KaZeR> MarcR: sounds like a good idea yes
20:12 #navit: < mvglasow> just need to figure out  way to deal with failed CI tests: roll back? give the dev a certain time to fix it? or wait indefinitely?
20:12 #navit: < jkoan> MarcRan KaZeR i will also need that for the tomtom disto, so please document it :D
20:12 #navit: < mvglasow> IMHO protecting master is a good idea—I've accidentally committed to it myself in the past
20:14 #navit: < MarcR> jkoan: ok 
20:14 #navit: < mvglasow> KaZeR what would happen at the moment if I were to create my own branch, push to it, CI passes... can I merge it by myself or would a review be needed?
20:15 #navit: <@KaZeR> mvglasow: on failed ci test, hopefully other devs can jump in and help fix too :)
20:16 #navit: <@KaZeR> mvglasow: ideally someone else should review, as the goal is to increase collaboration. But we probably don't need to strictly enforce that
20:16 #navit: <@KaZeR> mvglasow: this is really up for discussion btw so feel free to speak up your mind :)
20:17 #navit: < jkoan> KaZeR: could you take a look at: https://circleci.com/gh/navit-gps/navit/3409 its failin in order of the android sdk build tools?
20:18 #navit: < mvglasow> KaZeR: for the moment I'd protect master only, and make it a condition that CI passes successfully
20:18 #navit: < mvglasow> then we can refine CI to catch more errors
20:20 #navit: < mvglasow> another thing that comes to mind is architectural changes—but it's always been a convention to discuss major changes first
20:20 #navit: < mvglasow> and I would assume we're giving commit access only to people we trust to play nice in that respect
20:22 #navit: < mvglasow> thus we don't need to put up a technical barrier
20:22 #navit: <@KaZeR> mvglasow: true. one problem is that we don't have an efficient way to discuss these changes. Some prefer irc, some prefer trac, some prefer emails
20:23 #navit: <@KaZeR> MarcR: want to be my guinea pig and test a worldwide preview?
20:23 #navit: <@KaZeR> jkoan: will try to do it soon
20:23 #navit: < jkoan> okay
20:23 #navit: < MarcR> KaZeR: how can I help? :D
20:24 #navit: < jkoan> KaZeR: could you also resent me the finished asw url? 
20:24 #navit: <@KaZeR> MarcR: https://wiki.navit-project.org/index.php/QML2_GUI under 'Prebuilt image'
20:24 #navit: < MarcR> good that I already have more then one sdcard here :D 
20:25 #navit: <@KaZeR> :)
20:25 #navit: <@KaZeR> MarcR: if we disable network boot (or switch to wifi) it should boot in ~5s, so cold boot to navit should be around 8s
20:26 #navit: < MarcR> Ok
20:26 #navit: < mvglasow> KaZeR: if there's code already, then a pull request would be the vehicle of choice. Otherwise...
20:27 #navit: <@KaZeR> mvglasow: good example : should we enable branch protection on trunc? what would be the best way to get everybody's opinion?
20:27 #navit: < mvglasow> since trac is capable of sending email, is there a way to have people subscribe to a particular category of tickets?
20:28 #navit: <@KaZeR> i'm not sure, we would have to check. it could be a good option indeed
20:29 #navit: < mvglasow> UX would be: requester opens a ticket, tags it as "major change proposal", and everybody who's signaled interest in this kind of ticket gets notified
20:29 #navit: < mvglasow> we have keywords for tickets already
20:29 #navit: < mvglasow> the missing step is to automatically add CC recipients when a particular keyword is present
20:30 #navit: < mvglasow> that would cover email
20:30 #navit: < mvglasow> as for irc, does trac have an interface for that?
20:31 #navit: <@KaZeR> i'm not sure. we also have issues with our notifications to irc, overall. circleci and github should push notifications but we aren't receiving them
20:31 #navit: < mvglasow> at a minimum, when a ticket with the "magic" keyword is created (or modified), post a one-line message on IRC, with a link to trac?
20:32 #navit: <@KaZeR> i've disabled the PR requirement on trunk, but i left the disable force push and branch deletion active
20:32 #navit: < mvglasow> would it be an issue if we limited ourselves to trac+email notifications for the moment?
20:32 #navit: <@KaZeR> i don't think that it would
20:32 #navit: < MarcR> KaZeR: flashing sd card now
20:33 #navit: < mvglasow> while I don't check trac frequently (and also don't get on IRC that often), I do check my email regularly
20:33 #navit: <@KaZeR> i still believe that we would benefit from leveraging PR more. Many commits are merged by their authors. Which is fine because we progress, but doesn't foster the collaboration and review we could benefit from too
20:33 #navit: < MarcR> Houston we have a problem - no beers left :-P
20:33 #navit: <@KaZeR> MarcR: emergency! emergency!
20:33 #navit: <@KaZeR> MarcR: navit can guide you to the closest pub or liquor store :)
20:34 #navit: < MarcR> KaZeR: hehe 
20:35 #navit: < mvglasow> KaZeR: if you really want to encourage devs doing things differently...
20:36 #navit: <@KaZeR> mvglasow: actually we can try that workflow (trac+email) to get feedback and a collaborative decision regarding wether we should require PR to commit to trunk :)
20:36 #navit: < mvglasow> ...an option would be to have new commits go to a branch other than trunk (maybe dev or another name of your choice), then lock down trunk and display a message with a link to a wiki page...
20:37 #navit: <@KaZeR> but then we'd have dev->trunk->master, it's a bit overkill no?
20:37 #navit: < MarcR> KaZeR: Pi is not booting to x-server 
20:37 #navit: < mvglasow> ...which tells people to use the new branch for commits, but encourage them to discuss their changes first...
20:37 #navit: <@KaZeR> MarcR: on purpose, not needed :)
20:37 #navit: < mvglasow> I was thinking of dev->master only
20:38 #navit: <@KaZeR> what would we do with trunk in that case?
20:38 #navit: < mvglasow> locking down trunk would just be to break the existing workflow and require people to read the instructions before proceeding
20:38 #navit: <@KaZeR> ha! i see
20:38 #navit: < mvglasow> just an idea, though
20:39 #navit: <@KaZeR> collaboration! i love it! :)
20:40 #navit: < mvglasow> another thing that might help: without any locks in place, how would I ask for a review (other than filing a merge request and waiting for someone else to review it)?
20:40 #navit: < MarcR> KaZeR: mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
20:41 #navit: < MarcR> KaZeR: mmcblk0: error -110 transferring data, sector 94625, nr 56, cmd response 0x900, card status 0x0
20:42 #navit: < MarcR> wait, mmcblk0 is the sd card right? is my sdcard broken now? 
20:42 #navit: <@KaZeR> MarcR: probably not broken. You flashed it and then you got that during boot?
20:43 #navit: < MarcR> correct
20:43 #navit: < MarcR> should i flash it again? 
20:43 #navit: <@KaZeR> mvglasow: i think that there's two ways to ask for review. Open a ticket and discuss the idea (which we rarely do) or code the thing and open a PR (which we do a bit more)
20:44 #navit: <@KaZeR> MarcR: that's odd. try to run 'sync' after flashing to ensure all data are written before unplugging it. What command did you use to flash?
20:44 #navit: <@KaZeR> mvglasow: would you like to see something else happen?
20:45 #navit: < MarcR> I use a windows app to flash, but it has synced the data and said everything is fine, but let me do it again, no prob 
20:45 #navit: < mvglasow> KaZeR: not really, just asking what would be the way to go... if it's via a change request, that's fine
20:46 #navit: < jkoan> mvglasow: if cou create the pull request you cann add specific persons to the review (on the right side)
20:46 #navit: < mvglasow> KaZeR: another thing that comes to mind, though... how many of us are willing to review other people's changes, have time to do so and know their way around that part of the code?
20:47 #navit: < jkoan> adb
20:47 #navit: < jkoan> fuuu :D
20:47 #navit: < jkoan> false window
20:48 #navit: < mvglasow> KaZeR: for myself, availability of time is subject to change; I know my way around some parts of the code but there are others I am less familiar with, and the changes I would review are likel to be parts of the code I'm interested in myself
20:50 #navit: < MarcR> hm looks like i already have a broken micro sd card - these guys are weak like popcorn :P 
20:51 #navit: < mvglasow> KaZeR: maybe we can adopt something like the following: open a change request, leave it open for comments for a certain time (anywhere from 2 days to 2 weeks), if nobody objects, it's OK to merge by yourself
20:51 #navit: < mvglasow> err... I meant pull request
20:52 #navit: < MarcR> KaZeR: aah now we talking 
20:53 #navit: < MarcR> KaZeR: error:navit:graphics_new:Failed to load graphics plugin gtk_drawing_area
20:54 #navit: < mvglasow> jkoan: (hi btw) good to know
20:54 #navit: < jkoan> hi again mvglasow :D
20:54 #navit: < mvglasow> I guess such dev conventions should be described in the wiki
20:54 #navit: < MarcR> KaZeR: error:navit:vehicle_new:invalid source 'gpsd://localhost' : unknown type 'gpsd'
20:55 #navit: < mvglasow> and linked either directly from the start page, or from start page > Development
20:55 #navit: < MarcR> KaZeR: error:navit:navit_init:FATAL: no graphics subsystem available.
20:57 #navit: < Number6> KaZeR: It's gonna be difficult to get the WinCE builds working again... the cross compiler stopped developement in 2009 - a lot of the linux libraries have been updated since then!
21:02 #navit: < jkoan> Number6: you need mingw right? which exactly?
21:05 #navit: < Number6> jkoan: The binaries available for mingw32ce are old, I dunno if even compiling the mingw32ce source will work :-/
21:06 #navit: < jkoan> hm okay
21:08 #navit: < jkoan> what about precompiled toolshane like this one: https://sourceforge.net/projects/cegcc/files/cegcc/0.59.1/
21:13 #navit: < Number6> That's what I've been using :-)
21:13 #navit: < Number6> look at the age of the toolchain - 2009
21:14 #navit: < jkoan> yep, right, but whats the issue?
21:14 #navit: < Number6> cmake is complaining about libraries, which I've jerry rigged by symlinking... that's a nasty hack that, IIRC, caused memory issues on WinCE devices
21:15 #navit: < Number6> I'll take another look at it tomorrow - now is Mr.Robot time :-)
21:15 -!- ColdFyre [~lenny@24-113-108-124.wavecable.com] has quit [Ping timeout: 248 seconds]
21:24 #navit: < MarcR> Guys, i will go to sleep. See you later - have a good sleep
21:24 -!- MarcR [~MarcR@p5B00E033.dip0.t-ipconnect.de] has quit []
21:35 #navit: <@KaZeR> mvglasow: i'm willing to review any and all PR, despite not being the best expert. Hopefully we can get some folks involved. At least when we have PR changes get more visible
21:36 #navit: <@KaZeR> here's a good example : https://github.com/navit-gps/navit/issues/347 in just 2 days 3 members were involved
21:36 -!- ColdFyre [~lenny@24-113-108-124.wavecable.com] has joined #navit
21:36 #navit: <@KaZeR> and as jkoan said you can ask for someone's review, in this case they get an email
21:37 #navit: <@KaZeR> mvglasow: definitely agree on your proposal regarding self merge. I'd suggest 5-7 days 
21:38 #navit: <@KaZeR> Number6: thanks! we could try to build using ubuntu 12.04 or even older, as long as the mirrors are still up maybe it'll help fetch the packages
21:39 #navit: < mvglasow> KaZeR: sounds good to me
21:40 #navit: < mvglasow> KaZeR: btw, trac logon via wiki is still having issues
21:44 #navit: < Number6> KaZeR: Yeah, tomorrow is gonna be on 12.04 and see if that works. I'd rather 14.04, obviously
21:44 #navit: < Number6> *gonna be trying on 12.04
21:45 #navit: < Number6> From my patchy memory back then, 12.04 might work. It *has* been 7 years :-D
21:50 #navit: <@KaZeR> mvglasow: are you using http or https for your user URL ?
21:51 #navit: <@KaZeR> Number6: boy does time fly.
21:51 #navit: < mvglasow> KaZeR: http on the last few attempts, though a few weeks earlier I had the same issue with https
21:52 #navit: < Number6> KaZeR: Back then I lived in a different town, and was fresh out of college. Now I'm married, missing hair, in a different city, and thinking of starting a family :-/
21:52 #navit: < mvglasow> KaZeR: just tried https, same error message
21:52 #navit: <@KaZeR> Number6: pretty much the same story here! :)
21:53 #navit: <@KaZeR> mvglasow: ok let's see. what error message are you getting?
21:53 #navit: <@KaZeR> Number6: although i'm doing ok on the hair front :D
21:53 #navit: < mvglasow> KaZeR: Warning: Invalid argument supplied for foreach() in /var/www/html/extensions/OpenID/SpecialOpenIDServer.body.php on line 686
21:53 #navit: < Number6> KaZeR: Bastard! I'm jealous
21:53 #navit: < mvglasow> from https://wiki.navit-project.org/index.php/Special:OpenIDServer
21:56 #navit: < jkoan> mvglasow: what openid url you use?
21:56 #navit: <@KaZeR> Number6: :D
21:56 #navit: <@KaZeR> mvglasow: let's look at the logs
21:57 #navit: < jkoan> for me this one works: http://wiki.navit-project.org/index.php/User:Jkoan
21:57 #navit: <@KaZeR> mvglasow: can you confirm the url you're using? jkoan might be right
21:58 #navit: < mvglasow> http://wiki.navit-project.org/index.php/user:mvglasow
21:59 #navit: < jkoan> https://wiki.navit-project.org/index.php/User:Mvglasow
21:59 #navit: < jkoan> this would be right
21:59 #navit: < jkoan> probably also without httpS
21:59 #navit: < mvglasow> indeed
22:00 #navit: < mvglasow> I remember the issue with the case of the username, "user" in lowercase used to work
22:00 #navit: < mvglasow> anyway, now I know, thanks
22:00 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
22:01 #navit: < mvglasow> KaZeR: would it be possible (with a reasonable amount of effort) to add the wiki as an OpenID provider so I'd just have to enter my username?
22:02 #navit: < jkoan> for me jkoan is not working, i must use Jkoan
22:02 #navit: <@KaZeR> yes the first letter must be capitalized, that's because of the wiki openid provider
22:02 #navit: < mvglasow> jkoan: yes, that's been around for as long as I can remember
22:03 #navit: <@KaZeR> mvglasow: probably yeah. i can give you access to the setup and even create a test setup just to test if you want
22:03 #navit: < mvglasow> KaZeR: sure, that would be great
22:03 #navit: <@KaZeR> i agree that our current signin process is messy. there's just so much to do :)
22:04 #navit: < mvglasow> I know :-)
22:04 #navit: <@KaZeR> mvglasow: cool i'll do it and be in touch. poke me anytime if i seem to have forgotten :)
22:04 #navit: < mvglasow> OK
22:08 #navit: < mvglasow> jkoan: about the TMC thing, would you mind dropping me a quick email? then I'd send you a writeup of what I've done so far, I find that easier to do via email
22:09 #navit: < mvglasow> thx
22:09 #navit: < jkoan> oh good that you remind me, i always want to do that :X
22:10 #navit: < mvglasow> happy to do that, just prod me if you don't hear from me in a few days :-)
22:45 -!- mvglasow [5cd90b88@gateway/web/freenode/ip.92.217.11.136] has quit [Quit: Page closed]
23:32 -!- Horwitz [~mich1@p200300800E475901022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
23:45 -!- Horwitz [~mich1@p200300800E598C00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:45 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Sat Oct 28 00:00:55 2017