-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F-Droid can't build #1852
Comments
Seems confusing that f-droid happily built 2.5.0 not that long ago, which had the same dep. |
not really as it had https://github.com/owntracks/android/blob/v2.5.0/project/gradle/libs.versions.toml#L47 from this repo https://mvnrepository.com/artifact/com.android.tools/r8/8.3.37 and your current https://github.com/owntracks/android/blob/v2.5.2/project/gradle/libs.versions.toml#L47 is available only from the untrusted repo fyi that repo will never be used as we remove it from the code https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/org.owntracks.android.yml#L24 |
Aha, that makes sense. Will revert it. |
Is there an fdroid command that I can use to catch this in CI?
|
remove other maven repos that are not on this list: https://gitlab.com/fdroid/fdroidserver/-/blob/02f005280654e733ffc176b80d6119b5d5f55d50/fdroidserver/scanner.py#L506-L526 then try to build 🤷 😄 |
Looks like there was a historical reason we were depending on a version of r8 from Google, but now can probably rely on the one that's shipped as part of AGP.
Yeah, I see that. Be nice if there was some lint we could run so we don't fall over these issues inadvertently at publish-time. |
|
Hmm. Can't seem to get that to work here:
I can see scanner is doing the prebuild, but then it's not validating that the resulting project can resolve its dependencies (which it won't be able to without that google repo). edit
|
Look in the recipe, there's a |
I see that - I don't think that's something we added? My point is that F-Droid could (in theory) change the recipe in the future, and the f-droid scan stop won't necessarily alert us that build will fail. Maybe the easiest thing here is to actually do an f-droid build as part of the CI. |
Depends on how you want to continue. If the repo is not there anymore, we'll remove the Hence, if you readd it in the future, the scanner will alert us. |
I've taken the repo out, so the sed step is now probably unnecessary. I'll change our f-droid CI job to do a scanner & build. Is there a trivial way to get fdroidserver to scan and build from |
It scans the current folder state, you can trigger whenever you want. |
It scans the current folder for metadata, yes, but I'll need it to build off the HEAD of |
You can update versionCode, versionName and commit in the .yml, then trigger the scan |
this maven repo https://github.com/owntracks/android/blob/v2.5.2/project/build.gradle.kts#L6 is not on the small trusted list: https://gitlab.com/fdroid/fdroidserver/-/blob/fe1c6b5149f8b014e6105a54396bace9a806db63/fdroidserver/scanner.py#L506-L527
ref: https://monitor.f-droid.org/builds/log/org.owntracks.android/420502019#site-footer
/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/commit/ac608aa49242a82cf0f47daff4eba47c657e1e1e
The text was updated successfully, but these errors were encountered: