Build fails while installing Android Support Repository

F-Droid currently is not able to build org.totschnig.myexpenses: https://f-droid.org/wiki/page/org.totschnig.myexpenses/lastbuild_283. Is there something I can change as the maintainer of the app to remove this obstacle? My users are waiting for fixes to critical bugs, so would be great if F-Droid could deliver the latest version to them again.

F-Droid currently is not able to build org.totschnig.myexpenses: https://f-droid.org/wiki/page/org.totschnig.myexpenses/lastbuild_283. Is there something I can change as the maintainer of the app to remove this obstacle? My users are waiting for fixes to critical bugs, so would be great if F-Droid could deliver the latest version to them again.

No, nothing on your end, see Build error: The SDK directory (/home/vagrant/android-sdk) is not writeable (#23) · Issues · F-Droid / admin · GitLab.

the buildserver needs to be updated to allow the Android SDK to auto-update itself. The fix is already in git.

Is it forseeable, when the fix will be deployed? When it is deployed, will failed builds be triggered again automatically?

See Build error: The SDK directory (/home/vagrant/android-sdk) is not writeable (#23) · Issues · F-Droid / admin · GitLab.

Yes, failing builds get automatically retried.