--- Log opened Mon Jan 14 00:00:42 2019
00:34 -!- mvglasow [~mvglasow@dslb-088-065-131-076.088.065.pools.vodafone-ip.de] has quit [Quit: Leaving]
00:56 -!- odo2063 [~odo2063@unaffiliated/odo2063] has quit [Ping timeout: 260 seconds]
03:08 -!- youte [~youte@95-210-222-17.ip.skylogicnet.com] has quit [Read error: Connection reset by peer]
05:37 -!- youte [~youte@95-210-222-17.ip.skylogicnet.com] has joined #navit
05:38 -!- mode/#navit [+v youte] by ChanServ
05:59 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
05:59 -!- mode/#navit [+v xenos1984] by ChanServ
06:32 #navit: <+Navit> <7475da40> Sex Dating > http://discord.amazingsexdating.com
07:31 -!- naggety [~naggety@27.red-95-125-56.dynamicip.rima-tde.net] has joined #navit
08:13 -!- youte [~youte@95-210-222-17.ip.skylogicnet.com] has quit []
13:49 -!- odo2063 [~odo2063@unaffiliated/odo2063] has joined #navit
13:49 #navit: < odo2063> hi!
13:50 #navit: < odo2063> i'm back from my first testdrive and i have an issue...the logging didb't work
14:38 #navit: < odo2063> and navit doesn't talk at all to me
14:55 #navit: <+Navit> <KaZeR> Hi odo2063
14:55 #navit: <+Navit> <KaZeR> I can help you in about 45 mins
14:59 #navit: < odo2063> KaZeR,  i'll be back later need to go now
15:03 -!- odo2063 [~odo2063@unaffiliated/odo2063] has quit [Ping timeout: 252 seconds]
15:29 -!- naggety [~naggety@27.red-95-125-56.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:56 -!- odo2063 [~odo2063@unaffiliated/odo2063] has joined #navit
15:56 #navit: < odo2063> KaZeR,  i'm back
15:58 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
16:32 -!- tryagain [~quassel@217.107.194.17] has joined #navit
16:32 -!- mode/#navit [+o tryagain] by ChanServ
16:44 #navit: <@KaZeR> odo2063: me too
16:44 #navit: <@KaZeR> let's look at your logging issue 
16:57 #navit: < odo2063> https://pastebin.com/UDjdGE9k
16:58 #navit: < odo2063> this may navit.xml. it runs on winCE 6.0 core
17:03 #navit: <@KaZeR> your config looks good. Do you get an empty log file, or no file at all?
17:03 #navit: < odo2063> https://pastebin.com/ZSF1a9ZE
17:03 #navit: < odo2063> nothing that indicates that is not tracking
17:04 #navit: < odo2063> i guess
17:05 #navit: < odo2063> where does it try to save the file? in navit directory or on c:\ (or what it is called in wince)
17:05 #navit: <@KaZeR> for the vehicle log, i am wondering if the file isn't just someplace else. I have a wince device in a box somewhere i can try
17:06 #navit: <@KaZeR> also i'm unsure if the powershell thing isn't just for windows, not wince. did you get that from the wiki?
17:07 #navit: < odo2063> this is mostly what comes with the zip plus https://wiki.navit-project.org/index.php/OSD_Layouts#Layout_for_Sony_nav-u92T
17:11 #navit: < odo2063> maybe justb need to tell him he should save on SD-card?
17:13 #navit: <@KaZeR> you can tweak that with the "data="track_%Y%m%d-%%i.gpx" " field. By default it uses NAVIT_SHAREDIR iirc
17:16 #navit: < odo2063> ok...i'll try that...
17:16 #navit: < odo2063> what can we do about the not talking?
17:40 -!- xenos1984 [~xenos1984@61e7-1cab-e433-01f6-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit
17:40 -!- mode/#navit [+v xenos1984] by ChanServ
18:01 -!- mvglasow [~mvglasow@dslb-088-065-131-076.088.065.pools.vodafone-ip.de] has joined #navit
18:02 -!- youte [~youte@95-210-222-17.ip.skylogicnet.com] has joined #navit
18:02 -!- mode/#navit [+v youte] by ChanServ
18:41 #navit: <@tryagain> mvglasow on ubuntu 16.04, the asn1 package is named python3-pyasn1-modules, I also had to install python3-yaml
18:42 #navit: <@tryagain> s/the asn1/the asn1 package required by fdroid/
18:43 #navit: < mvglasow> thanks, what about the other python packages? do I switch everything to python3?
18:44 #navit: <@tryagain> it looks like I was able to start local build process after adding these two. If you got an error, it worths to try the others :)
18:44 #navit: <@tryagain> my command was ../fdroidserver/fdroid build -v -l org.navitproject.navit
18:44 #navit: < mvglasow> do I have to add them on top of their python-* counterparts or instead of them?
18:45 #navit: <@tryagain> I guess instead
18:45 #navit: < mvglasow> thanks, I'll give it a shot
19:01 #navit: < odo2063> ontop python2 and python3 are 2 different systems
19:03 #navit: < mvglasow> yea, currently I seem to be running a mix of both
19:04 #navit: < mvglasow> had to lift python-requests to version 3 as well
19:04 #navit: < mvglasow> the job is still running, then we will see
19:07 #navit: < mvglasow> another error, see here: https://gitlab.com/mvglasow/Navit-fdroid/-/jobs/145627831
19:08 #navit: < mvglasow> do I need any of the python2 stuff anyway? or can I upgrade everything to python3? That's what I'll try now...
19:19 #navit: <@tryagain> mvglasow Looks like navit.navitproject.navit.txt issue. Maybe at first try to build an old version of navit? Just to make sure our build setup is ready.
19:25 #navit: < mvglasow> the file does not seem to contain any characters above 0x7F, so I doubt that's the issue
19:25 #navit: < mvglasow> any idea what 'position 411' refers to? the 411th byte (dec or hex) in the txt file? though either dec or hex, that is a Latin lowercase letter
19:26 #navit: < odo2063> mvglasow,  some systemstuff needs python2
19:27 #navit: < mvglasow> and 0xe2 (the illegible byte) definitely does not appear anywhere in the file
19:31 #navit: <@tryagain> mvglasow your file copied over my current fdroid-data doesn't produce same error for me
19:32 #navit: < mvglasow> strange, what yml file are you using? mine or a different one?
19:32 #navit: <@tryagain> maybe it worths to run '../fdroidserver/fdroid readmeta' and '../fdroidserver/fdroid lint'
19:33 #navit: <@tryagain> I run it on my local computer, not on CI server
19:33 #navit: < mvglasow> ok, added those to the yml script
19:33 #navit: < mvglasow> if that doesn't help, I'll try building a different app
19:35 #navit: <@tryagain> have to go now.
19:35 #navit: < mvglasow> ok, thanks for now
19:36 #navit: < mvglasow> will keep you posted
19:45 #navit: < mvglasow> fdroid readmeta reports the same error, same byte, but for a different position:
19:45 #navit: < mvglasow> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 395: ordinal not in range(128)
19:45 #navit: < mvglasow> seems to be a different file, but it doesn't say which
19:50 #navit: < odo2063> seems you are working with strings and not with bytes
19:53 #navit: < mvglasow> when I try to build com.vonglasow.michael.satstat, fdroid build throws the same error
19:54 #navit: < mvglasow> byte 0xe2 in position 411
19:54 #navit: < mvglasow> so it' almost definitely not the build recipe file
20:09 #navit: < odo2063> seems to
20:13 #navit: <+Navit> <jkoan> could somewan help me by expülaining something in item.h
20:14 #navit: <+Navit> <jkoan> why we have so many functions which are defined by the preprocessor define instead of a real function?
20:32 #navit: < mvglasow> odo2063 tryagain looks like it works now, checked out tag 1.9.0 if fdroidserver instead of latest master and it works
20:33 #navit: < mvglasow> build is still running but I'm already much further that I ever got before
20:36 #navit: < mvglasow> jkoan are you referring to lines 50-66?
20:38 #navit: < mvglasow> could be to save a few processor cycles
20:39 #navit: < mvglasow> define causes the preprocessor to replace every occurrence of the defined expression with the "function body"
20:39 #navit: < mvglasow> so in terms of runtime, it is the equivalent of writing the expression out in full each time
20:39 #navit: <+Navit> <jkoan> hm okay...
20:40 #navit: < mvglasow> a function would involve adding the call and arguments to the stack, then a jump (disrupting the pipeline), execution of the expression, then another jump to return and popping the function call from the stack
20:41 #navit: < mvglasow> unless the compiler manages to optimize that out, it means a few extra clock cycles with no added benefit
20:41 #navit: < mvglasow> if you're iterating over a bunch of items and use these expressions a few hundred or thousand times in a row, that makes a noticeable difference
20:42 #navit: < mvglasow> presumably - I didn't write this but I could imagine that was the reason behind it
20:43 #navit:  * tryagain agrees
20:44 #navit: <@tryagain> the build seem to has failed now, but reports success
20:45 #navit: <+Navit> <jkoan> i would be very happy to replace it... and also i would like to replace item_def.h with something more structured, and meaningfull. Because, like its now, we dont have a standart to create a map, avery map is only vailid as long the item_def stays the same. In my oppinion we shuld ship a "item_def" or id_to_type table in the binfile itself and process it on initial load of the file. Probably a more indipendent
20:45 #navit: <+Navit> format as binfile2?
20:45 #navit: < mvglasow> tryagain ah, yeah, still an issue with the build recipe
20:46 #navit: < mvglasow> need to investigate and make sure I checked out the correct version
20:46 #navit: <@tryagain> there are earler failures while building ACRA with maven
20:46 #navit: < mvglasow> currently we don't have a version which would build this way
20:47 #navit: < mvglasow> the last released version doesn't have the build script yet, so that part is bound to fail
20:47 #navit: < mvglasow> need to look into the acra stuff as well
20:48 #navit: < mvglasow> on the long run we should not need any special stuff for F-Droid
20:49 #navit: < mvglasow> acra is no longer included as a jar, hence the special handling is no longer needed
20:49 #navit: < mvglasow> if I get that correctly, we've ditched it
20:50 #navit: < mvglasow> or it's still somewhere in the toolchain, but that would look like it gets built from source
20:50 #navit: < mvglasow> so it should be fine with F-Droid
20:53 #navit: < mvglasow> I removed the srclibs line and am re-running the job now
20:53 #navit: < mvglasow> tryagain do you know for certain what version of the Android SDK tools the F-Droid build server uses?
20:54 #navit: < mvglasow> specifically if the sdkmanager command will work to add/remove components?
20:55 #navit: <@tryagain> no, but IIRC I was said three years ago something like "we have all versions of SDK available".
20:56 #navit: < mvglasow> it's more about the installer for new SDK components than the components themselves
20:56 #navit: < mvglasow> but I'll see if that works with the script as is
20:56 #navit: < mvglasow> else we'll have to dig deeper
21:01 #navit: <@tryagain> there's #fdroid channel on the freenode, the person I was talking to is mvdan, who was very kind to answer all my questions.
21:06 #navit: <@tryagain> jkoan anyway new items would require config change to have them visible, routable etc. For now, we have maps "almost" backward compatible. Old binary doesn't see new POIs, it doesn't route through new street types. But in all other senses it's compatible.
21:08 #navit: <@tryagain> If we attempt to make binfile update automatically implement all new navit features, we could finish including navit binary and libraries into map file :)
21:12 #navit: < mvglasow> +1, each of the item types translates to a numeric identifier
21:12 #navit: < mvglasow> by convention, these never change once assigned
21:13 #navit: < mvglasow> thus maps are guaranteed to remain legible
21:13 #navit: < mvglasow> and new maps will work with old versions, except that items with "new" types will not work in the old version
21:14 #navit: <+jkoan> But at least it is quite instabile in the way we "wrote it down" because not every id is written. Instead (as far I see) we write the first id with item2 und count them up with item?
21:15 #navit: < mvglasow> need to add, some map types (txtfile) and styles also use item type strings
21:15 #navit: < mvglasow> yes, IIRC item2 means an item with that particular identifier
21:16 #navit: < mvglasow> item means an item with an identifier 1 higher than the previous item
21:20 #navit: <+jkoan> So it would be possible to rewrite it with over entry explicit?
21:21 #navit: <+jkoan> But anyway, thx for the explanation
21:24 #navit: < odo2063> can i wish for something? Qmapshack compatibility?
21:33 #navit: <@tryagain> mvglasow you seem to attempt build of this version https://github.com/navit-gps/navit/commit/609805e24c80a5e950adbfd20b5f1344708d4eb9
21:33 #navit: <@tryagain> it's half year old and doesnt include the script you attempt to run
21:33 #navit: < mvglasow> fixed that already, now I am trying latest master
22:29 #navit: < mvglasow> tryagain in the CI console output I see the following line:
22:29 #navit: < mvglasow> WARNING: org.navitproject.navit:v0.5.3-442-gbca21e7 runs this on the buildserver with sudo:
22:29 #navit: < mvglasow> followed by the commands I specified in my build recipe to run as sudo
22:30 #navit: < mvglasow> does that mean the commands are getting executed or not?
22:30 #navit: <@tryagain> hm, i guess, they get executed, as it's just warning :)
22:31 #navit: < mvglasow> the thing is, one of these commands is supposed to install gradle, and later the script complains about gradle missing
22:32 #navit: < mvglasow> though I'm not sure if the build server should have gradle available by default, even if the build recipe does not specify gradle=*
22:33 #navit: <@tryagain> https://gitlab.com/fdroid/fdroidserver/merge_requests/297
22:34 #navit: <@tryagain> looks indeed like just a warning
22:35 #navit: <@tryagain> but may have some consequences if running on actual build server
22:36 #navit: <@tryagain> maybe better move install gradle command to .yml?
22:37 #navit: < mvglasow> yep, that's what I'm trying right now
22:37 -!- xenos1984 [~xenos1984@61e7-1cab-e433-01f6-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
22:37 #navit: < mvglasow> and hope the build server has gradle available by default, even when no gradle*= entry is resent in the build recipe
22:43 #navit: < mvglasow> all right, now at least Gradle runs
22:44 #navit: < mvglasow> but barfs over google() appearing in build.gradle
22:44 #navit: < mvglasow> think I'll look at that tomorrow
22:44 #navit: < mvglasow> thanks for your support
22:44 #navit: < mvglasow> bye
22:47 #navit: <@tryagain> see you
23:05 -!- mvglasow [~mvglasow@dslb-088-065-131-076.088.065.pools.vodafone-ip.de] has quit [Quit: Leaving]
23:05 #navit: <@tryagain> at the  https://gitlab.com/fdroid/fdroidserver/blob/master/.gitlab-ci.yml there is a reference to registry.gitlab.com/fdroid/ci-images-server:latest which it used in CI testig of f-droid itself. 
23:07 #navit: <@tryagain> We could adopt that image or ask at #fdroid if they can share image they use on their production, so we can reuse it for our CI.
23:08 -!- tryagain [~quassel@217.107.194.17] has quit [Remote host closed the connection]
--- Log closed Tue Jan 15 00:00:44 2019