‘full’ is an incomplete specification. What needs to be built is build type ‘GitHub’, so only signature V1 will be used (which was what changed in version 1.992 besides specifying the exact NDK version) and product flavor ‘full’ to use the right build config (links, etc).
If I put gradle: yes it builds both Full and Play, as releases, so Github can’t be build…no release.
If I omit gradle: if tries the old build system
DEBUG: > /home/strech/android/tools/android update lib-project -p .
Error: . is not a valid project (AndroidManifest.xml not found).
ERROR: Could not build app eu.faircode.email: Failed to update project at .
Yes, F-Droid builds to verify, and users will get an update, but you can have the inbuild autoupdate/your fdroidrepo update the app before we verify it.
The trick is that being signed twice users can update from multiple places.
check the F-Droid docs, like the Reproducible Builds page, for more
info. It will likely require you dig into things to figure out why. reproducible-builds.org also has useful resources.
`* What went wrong:
Execution failed for task ‘:app:stripFullReleaseDebugSymbols’.
Requested NDK version 21.0.6113669 did not match the version 12.1.2977051 requested by ndk.dir at /home/vagrant/android-ndk/r12b
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
I have tried to figure this out on my own, but I have zero experience with reproducible builds, so I need help on this. What should I as developer do to make this happen?
first, find the diffs between builds. diffoscope is the tool for
that. You can just run the build twice on your own machine to start
with. Then take it from there.