[01:27:57] *** Quits: Horwitz (~mich1@p200300ec9f29db00022268fffe64e7c4.dip0.t-ipconnect.de) (Ping timeout: 265 seconds) [01:40:45] *** Joins: Horwitz (~mich1@p200300ec9f3e0d00022268fffe64e7c4.dip0.t-ipconnect.de) [01:40:45] *** ChanServ sets mode: +o Horwitz [03:04:41] *** Quits: Cyker (~Cyker@81-178-217-39.dsl.pipex.com) (Ping timeout: 256 seconds) [03:06:48] *** Joins: Cyker (~Cyker@host-92-28-106-115.as13285.net) [06:51:05] I think the error comes from here: [06:51:08] Parsing manifest at './build.gradle' [06:51:26] got package=None, version=None, vercode=None [06:52:37] Probably because we don't have the package or any version information within this file [06:54:06] And because of this the line os.path.join('build', app.id) in python break's [06:54:36] Because app.id is None [10:32:24] *** Quits: mvglasow (~mvglasow@78-61-158-97.static.zebra.lt) (Ping timeout: 272 seconds) [10:45:50] *** Joins: mvglasow (~mvglasow@78-61-158-97.static.zebra.lt) [11:06:05] jkoan good catch, didn't even realize we don't have an app ID anywhere in the recipe... I'll investigate (and in the meantime have filed a bug for a more descriptive error message) [14:28:02] apparently, when the toolchain is gradle, fdroid scans build.gradle for a manifest path, then extracts the package ID from the manifest [14:29:17] it looks for the file in the root of the source tree, unless subdir is specified (though specifying subdir has the side effect of F-Droid cd'ing into that dir prior to building) [14:30:59] I tried `subdir: navit/android` and cd'ing out of it at the start of each build script, but then the build can't even find the C compiler [14:31:36] any way we can provide the manifest path in the top-level build.gradle? or would that break something else? [15:03:12] as far as I can tell, adding an unused android section to the top-leven build.gradle will break checkstyle, but no idea about the implications about also adding the plugin and as much as is needed to tell the plugin to do nothing in here