-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F-Droid #111
Comments
Hey! I don't see why not. That said, I'm not managing the F-Droid version, so someone else should jump in and update it (I guess?). |
I don't know, but perhaps @IzzySoft could advise. |
UpdateCheckMode: Tags ^android-\d\.\d$ Proper tag names might help, no? 😉 Check when that pattern matched last (hint: |
Additionally, @ikanakova , besides the new tag format the build step might be different now since I'm using Expo. |
@mmazzarolo Does that mean the new version won't be on the F-Droid? |
Hey @ikanakova I didn't create and I never updated the F-Droid version of Breathly... I'm not even familiar with F-Droid and unfortunately I don't have much free time lately to investigate/learn how to update and support the new version :/ |
@mmazzarolo if you want I can adjust the UpdateCheckMode mentioned above at F-Droid (disclosure: I'm one of the maintainers there) and we can see if the build succeeds once the updater has picked up the new release. We'd just need to remove the trailing |
@IzzySoft that works for me, thank you |
OK, there you go – and fingers crossed! |
Hm. I've no idea why it insists on v1.9 being the latest release – stripped UCM down to |
Did you rewrite the app in Expo? The recipe needs a complete overhaul then... |
Yes. |
Thanks @licaon-kter – and yes, see above… |
@mmazzarolo help? Updated recipe: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12791/diffs?commit_id=fb2d997a907effcf86057090cd8818bc79828d51 But fails later: Where are the build instructions exactly? |
|
Will the new version be available on F-Droid? There is still a version 1.9 on F-Droid.
The text was updated successfully, but these errors were encountered: