Post B8C1Die6RWMzCIQXtQ by fdroidorg@floss.social
 (DIR) More posts by fdroidorg@floss.social
 (DIR) Post #B8C1DiMNVQBwJK8OGW by pachli@mastodon.social
       0 likes, 0 repeats
       
       Hey @fdroidorg - trying to create an issue on gitlab.com is failing/hanging at the moment, so reporting this here (I appreciate this is not an ideal bug report forum...)https://verification.f-droid.org/packages/app.pachli/ seems to be very out of date (from the app's "Reproducibility status" link).At the time of writing it shows the last attempt to check the reproducibility status was December last year.There has been at least one release per month since then, and the most recent release *is* showing up on fdroid.org.
       
 (DIR) Post #B8C1Die6RWMzCIQXtQ by fdroidorg@floss.social
       0 likes, 0 repeats
       
       @pachli https://f-droid.org/about/#contact has more ways. And yes, the verification server is severely behind, due to its allocated resources. Since the Oct 2025 main server upgrade, we are building many more apps than we can verify. 😉
       
 (DIR) Post #B8CIEaG0obp6gu9nPs by soaproot@sfba.social
       0 likes, 0 repeats
       
       @fdroidorg Fascinating. I always thought of the hard part of reproducible builds as being making the verification possible but hadn't even thought about how the verification is to be done. @pachli
       
 (DIR) Post #B8DgocMCebgquiI8e0 by fdroidorg@floss.social
       0 likes, 0 repeats
       
       @soaproot @pachli Note that, for apps signed by upstream, the reproducible built ones, we are hosting their updates after our main server verifies.The separate "verification server" is doing a second pass for all apps, to verify versus published packages.