-
-
Notifications
You must be signed in to change notification settings - Fork 36
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 #147
Comments
Hi Licaon Kter, thank you for reporting the failure. |
Version 44 built successfully |
Reproducible build failed. Maybe clean the cache and rebuild? Could you please take a look? Thanks! |
F-Droid, oh, F-Droid 😄 |
ua.com.radiokot.photoprism-1.31.0(1).apk.html.zip |
I accidentally added an extra line break to the class source code, maybe that's why the lines are offset by 1, although I thought the compiler ignores all the line breaks and spaces. |
It works, thanks! |
and again: https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/8327688100#L659 diff log is really small:
|
Hi, I've cleaned the local build cache and re-built the APK. The updated file is attached to the release: |
same fail, same diff log :( |
@licaon-kter Ok, I have no idea on the cause of the issue, so now I just signed the APK from the fdroid build run artifacts and attached it to the release. Please, re-run. Thank you for your work 🤝🏻 |
that's not how reproducibility works 🤷 |
|
@Radiokot yes, go ahead then 🤷 |
@licaon-kter please, re-run the job |
this was ok in the CI https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/8340827080 but failed on the main server still: https://monitor.f-droid.org/builds/log/ua.com.radiokot.photoprism/48#site-footer will loop locally to see if there's a pattern |
limiting to 6 cores was ok in my testing, eg. 22 cores was failing will reopen if main server fails again: https://gitlab.com/fdroid/fdroiddata/-/commit/9437c790e215668c4f12cbf01b8a4b0aa4ad7aca |
Thank you! |
ua.com.radiokot.photoprism-1.33.0.apk.html.zip Reproducible build failed. Maybe we need a clean rebuild? |
@linsui clean rebuild hasn't worked for some time now. The differences are negligible. I accept the package built by F-Droid as a correctly built one, I have signed it and attached to the release. Please, re-run the job. Thank you. |
OK, thanks! But there must be something different that the diff is so large. Did you build it with openjdk 17? |
Weird. I got the same apk. Could you please build the apk with openjdk 17, e.g. https://adoptium.net/temurin/releases/? |
I'll try it for the next release, let's proceed with the APK built by F-Droid for now. |
OK, thanks! |
Reproducible build failed again. |
Hi @linsui , that's unfortunate, this time it was built with JDK 17 as you suggested. Please, re-launch the task, I once again signed the F-Droid build and re-attached it to the release. Thank you. |
Maybe a clean build helps. Your apk was not built from the tag. |
What makes you think that? |
The apk has a vcs info embeded. It points to the commit before the tag. So you built the apk before committing the last change. |
I didn't know that. Could it cause the difference in dex files though? I build APK before putting a tag in order to smoke test it. If everything's fine, I update the changelog and put a tag, I don't change the sources 🤔 |
See https://f-droid.org/docs/Reproducible_Builds/#vcs-info as the tree info (commit) ends up in the APK. While we understand that developers build and test during their normal workflow, please upload release APKs built after tagging, from a clean tree at the actual tagged commit (i.e. without local changes or remaining artifacts from previous builds). |
It shouldn't cause the dex diff. Did you clean the cache before building? |
The diff is similiar though... It's still about smali_classes4/ua/com/radiokot/photoprism/features/gallery/view/model/GalleryViewModelGallery.smali. |
right, but it's nice that it acts as a clue to how the build was made, it might help |
Thanks guys, next time I'll build the APK after committing and tagging a version update. As for the clear cache, I run the Gradle |
Guys, please re-run the update job with the latest artifact attached to the release |
Thanks! |
Looks like it fails to build on both buildserver: https://monitor.f-droid.org/builds/log/ua.com.radiokot.photoprism/50#site-footer and for me locally difflog:
|
I literally signed the APK built by F-Droid update checker on Jan 09 and attached it to the release as |
...built by the F-Droid Gitlab CI user for verification at metadata merge time only. Now that I look at it again, it's the same diff log as Nov 12 🤦 |
Never mind |
The latest release artifact, version 1.35.0(51), has been built and signed by a GitHub action on Ubuntu 24.04 with Java 17 (Temurin). I wonder if there is going to be a diff this time. |
Ah, one more thing @Radiokot https://gitlab.com/fdroid/fdroiddata/-/jobs/9037719640#L609 We find that there is a It's a Signing block added by AGP and encrypted with the Google public key so it can't be read by anyone else except Google. You can read more about it here and here. While this was added a while ago, we were only enforcing it for new apps, and recently we started scanning updates too. Could you please disable it with the following code?
Thanks! |
Thanks, @licaon-kter
|
https://monitor.f-droid.org/builds/log/ua.com.radiokot.photoprism/43#site-footer
Is that coming to maven soon or should we build it from source instead?
/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/commit/ce82a52e3d2d08ae7af2b0b34d654d4a04fa442c
The text was updated successfully, but these errors were encountered: