this post was submitted on 21 Jul 2024
0 points (NaN% liked)

Jerboa

10291 readers
6 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
[email protected]
0
F-droid builds of 0.0.70 and 0.0.71 seem to be failing (lemmy.sdf.org)
submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]
10 comments fedilink hide all child comments
 

I use f-droid to update the app. Didn't see the recent updates and saw the failed build after a search.
https://monitor.f-droid.org/builds/log/com.jerboa/71#site-footer

I don't know much about programming... not sure whether this is an issue to be resolved from the side of Jerboa or F-droid. Had doubts whether I should inform of the issue in Jerboa's github and sharing this here because of that.

F-droid seems to have done a recent cleanup of apps, focusing on non-foss stuff. Not sure if that has an effect, but sharing the info.
https://f-droid.org/en/2024/07/18/twif.html

^Maybe related:
Builds of com.dessalines.thumbkey:96 and com.dessalines.rankmyfavs:11 seem to have failed too.
https://monitor.f-droid.org/builds/build (The page lists failed builds at the end)

top 10 comments
sorted by: hot top controversial new old
[–] [email protected] 0 points 3 months ago (1 children)

This is affecting about 5-10 apps, a few others besides mine. It's a new gradle version checksum verification issue.

I asked about it, and it should get fixed in the next build cycle, sometime this week hopefully. I've been waiting to "announce" my new app until this one gets fixed.

In the meantime, I also put all my apps on izzyondroid, which are updated to the latest versions.

[–] [email protected] 0 points 3 months ago

Thank you

[–] [email protected] 0 points 3 months ago (2 children)

Checkout NeoStore. Which uses multiple sources. The izzyondroid repo is successfully building 0.0.70 and 0.0.71

[–] [email protected] 0 points 3 months ago

Or droidify, it also adds izzyondroid by default.

[–] [email protected] 0 points 3 months ago* (last edited 3 months ago) (1 children)

IzzyOnDroid doesn't build apps, but hosts apk's of chosen apps from Github/Codeberg/Gitlab, right?

https://apt.izzysoft.de/fdroid/index/info

[–] [email protected] 0 points 3 months ago

Yes, but it's the app creators themselves who created those apks. Basically it swaps out trust for 3rd party packagers in for the open source app devs themselves.

[–] [email protected] 0 points 3 months ago

I find that the F-Droid "system" is pretty opaque. There doesn't seem to be any way that you can track a bug somewhere that a build is failing or who is working on it. Just the build fails and...hopefully someone realizes it and they'll fix it at...some date in the future.

[–] [email protected] 0 points 3 months ago (1 children)

What? I don't speak tech

[–] [email protected] 0 points 3 months ago

Crowdstrike holding F-droid's beer.