--- Log opened Fri Oct 19 00:00:26 2018
--- Log closed Fri Oct 19 09:03:54 2018
--- Log opened Fri Oct 19 09:04:05 2018
09:04 -NickServ(NickServ@services.)- You are now identified for NavitLogger.
09:04 -!- Irssi: Closing query with nickserv
--- Log closed Fri Oct 19 09:04:10 2018
--- Log opened Fri Oct 19 09:04:14 2018
09:04 -!- NavitLogger [~NavitLogg@176.126.247.29] has joined #navit
09:04 -!- Irssi: #navit: Total of 13 nicks [3 ops, 0 halfops, 4 voices, 6 normal]
09:04 -!- Irssi: Join to #navit was synced in 0 secs
09:04 < NavitLogger> hello
--- Log opened Fri Oct 19 13:55:02 2018
--- Log closed Fri Oct 19 14:00:27 2018
--- Log opened Fri Oct 19 14:36:36 2018
--- Log closed Fri Oct 19 14:38:27 2018
--- Log opened Fri Oct 19 14:38:29 2018
14:38 -!- Irssi: Log file /domains/irclogs.navit.ie/public_html/irclogs/#navit-%Y-%m-%d.log opened
14:38 #navit: < NavitLogger> test2
15:00 #navit: <@KaZeR> roger roger
15:09 #navit: < genesis> https://www.tomtom.com/fr_fr/opensource/ which file is tomtom sdk for opentom ?
15:11 #navit: <@KaZeR> genesis: jkoan: might be worth setting up a xslt to build that config file easily, and have it versioned?
15:12 #navit: < genesis> yes and distributed in the package ...
15:13 #navit: < genesis> since it still blocked for cmake 3, i've a look at tomtom port
15:14 #navit: <@KaZeR> > yes and distributed in the package ... 
15:14 #navit: <@KaZeR> i am starting to wonder if we shouldn't build packages for specific devices
15:14 #navit: < genesis> but i donno which files i've to pick up.
15:15 #navit: < genesis> it's the main interest using openembedded over buildroot
15:16 #navit: < genesis> it's easier to inherit class and provide / build only what differ, for example only screen size on XL vs non-XL version of tomtom
15:16 #navit: < genesis> or gps driver and so
15:16 #navit: < genesis> we could share same ipk paquet for map and so.
15:17 #navit: <@KaZeR> but how do you install an ipk on tomtom? 
15:17 #navit: < genesis> ipk is a stripped deb kind of pkg
15:18 #navit: < genesis> so you've to have ipkg cross compiled on it and some kind of ui to update
15:18 #navit: < genesis> but it's the interest of openembedded, we can choose the type of pakage, if you want tar.gz or both ...
15:19 #navit: < genesis> so we can still use ftp-like update like now.
15:19 #navit: < genesis> i need the write toolchain and i find no documentation which one
15:20 #navit: < genesis> "It can be downloaded from TomTom's website: http://www.tomtom.com/page.php?Page=gpl. This file needs to be unpacked into /usr/local/cross. "
15:28 #navit: < genesis> https://www.tomtom.com/fr_fr/opensource/go-version-54/ i guess.
15:30 #navit: < genesis> bbl
15:34 #navit: < genesis> btw we'll have to write tomtom instruction for user, and since they have to keep and edit their configuration
15:34 #navit: < genesis> a manual process is needed, but we have to provide a functional default xml.
15:43 #navit: <@KaZeR> yeah i've used ipk in the past, during my openmoko days. My question was more about how do you plan to deploy the ipk/tar.gz on the tomtom device
16:51 -!- aerostitch [~aerostitc@c-24-23-228-135.hsd1.ca.comcast.net] has joined #navit
16:51 -!- mode/#navit [+v aerostitch] by ChanServ
17:43 #navit: < genesis> i don't see any difficulty there KaZeR 
17:44 #navit: < genesis> you can ftp them and run opkg locally or so, don't bother since i don't plan to push on openembedded alone
17:44 #navit: <@KaZeR> i'm not saying that there is one, just that i don't know how you would do that :)
17:45 #navit: <@KaZeR> how would you run opkg on the tomtom device? (i'm not familiar with the tomtom devices)
17:45 #navit: < genesis> i'd like to clean Toolchain/ for now
17:46 #navit: < genesis> you could use remote command with opentom i think
17:46 #navit: < genesis> anyway , you put ipk in a directory, and script a button in the tomtom menu that runs them locally
17:46 #navit: < genesis> plenty easy solution.
17:47 #navit: < genesis> perharps you can run a host opkg version against the tomtom mounted device
17:47 #navit: < genesis> (act like a tomtom HOME apps)
17:49 #navit: <+aerostitch> Damn I love this CVE: https://nvd.nist.gov/vuln/detail/CVE-2018-10933
17:49 #navit: <+aerostitch> So basically you send a `SSH2_MSG_USERAUTH_SUCCESS` packet to the ssh server instead of a `SSH2_MSG_USERAUTH_REQUEST` and you're in!
17:49 #navit: <+aerostitch> lol
17:50 #navit: < genesis> KaZeR : the main difficulty is to clean navit build process
17:51 #navit: <@KaZeR> noice
17:53 #navit: < genesis> aerostitch : woot :']
17:58 #navit: <+aerostitch> lol
17:58 #navit: <+aerostitch> yeah it's a very funny one
17:58 #navit: <+aerostitch> you remember the yes cards back in the days?
17:58 #navit: <+aerostitch> :D
17:59 #navit: <+aerostitch> Same principle
17:59 #navit: <+aerostitch> or maybe easier
17:59 #navit: < genesis> yes :) 
18:05 #navit: < genesis> https://www.tomtom.com/fr_fr/opensource/go-version-54/ great that tomtom provide diff , easier to make clean stuff with that
18:05 #navit: < genesis> even the canadian cross compile and have a good toolchain.
18:06 #navit: < genesis> that what i'd do first.
19:38 #navit: <+ilovekiruna> hi @all
19:38 #navit: <+ilovekiruna> KaZeR: so about sailfish we proceed next with a forum entry?
21:26 #navit: <@KaZeR> you mean for the circleci issue?
21:29 #navit: <+ilovekiruna> yes
21:32 #navit: <@KaZeR> yeah, that's our only option i think. i'm not aware of a chat
21:52 -!- Number6 [~number6@zoidberg.geoghegan.me] has quit [Quit: leaving]
21:56 #navit: <+ilovekiruna> to track our entry in the circleci forums: https://discuss.circleci.com/t/non-reproducable-build-results/25864
21:57 #navit: <@KaZeR> great thanks
22:10 #navit: <+ilovekiruna> i check now about artifacts
22:10 #navit: <+ilovekiruna> KaZeR: do you have amazon S3 setting sfor me? https://docs.travis-ci.com/user/uploading-artifacts/
22:27 -!- Number6 [~number6@zoidberg.geoghegan.me] has joined #navit
22:27 -!- mode/#navit [+o Number6] by ChanServ
22:33 #navit: <@KaZeR> that's an option, but i'm going to have to pay for it :)
22:34 #navit: <+ilovekiruna> dont think uploading to github relases would be an option, or what do you think?
22:34 #navit: <@KaZeR> not really, as it would require a release for each build
22:34 #navit: <@KaZeR> how big are the resulting files?
22:40 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
22:45 #navit: <+ilovekiruna> will rebuild now to check
22:46 #navit: <+ilovekiruna> what about tagging the version with the git-hash?
22:47 #navit: <@KaZeR> version of the sailfish packages?
22:54 #navit: <+ilovekiruna> 6 MB each
22:55 #navit: <+ilovekiruna> yes, tagging these "nightly" versions
23:20 #navit: <@KaZeR> oh, for 6MB we could push them to github maybe
23:20 #navit: <@KaZeR> as a rule of thumb, using a semver release when available and then defaulting to the git sha1 is perfect IMO
23:32 #navit: <+ilovekiruna> ok, will then have a try tomorrow
--- Log closed Sat Oct 20 00:00:28 2018