Zum Inhalt der Seite gehen

This week on #FDroid (TWIF) is a lot to read, and also we missed the toot about last week.

In short:
- F-Droid client 1.21 was released, but you should wait for 1.21.1 before you update
- there were some bugs in DAVx⁵, Nextcloud and Tailscale, so be careful in updating these too
- we're working together with @Codeberg to get our builds from apps hosted there working again
- any much more

Read the full details at
f-droid.org/2024/10/24/twif.ht… and f-droid.org/de/2024/10/17/twif…


This Week Is on Fire | F-Droid - Free and Open Source Android App Repository

This Week in F-DroidTWIF curated on Wednesday, 23 Oct 2024, Week 43F-Droid coreJust after the last TWIF was published we thought it will be just another nice...
f-droid.org
#FDroid @Codeberg.org
Als Antwort auf F-Droid

Codeberg.org
Codeberg.org
• •

Our admin tried something one or two days ago and it seems like, as of the time of publication, cloning from Codeberg with your provider works again: monitor.f-droid.org/builds/log…

Could you please confirm with us? Thanks! ~n

log: com.zell_mbc.medilog:5462 - F-Droid Monitor

monitor.f-droid.org
Als Antwort auf Codeberg.org

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
Nope, see gitlab.com/fdroid/fdroiddata/-… – F-Droid instead set up mirrors at GitLab. The app you've linked to uses that mirror. As for line 7, that probably shows "Source" instead of "Repo".
screenshot from the current YAML metadata showing MediLog is built from a GitLab mirror

Codeberg hosted apps - temporary use mirror to build (!16090) · Merge requests · F-Droid / Data · GitLab

ref: https://chaos.social/@grote/113334573794735891 some limitations might apply: mirrored tags on gitlab don't have the associated APKs, so main...
GitLab
Unbekannter Ursprungsbeitrag

Codeberg.org
Codeberg.org
• •

@IzzyOnDroid @hiddengravitas A genuine thank you to you both for stepping up to show us the ropes and give us the help we really needed – this wild-goose chase took us a large amount of extra volunteer hours during a heavy week.

We may not be like other SCM's (mostly billion $ companies), but that's exactly why we really do prefer interpersonal communication and cooperation over social media posts. Next time, for the sake of the developers, we hope to have that. I hope the issue is fixed. ~n

@IzzyOnDroid ✅ @hiddengravitas
Unbekannter Ursprungsbeitrag

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
@hiddengravitas Indeed, that was a day before the MR I've linked was merged. Then it seems @Codeberg was able to solve the issue without their help – thanks to the Codeberg crew for getting that done amidst their current double-heavy workload! 🙇
@Codeberg.org @hiddengravitas
Als Antwort auf F-Droid

Codeberg.org
Codeberg.org
• •

The comment in social.librem.one/@eighthave/1… indicates the IP addresses and provider used by F-Droid should not become public information. It looks like we indeed managed to figure them out with some days of digging in our access logs.

However, we are not sure how to deal with this information further. Our allowlist is managed in public, and we probably need to figure out a better way to persist the exception without disclosing your IP range.

~f

Hans-Christoph Steiner

2024-10-23 07:03:35


@grote @fdroidorg where are production buildservers are located is not public information, and it is not necessarily static. But I imagine it would be easy to figure out which IP address by looking at the logs on the codeberg side. We haven't been blocked before by any other git/scm hoster, to my knowledge.

Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos

⇧