Closed ca-scribner closed 3 months ago
I think both (1) and (2) affect this repo.
To debug the release snap action run failure I've moved the credentials to ~/.local/share/snapcraft/launchpad-credentials
. That resolves the issue where that action run hangs while asking the user to do 2FA, but it immediately hits a new error:
snapcraft remote-build --launchpad-accept-public-upload
# remote-build is experimental and is subject to change. Use with caution.
# snapcraft internal error: RemoteBuildInvalidGitRepoError(brief='The Git repository is invalid for remote build.', details='Remote build for shallow cloned git repos are no longer supported')
which I think is issue (2) mentioned above. But, good news is that converting the shallow git clone to a full clone (git fetch --unshallow
during debugging) unblocked snapcraft remote-build
. So if we change the workflow's actions/checkout
fetch-depth
to 0
I think it'll work how we want.
snapcraft 8.2.0 introduced breaking changes to
snapcraft remote-build
:$XDG_DATA_DIR/snapcraft/provider/launchpad/credentials
to$XDG_DATA_DIR/snapcraft/launchpad-credentials
(1) I think blocks this repo from releasing, as seen in the most recent failure for the release snap workflow run