Snapcraft complains the missing `source` property when the source URL is determined in override-pull scriptlet
Metadata
Current evaluation
Dynamic override-pull builds cannot omit source because validation still requires it, while a dummy source triggers source-type detection failure. This old, unlabelled report needs reproduction against the current lifecycle.
Suggested action: needs triage
Reason: The report provides both concrete validation failures, and current craft-parts code explicitly executes override-pull "instead" of the default pull, supporting the expected behavior. However, the issue has no labels, reproducer, version, or maintainer response, and no resolving commit was identified, so its behavior must be reproduced against the current dependency stack.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
12
Complexity:
58
Confidence:
81
Actionability:
66
Issue body
I've set up an `override-pull` scriptlet for some snaps to automatically parse the upstream release page and download & extract the latest release tarball to SNAPCRAFT_PART_SRC, as the actual source URL is determined in the scriptlet the `source` property isn't really required but Snapcraft currently will still complain:
* Failed to load plugin: properties failed to load for main: 'source' is a required property
* Failed to pull source: unable to determine source type of 'Parsed automatically at main-pull scriptlet'
('Parsed automatically at main-pull scriptlet' is a dummy value set in snapcraft yaml)
Some thoughts:
* The checks probably should be deferred to the point where the snapcraft-managed-pull is triggered
* `snapcraftctl set-source`?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
12
Complexity:
58
Confidence:
81
Actionability:
66
|
needs triage | Dynamic override-pull builds cannot omit source because validation still requires it, while a dummy source triggers source-type detection failure. This old, unlabelled report needs reproduction against the current lifecycle. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
8
Complexity:
65
Confidence:
75
Actionability:
62
|
needs triage | Missing source validation prevents override-pull recipes from downloading dynamic release URLs. The report has no maintainer triage; current craft-parts supports a null source but lacks set-source. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18
Staleness:
95
Complexity:
55
Confidence:
55
Support Request:
15
|
needs triage | Snapcraft rejects snapcraft.yaml when a part omits `source` because the URL is resolved at runtime in an override-pull scriptlet; reporter suggests deferring the check or adding snapcraftctl set-source. No labels, no comments, no maintainer activity for ~7.4 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
99
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Unresolved bug report regarding Snapcraft's source property validation in override-pull scriptlets. Issue remains completely inactive with zero maintainer feedback for over seven years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
10
|
close stale | Snapcraft requires a static source property even when the URL is dynamically determined in override-pull. The report is 7+ years old with no maintainer interaction or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
80
Support Request:
25
|
close stale | Snapcraft validation fails when source URL is dynamically determined in override-pull. Open for over 7 years with no maintainer response, labels, or assignee. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.