-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add troubleshooting section for building
- Loading branch information
Showing
2 changed files
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,3 +19,4 @@ before reading this section. | |
manifests | ||
sandbox-permissions | ||
guides | ||
troubleshooting |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
Troubleshooting | ||
=============== | ||
|
||
Sometimes you run into issues when building Flatpaks. This page includes a list | ||
of common problems and how to solve them. | ||
|
||
Remote server doesn't support shallow cloning | ||
--------------------------------------------- | ||
|
||
If you get an error message like | ||
``fatal: dumb http transport does not support shallow capabilities`` when | ||
building your Flatpak application, it's because ``flatpak-builder`` will by | ||
default attempt to shallow clone git repositories as an optimisation. However, | ||
not all git remotes support shallow cloning, and in such cases you can disable | ||
this optimisation by setting the ``disable-shallow-clone`` property to ``true`` | ||
in your source. |