My desktop and laptop aren't fast enough to reproduce the issue locally, but test_sources_update "regularly fails" on half of Debian's CI, reproducibility, and regression testing networks. The Release Team now considers this a serious (release critical) issue. https://bugs.debian.org/1086524

Here is a recent log for 0.10.0-beta1 on arm64:
https://tests.reproducible-builds.org/debian/logs/experimental/arm64/vorta_0.10.0~beta1-1~exp1.build2.log.gz

The dashboard (with logs) for all Reproducibility Builds is available here:
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/arm64/vorta.html

The main dashboard for the CI network is here:
https://ci.debian.net/packages/v/vorta/

Please note that you actually need to click on a particular version under one of the four columns in order to access the CI and regression-testing history for that suite. The nature of the problem Paul Gevers reported is logged on each arch under "testing"; this is where we prepare for the next stable Debian release. Unstable tracks the latest stable version and/or the latest version believed to not have any release critical issues (ie crashes, data loss). Attempts to migrate the experimental version to unstable are also logged here.

All details about environment are also logged; please let me know if you have any questions about interpreting them.