You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can check our recipe and the log, it's all public. I've just checked again to make sure: sha256sum confirms we've built the APK matching the one currently at the release, so it's no "replacement" either. The machine which built it is running trixie on the host, and is equipped with 32 cores and 128 GB RAM, if it helps…
@licaon-kter No clue yet. I added the link as a reference. GitHub Actions created the release and built the APK, and I can reproduce the same binary on my machine. I'll dig into the F-Droid pipeline later.
Activity
DeweyReed commentedon Jul 16, 2026
Thank you!
I reviewed the log and searched for it, but I couldn't determine the reason. I'll get back to this problem the moment I get some free time.
licaon-kter commentedon Jul 29, 2026
Odd that Izzy has it marked as RB
I tested with Java 17 (like Izzy builds) and the output is the same
the diff looks like the usual "need to clean all caches and gradle cache before building from a clean tree" 🤷
IzzySoft commentedon Jul 29, 2026
You can check our recipe and the log, it's all public. I've just checked again to make sure:
sha256sumconfirms we've built the APK matching the one currently at the release, so it's no "replacement" either. The machine which built it is running trixie on the host, and is equipped with 32 cores and 128 GB RAM, if it helps…DeweyReed commentedon Aug 4, 2026
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/39478
licaon-kter commentedon Aug 4, 2026
@DeweyReed yes, but any fix?
DeweyReed commentedon Aug 5, 2026
@licaon-kter No clue yet. I added the link as a reference. GitHub Actions created the release and built the APK, and I can reproduce the same binary on my machine. I'll dig into the F-Droid pipeline later.