[Bug] F-Droid can't build
Closed this issue · 9 comments
ref: https://monitor.f-droid.org/builds/log/com.w2sv.filenavigator/5#site-footer
so looks like you tagged https://github.com/w2sv/FileNavigator/releases/tag/0.1.0 from d160247
but the APK was built from 3ffc571
yet if I build from that
==== detail begin ====
verification of APK with copied signature failed
Comparing reference APK to APK with copied signature...
Unexpected diff output:
Binary files /tmp/tmp1hkqq9hy/unsigned_binaries_com.w2sv.filenavigator_5.binary/content/assets/dexopt/baseline.prof and /tmp/tmp1hkqq9hy/_tmp_tmp1hkqq9hy_sigcp_com.w2sv.filenavigator_5/content/assets/dexopt/baseline.prof differ
Binary files /tmp/tmp1hkqq9hy/unsigned_binaries_com.w2sv.filenavigator_5.binary/content/classes.dex and /tmp/tmp1hkqq9hy/_tmp_tmp1hkqq9hy_sigcp_com.w2sv.filenavigator_5/content/classes.dex differ
==== detail end ====
/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/commit/e83b9f17de7b787ce3877c07794e8014012e9483
I think it was the other way around, I built the APK from d160247, then my Make publishing routine threw an error during the upload to the playstore, because the release notes were too long, so I changed them and thereupon tagged the release from 3ffc571. I don't know how that could possibly impact the generated baseline profile or the dex classes, though.
I could simply create a new release, I have one at the ready anyways. Would that be a valid workaround? :D
Please do
you tagged https://github.com/w2sv/FileNavigator/releases/tag/0.1.1 from 8ee0e80
but you built from 6f5a0ab
diff -r /tmp/tmprxk9qcuj/unsigned_binaries_com.w2sv.filenavigator_6.binary/content/META-INF/version-control-info.textproto /tmp/tmprxk9qcuj/_tmp_tmprxk9qcuj_sigcp_com.w2sv.filenavigator_6/content/META-INF/version-control-info.textproto
4c4
< revision: "6f5a0ab3fafb0979f39a2e26ae00a1606cc2e799"
---
> revision: "8ee0e8060c30075c4cefb66a16330c6594fa0758"
Uff...
Next try I guess: https://github.com/w2sv/FileNavigator/releases/tag/0.1.2
Sorry...
Thank you.