chore: correct hosted isar paths in fdroid_build_isar.sh #23529
Merged
+5
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Following the suggestion in #22757 (comment), adjust the F-Droid script to point at the new isar paths.
This should hopefully unblock F-Droid builds, which are currently stuck on version 2.0.1; see https://gitlab.com/fdroid/fdroiddata/-/merge_requests/28208 which is currently marked
waiting-for-upstream.How Has This Been Tested?
This has not been tested. (Apologies; I don't have a setup for testing nor know the F-Droid process well enough to be confident in verifying the results.)
Checklist:
I have made corresponding changes to the documentation if applicableN/AI have confirmed that any new dependencies are strictly necessary.N/AI have written tests for new code (if applicable)N/AAll code inN/Asrc/services/uses repositories implementations for database calls, filesystem operations, etc.All code inN/Asrc/repositories/is pretty basic/simple and does not have any immich specific logic (that belongs insrc/services/)Please describe to which degree, if any, an LLM was used in creating this pull request.
No LLM was used in creating this pull request.