source-type: git uses --remote for submodules
Metadata
Current evaluation
Fixed by merged PR snapcore/snapcraft#1344 (commit a8500f718), removing --remote from Git submodule updates so superproject-recorded revisions are honored.
Resolution: closed resolved
Reason: PR #1344 was merged as commit a8500f718 and removed --remote from Git submodule update commands, ensuring Snapcraft checks out the revision recorded by the superproject.
Evaluated by: mr-cal-bot
No scores available.
Issue body
https://github.com/snapcore/snapcraft/commit/d22880fdcee434a5e85c376e8f26c61a661231ce introduced `--remote` to `git submodule update` calls.
If I understand the git manual right [1], this actually updates to HEAD from the remote repository, effectively ignoring the commit recorded in the superproject.
This sounds really wrong as this means the superproject loses control over the submodule checkout.
[1] https://git-scm.com/docs/git-submodule#git-submodule---remote
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR snapcore/snapcraft#1344 (commit a8500f718), removing --remote from Git submodule updates so superproject-recorded revisions are honored. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in canonical/snapcraft#1344 (a8500f718) by removing --remote from Git submodule updates, restoring use of the superproject-recorded commit. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in PR #1344 via commit a8500f718: submodule updates no longer use --remote, so the commit recorded by the superproject is checked out. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The report noted that --remote in git submodule update overrides superproject commit references, breaking submodule control. Closed without discussion or a fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comment or resolution. The reported issue regarding --remote overriding superproject commit references in git submodule update was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Using --remote in git submodule update causes submodules to track remote HEAD instead of the superproject's recorded commit. The report was closed without comments or resolution, indicating it was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. The report noted that --remote in git submodule update ignores superproject commit references, but no fix was implemented and the issue was closed. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#1344
(confidence 100%)
Merged fix removing --remote from Git submodule updates.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1344 git: don't use --remote for updating submodules | snapcraft | merged | Merged #1344 as commit a8500f718, removing --remote from Git submodule updates so the commit recorded in the superproject is checked out. | |
| #249 Git source: Support submodules. | snapcraft | merged | Merged canonical/snapcraft#249 via 1984cb339, adding recursive Git cloning and submodule updates on pull to resolve LP #1536698. | |
| #1957767 no way to use non-recursive git source | snapcraft (launchpad) | closed | Merged in snapcore/snapcraft#3629, adding configurable Git submodule fetching so non-recursive clones can be requested. | |
| #1640675 Add source option for git submodules | snapcraft (launchpad) | closed | Feature request implemented: source-submodules added to git sources, merged as snapcraft PR #3629 (383c1f1ce) and craft-parts PR #169 (3891f255); shipped in Snapcraft 7 and 8. Maintainer closed the2016 Launchpad bug as done. | |
| #1536698 Git source doesn't support submodules | snapcraft (launchpad) | closed | Git source submodule support was implemented and merged in ubuntu-core/snapcraft PR #249 (merge commit 1984cb339), using recursive cloning and submodule updates on pull. |