F-Droid build failed

[linsui]

Brief summary

https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/15417568149 Could you please take a look? Thanks!

Steps to reproduce

No response

Usagi version

0.0.32-beta2

Android version

--

Device

No response

Acknowledgements

• This is not a duplicate of an existing issue. Please look through the list of open issues before creating a new one.
• This is not an issue with a specific plugin / source / extension. Otherwise, you must close this issue immediately because we do not accept support for issues related to it.

[dragonx943]

Brief summary

https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/15417568149 Could you please take a look? Thanks!

Steps to reproduce

No response

Usagi version

0.0.32-beta2

Android version

--

Device

No response

Acknowledgements

• This is not a duplicate of an existing issue. Please look through the list of open issues before creating a new one.[x] This is not an issue with a specific plugin / source / extension. Otherwise, you must close this issue immediately because we do not accept support for issues related to it.

I already fixed this problem in latest commit. However, I believe the issue stems from F-Droid pipelines, which is currently experiencing some unexpected problems...

Known issue: I built Usagi 0.0.32-beta2 using Android Studio on Windows, which uses the CRLF (Windows) line ending format, whereas F-Droid pipeline on GitLab uses the LF (Linux) format. This issue can be resolved by rebuilding Usagi on Linux, re-uploading the APK file, and re-running the pipeline.

[linsui]

Which commit should we use?

[dragonx943]

Which commit should we use?

Usagi 0.0.32-beta2 used 553d7e8 commit. Can you trigger F-Droid bot to rebuild it?

[linsui]

https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/15417568149 Still can't built it.

[dragonx943]

https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/15417568149 Still can't built it.

K, I will fix it in 1.0.0-beta1 👌

[dragonx943]

Would be fixed in next release. Resolved cff0593