--- Log opened Sun Oct 08 00:00:19 2017
00:02 #navit: <@KaZeR> ilovekiruna: progress! https://imgur.com/a/liQic 
00:02 #navit: < ilovekiruna> KaZeR: so i understand it generally right, that in theory the tests would run, if there were any valid tests, right?
00:04 #navit: <@KaZeR> yeah i found an error in the logs, trying to isolate it. The UI doesn't make it easy because it's in a stupid hover window
00:05 #navit: < ilovekiruna> i know that test2 is probably totally flawed
00:05 #navit: < ilovekiruna> i would ignore that
00:05 #navit: < ilovekiruna> I mean test_second
00:06 #navit: < ilovekiruna> both are appium sample codes
00:06 #navit: < ilovekiruna> that i would adjust then more to our needs
00:06 #navit: <@KaZeR> ok. but you definitely fixed the packaging
00:06 #navit: < ilovekiruna> actually the issue was simple
00:06 #navit: <@KaZeR> ilovekiruna: i'll look into giving you direct access to that console, it will make it easier
00:06 #navit: < ilovekiruna> thanks KaZeR
00:06 #navit: < ilovekiruna> py.test expects a certain filenaming convention
00:07 #navit: < ilovekiruna> i called it test1.py
00:07 #navit: < ilovekiruna> but it needs to follow the pattern test_something.py
00:07 -!- Horwitz [~mich1@p200300800E086700022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:07 -!- mode/#navit [+o Horwitz] by ChanServ
00:08 #navit: <@KaZeR> ha, good to know
00:38 #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:38 #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:38 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
00:39 #navit: < sleske> KaZeR: As I wrote above, I don't think it makes sense to keep both issue systems open in parallel.
00:39 #navit: < sleske> But ultimately it's not my decision.
00:40 #navit: < sleske> And about finding trac: We could include it into our README :-).
00:42 #navit: <@KaZeR> sleske: "But ultimately it's not my decision. " this is actually something i'd like to address too, but let's get back to this in a moment
00:44 #navit: <@KaZeR> just so that i get the facts right : do you feel strongly about keeping trac or is your issue really only about having two bug trackers right now? 
00:46 #navit: < sleske> I don't care that much about trac vs. GitHub - I think both work fine.
00:46 #navit: < sleske> It's just that I think if we move to GH, we should really migrate old issues from trac - and that will be a lot of work.
00:48 #navit: <@KaZeR> that's a fair point. jkoan offered earlier to have a look at it. We could create a test repository to see how painful this would be
00:48 #navit: < sleske> Plus referencing issues from commits will get really messy, because we used the "#123" syntax for trac issues in the past - these will suddenly seem to reference non-existend GH issues.
00:48 #navit: < sleske> I mean in commit msges.
00:48 #navit: <@KaZeR> yes, and for this one i don't think that there would be a fix
00:49 #navit: < sleske> And using trac does give us more freedom to do special stuff with tickets - with GH we must live with what GH offers (e.g. no deleting of issues).
00:49 #navit: < sleske> So in balance, I don't think GH issues has enough advantages to switch.
00:51 #navit: < sleske> Of course, I may be overlooking some advantage of GH.
00:51 #navit: <@KaZeR> that's a fair point. On the other hand, it's quite probable that many folks who would be likely to contribute would already have a GH account
00:51 #navit: <@KaZeR> my end goal really is to try to lower the bar for people to contribute, to boost the community
00:52 #navit: < sleske> That's a good idea. I'm not sure whether the lack of GH issues is the problem though (though we should probably link to trac from our README...).
00:54 #navit: <@KaZeR> yes i'll add a link to trac in the README that's a good idea.
00:55 #navit: <@KaZeR> i'm sure that not having GH issues isn't our biggest factor slowing down our community, but i am wondering if it isn't at least contributing a bit
01:00 #navit: < sleske> Yes, it might. On the other hand, having two ticket systems in parallel would probably slow us down a lot.
01:01 #navit: < sleske> And migrating trac to GH, while possible, is not easy, as explained above.
01:01 #navit: < sleske> I hate to be a spoilsport, but I don't see an easy way to move to GH issues.
01:04 #navit: <@KaZeR> sleske: you're not being a spoilsport. As I said in my email, your opinion is really valued
01:06 #navit: <@KaZeR> so we currently have 304 open tickets on trac. i am guesstimating that half of them are not reproducable
01:07 #navit: <@KaZeR> i am also betting that for those that are still valid, there's a good chunk of the users that we cannot reach because the email address is invalid or the openid provider doesn't exist anymore
01:07 #navit: <@KaZeR> this is part of the problem i think. the major factor of course being that we have always been quite bad at managing our tickets
01:08 #navit: <@KaZeR> this is why many projects today automatically close tickets after a given period of time
01:12 #navit: < sleske> Yes, that is a general problem with tickets - you need to follow up. But that's independent of where we store them :-).
01:13 #navit: < sleske> And apart from the unreproducible tickets, we also have many that have seen a lot of work, with useful comments.
01:14 #navit: <@KaZeR> absolutely and we need to keep that
01:49 #navit: < sleske> Yes.
01:50 #navit: < sleske> So, what about putting a link to trac into the README, and seeing how it goes? We could even explain why we don't use GH issues (yet). Then if we get feedback that it would be useful, we can consider a migration.
01:50 #navit: < sleske> In the meantime we stick with trac.
01:50 #navit: < sleske> Well, gotta sleep now. Good night!
01:50 -!- sleske [~sleske@p4FD45260.dip0.t-ipconnect.de] has quit [Quit: leaving]
02:49 -!- noradtux [~noradtux@2a02:2028:73a:1901:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 258 seconds]
02:54 -!- noradtux [~noradtux@2a02:2028:63a:dc01:ec4:7aff:fe33:3dc1] has joined #navit
04:12 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
04:12 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Remote host closed the connection]
04:13 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
15:32 #navit: < ilovekiruna> hi everyone
15:35 #navit: < ilovekiruna> KaZeR: which devices did my test run on?
15:54 #navit: < jkoan> hi ilovekiruna
16:00 #navit: < ilovekiruna> hi jkoan
16:01 #navit: < ilovekiruna> the current zip file doesnt make any useful test, but at least ran when KaZeR uploaded it
16:01 #navit: < ilovekiruna> hope to get sth useful the coming days
16:03 #navit: < jkoan> nice :)
16:03 #navit: < jkoan> i worked on the traffic plugin integration :)
16:04 #navit: < ilovekiruna> how is it going?
16:04 #navit: < jkoan> i slowly understand how the plugin system is working
16:05 #navit: < ilovekiruna> great
16:05 #navit: < jkoan> do you think its okay to use cpp insted of raw c?
16:06 #navit: < ilovekiruna> for me it would, but I am not sure about what the others think
16:07 #navit: < ilovekiruna> especially as navit is based i think on glib which is c based
16:07 #navit: < ilovekiruna> so it could be tricky
16:08 #navit: < jkoan> but the qt5/qml thing is also cpp based ;)
16:08 #navit: < ilovekiruna> hmm, also true
16:09 #navit: < ilovekiruna> so far i thought most navit code is in C
16:09 #navit: < ilovekiruna> not C++
16:10 #navit: < ilovekiruna> but honestly i still dont know the code base so well
16:10 #navit: < jkoan> i dont know the base verry well also
16:10 #navit: < ilovekiruna> i guess we have to wait for KaZeR to answer
16:11 #navit: < jkoan> yep
16:11 #navit: < ilovekiruna> can you give me a bit more details about how far you got with the traffic plugin?
16:17 #navit: < jkoan> 1% so far. I am about to write the plugin register for traffic plugins (so we can write new traffic plugin eg. web services). Then i will write the plugin for rds-tmc in sync with the register
16:20 #navit: < ilovekiruna> so i guess the issue of tmc point still persists
16:20 #navit: < ilovekiruna> right?
16:21 #navit: < jkoan> yes
16:22 #navit: < ilovekiruna> then what will be our major data source?
16:23 #navit: < ilovekiruna> or we just prepare for one to appear?
16:43 #navit: < jkoan> half and half. i think we will get get tmc working, but yes, it would be nice if we find something better
16:46 #navit: < jkoan> and because of this i want to write it as plugins ;)
16:46 #navit: < ilovekiruna> jkoan: I dont want to discourage you, just understand the status
16:46 #navit: < jkoan> yes i know :) everything is fine ^^ i was only afk :X
18:50 #navit: < ilovekiruna> jkoan: do you know a permanent link from where I could download the latest build of navit android?
19:10 #navit: < ilovekiruna> does any sort of nightlies exist?
19:17 -!- mvglasow [5e87a62a@gateway/web/freenode/ip.94.135.166.42] has joined #navit
19:54 #navit: < jkoan> Right now there is no permanent link, but with some changes in the build I can probably give you one. Why do you need it?
19:55 -!- mvglasow [5e87a62a@gateway/web/freenode/ip.94.135.166.42] has quit [Quit: Page closed]
19:56 #navit: <@KaZeR> hi there
19:57 #navit: <@KaZeR> ilovekiruna: do you have a gpg key? i have credentials for you to access the test farm
19:57 #navit: < ilovekiruna> hi KaZeR
19:57 #navit: < ilovekiruna> jkoan: I wanted to download the latest apk file when making a new test on the test farm
19:57 #navit: < ilovekiruna> for my own convinience
19:58 #navit: < ilovekiruna> I think i should have one, just need to find it again
19:58 #navit: < ilovekiruna> KaZeR: have you seen my question about which devices the zip file ran on?
19:59 #navit: <@KaZeR> yeah saw the question, that's why giving you access to the device farm would be easier :)
20:00 #navit: < ilovekiruna> I c :)
20:02 #navit: <@KaZeR> ilovekiruna: we should export the apk automatically after builds, but until then if you look at the last successful job for android-arm here : https://circleci.com/gh/navit-gps/navit
20:03 #navit: < ilovekiruna> was looking at it
20:03 #navit: < ilovekiruna> but not sure if i can access the artifacts
20:03 #navit: <@KaZeR> and go to the artifact tab, you can find it under root/project/android-arm/navit/android/bin/
20:03 #navit: < ilovekiruna> for my own branch was ok, but not for the general one
20:03 #navit: <@KaZeR> artifacts should be public
20:03 #navit: <@KaZeR> but we should upload them somewhere easier to find anyway
20:03 #navit: < ilovekiruna> ah, now it is
20:03 #navit: < ilovekiruna> thx
20:04 #navit: <@KaZeR> did you see my question for your gpg key?
20:04 #navit: < ilovekiruna> KaZeR: yes, I saw it
20:04 #navit: < ilovekiruna> checking it out now
20:04 #navit: <@KaZeR> ok
20:04 #navit: < ilovekiruna> will give you in some minutes
20:04 #navit: <@KaZeR> perfecct
20:06 #navit: < ilovekiruna> KaZeR: Do I see it wrong that no apk file is created for build_android_arm? https://circleci.com/gh/navit-gps/navit/2804#artifacts/containers/0
20:07 #navit: <@KaZeR> how about this one? https://2804-30791823-gh.circle-artifacts.com/0/root/project/android-arm/navit/android/bin/navit-a3435121850201dc163c5f55153ea4bc9d91e179-arm-debug.apk 
20:07 #navit: <@KaZeR> it's currently a bit hidden in a subfolder :)
20:07 #navit: < ilovekiruna> ah, I c
20:07 #navit: < ilovekiruna> am blind :-o
20:07 #navit: <@KaZeR> haha
20:12 #navit: <@KaZeR> actually i can pm the password to you, you'll have to change it after the first login
20:13 #navit: < jkoan> There is also a way (at least for v1) to have a fully static link. This only need to know where the artifact is. And this is possible to set
20:16 #navit: <@KaZeR> yeah we just need to push the artifact url somewhere after the build using the notification api
20:17 #navit: < jkoan> Not really. There is also a really static url with circleci itself
20:21 #navit: <@KaZeR> the circleci url will always contain variable like buildid, account id and the commit sha1 no?
20:22 #navit: < jkoan> No
20:23 #navit: < jkoan> Like this one :
20:23 #navit: < jkoan> ://circleci.com/api/v1/project/navit-gps/NavitTom/latest/artifacts/0/home/ubuntu/NavitTom/target/opentom.tar.gz?branch=master&filter=successful
20:23 #navit: < jkoan> Of course https...
20:23 #navit: <@KaZeR> ha yeah via the api
20:23 #navit: < ilovekiruna> jkoan: This was exactly what i asked for
20:23 #navit: < ilovekiruna> sth like this
20:25 #navit: < jkoan> Ilovekiruna but we need to change that we don't store a random name, we need to change this to navit.apk and to a directory we know (the easiest would probably be only the root
20:25 #navit: < jkoan> )
20:28 -!- Horwitz [~mich1@p200300800E086700022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Quit: leaving]
20:30 #navit: <@KaZeR> jkoan: https://github.com/pgrandin/gentoo-pkg-builder/blob/master/circle.yml#L51 is how i
20:30 #navit: <@KaZeR> i'm doing it for another project
20:31 #navit: <@KaZeR> and the webservice is a very simple python script that stores the url of the latest build
20:31 #navit: < ilovekiruna> KazeR: are you also building a navit package for gentoo??
20:31 #navit: <@KaZeR> no, i always compile from source for Gentoo
20:32 #navit: <@KaZeR> jkoan: we could use a similar hook to store the artifacts url and have something like http://download.navit-project.org/navit/ 
20:32 #navit: < ilovekiruna> KaZeR: from source without an ebuild involved?
20:34 #navit: <@KaZeR> ilovekiruna: currently yes
20:36 #navit: <@KaZeR> ilovekiruna: please let me know once you'll have tested the device farm access. not urgent, just to be sure it's working as expected
20:40 -!- Horwitz [~mich1@p200300800E086700022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
20:40 -!- mode/#navit [+o Horwitz] by ChanServ
20:41 #navit: < ilovekiruna> KaZeR: Sure, will do that
21:22 #navit: < ilovekiruna> ok KaZeR: seems like i am in now
21:22 #navit: < ilovekiruna> with my new password
21:29 #navit: < ilovekiruna> which of the two projects on the device farm did u use last?
21:29 #navit: < ilovekiruna> ilovekiruna or Navit?
21:41 #navit: < ilovekiruna> jkoan: i just saw a package qtspeech on gentoo, could that be used also in sailfish?
22:35 #navit: <@KaZeR> ilovekiruna: last project i used was ilovekiruna. "navit" wast just a test. you can delete everything, create a new project, etc
23:37 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
23:53 -!- Horwitz [~mich1@p200300800E086700022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
23:55 #navit: <@KaZeR> just got a firetv for something else. Thought it would be fun to test navit on it
23:56 #navit: <@KaZeR> it works, although it's not super practical because the remote has really few buttons, and the icons in the menu are missing
23:56 #navit: <@KaZeR> but it works :)
--- Log closed Mon Oct 09 00:00:21 2017