-
Notifications
You must be signed in to change notification settings - Fork 15
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
LFS support broke #132
Comments
Alright, so something is up. Enter the flatpak runtime via
Then I cloned the repository via
All cloned fine and dandy.
git lfs fully fetched, no issues. So this means that the patch is improperly using git, I narrowed it down via modifying the patch and figured out that the following patch is broken. @@ -606,6 +616,15 @@ builder_git_mirror_repo (const char *repo_location,
was_shallow ? "--unshallow" : NULL,
NULL))
return FALSE;
+
+ g_print ("Fetching LFS assets\n");
+ if (!git (mirror_dir, NULL, 0, error,
+ "lfs", "fetch", "--all", NULL))
+ {
+ git (mirror_dir, NULL, 0, error,
+ "lfs", "logs", "last", NULL);
+ return FALSE;
+ }
}
if (alternates) |
But it does not make sense, why is it throwing a 404, no matter how long I look at it I do not understand. |
This is an issue with the source repository here. See flathub/com.revolutionarygamesstudio.ThriveLauncher#50 (comment) The lfs patch seems to work fine with other LFS repos. |
Description
At some point within the last month, git-lfs support broke itself again.
Expected Behavior
git-lfs properly pulls objects.
Actual behavior
flatpak run org.flatpak.Builder build --force-clean build *.yaml
log.txtAdditional Context
I tested with flatpak-builder as installed via rpm, version 1.2.3 and it worked fine.
Experimenting with the flatpak version of the builder, I discovered that while the builder does use the same version of the flatpak-builder, it has something preventing the proper pull via git-lfs.
I experimented with the flatpak versions of builder, from the current version to all the way back to 567fcc0 .
This is my limit of knowledge currently.
The text was updated successfully, but these errors were encountered: