← Back to issue list

Snapcraft complains the missing `source` property when the source URL is determined in override-pull scriptlet

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1822727
Type
issue
State
open
Author
~brlin
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: needs triage

Reason: Zero comments, no labels, no assignee, and no maintainer interaction for ~2709 days — the issue has never been assessed. It is a real validation/UX bug (schema requires `source` even when override-pull fully determines the source), not a support question, so it should be triaged rather than auto-closed; however, its age and the project's major refactor to craft-parts/craft-application since 2017 mean the original code paths likely no longer exist, so a maintainer needs to verify whether it still reproduces before any fix or close.

Impact: 40 Quick Win: 18.0 Staleness: 95 Complexity: 55 Confidence: 55 Support Request: 15

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
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 100
Complexity: 25
Confidence: 95
Support Request: 10
close stale Snapcraft incorrectly requires a 'source' property when the URL is dynamically determined in an override-pull scriptlet. The report has been inactive for over seven years with no maintainer engagement or labels.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1600428 Setting source: .. causes pull to fail snapcraft (launchpad) closed Abandoned. Setting source: .. in snapcraft.yaml caused an infinite loop and file name too long error during pull. The bug was not fixed or addressed.
70%
#2015327 Files in path to snapcraft.yaml are excluded in source directive snapcraft (launchpad) open Bug report about files in the source path being excluded when using source: ../.. in snapcraft.yaml. Open for over 3 years with no activity or maintainer response.
70%