[01:29:19] *** Quits: Horwitz (~mich1@p200300ec9f02e800022268fffe64e7c4.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) [01:41:51] *** Joins: Horwitz (~mich1@p200300ec9f29db00022268fffe64e7c4.dip0.t-ipconnect.de) [01:41:51] *** ChanServ sets mode: +o Horwitz [04:18:54] *** Quits: owlman (~owlman@61-68-86-34.tpgi.com.au) (Quit: Konversation terminated!) [06:46:21] Hi mvglasow, I actually looked into this and would like to remove the http function from the binfile plugin as we can't support it due to the lack of the Mapserver. Additionally I would also like to remove any self implemented things where suitable alternatives are around. What I don't want is to add those dependencies to navit/support. We should fix the build environment in the long term to accomplish this. So [06:46:22] please just pick the best library you can find and start with the fun part :) Also, thank you for your support and time [08:49:44] *** Quits: Millesimus (~millesimu@gomez.millesimus.de) (*.net *.split) [08:52:40] *** Joins: Millesimus (~millesimu@gomez.millesimus.de) [11:26:38] jkoan full ack, navit/support or homebuilt solutions are kind of a kludge, not the preferred solution [11:27:58] btw, I have https://github.com/navit-gps/navit/pull/1087 in the pipe which should fix the NDK build issue, I just held it back while you were working on the F-Droid build issue [11:28:28] from your side, is that OK to merge or would you prefer me to hold it back until the F-Droid issue is resolved? [11:30:19] a propos F-Droid: I investigated the idea of integrating the F-Droid build into CI a bit further for one of my own projects [11:30:27] see here: https://gitlab.com/traffxml/roadeagle/-/commit/7388318221e6c078b1e8286295a340d5b0b4681b [11:31:04] basically, I copied the `fdroid build` step from fdroiddata CI over and modified it slightly: [11:32:38] no git diff (as we don't have the fdroiddta repo at all), reduce the build loop to a single run, and just run `fdroid build` (which will build from .fdroid.yml in the root dir of the source tree) [11:33:49] the build recipe goes in the root of the source tree and must be named .fdroid.yml; specifying `commit: HEAD` for the version to build will build the current commit [12:39:57] *** Joins: peterm6881 (~peter@91.40.93.209.dyn.plus.net) [12:42:35] *** Quits: peterm6881 (~peter@91.40.93.209.dyn.plus.net) (Client Quit) [13:30:47] *** Quits: mvglasow (~mvglasow@78-61-158-97.static.zebra.lt) (Ping timeout: 272 seconds) [13:44:14] *** Joins: mvglasow (~mvglasow@78-61-158-97.static.zebra.lt) [17:35:14] Thx mvglasow [17:35:44] For the PR: the title has WIP in it, is this up to date? [17:36:32] And for the f-droid build: quite cool [17:48:03] jkoan: yes, the PR is up to date, I had just added WIP to avoid conflicts with any F-Droid debugging [17:48:19] but the code isn't going to change [18:26:49] Than its okay to be merged [18:56:14] great [18:56:59] btw, I am just trying to get an F-Droid build job into CI [18:59:05] currently still trying to figure out why CircleCI can't find the fdroid executable [19:40:19] ..found it, `export` is limited to one `run` item [20:50:26] still not working, I am getting some python error [20:51:11] if anyone feels like taking a look, source is at https://github.com/mvglasow/navit/tree/fdroid-ci (look in .circleci/config.yml and .fdroid.yml) [20:51:37] and the last CI results are at https://github.com/mvglasow/navit/runs/1894786898 [20:52:50] the script is the same as on GitLab CI and works there, somehow CircleCI behaves differently, no idea why