snapcraft points to wrong entry in apps as being invalid.
Metadata
Current evaluation
Snapcraft 6.1 validation error misreports the first app ('runtests') as invalid when the actual offending app name ('get_cache_info', with an underscore) is the real problem. No maintainer interaction; zero comments; ~4 years old.
Suggested action: keep open
Reason: The issue is a genuine bug in error-message reporting (validation flags the wrong app name), not a support request — the reporter correctly identified that 'get_cache_info' (underscore) is the invalid name, not 'runtests'. It has zero comments and no maintainer interaction in ~4 years, but there is no evidence it has been fixed, and two closely related Launchpad bugs (1996525, 1851003) describe the same misreporting behavior and remain open. Closing as stale would be premature without confirmation the fix landed; it needs triage to confirm whether current snapcraft still exhibits this.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
17.5
Staleness:
95
Complexity:
30
Confidence:
70
Support Request:
20
|
keep open | Snapcraft 6.1 validation error misreports the first app ('runtests') as invalid when the actual offending app name ('get_cache_info', with an underscore) is the real problem. No maintainer interaction; zero comments; ~4 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
30
|
close stale | snapcraft 6.1 incorrectly reports 'runtests' as an invalid app name in snapcraft.yaml. The report lacks maintainer interaction, has no comments, and is over 3.5 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
0
|
close stale | snapcraft v6.1 incorrectly flags 'runtests' as an invalid app name instead of 'get_cache_info'. No maintainer interaction in over 3.9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
0
|
needs triage | Snapcraft v6.1 validation incorrectly flags valid app names as invalid while ignoring actually invalid ones. Issue remains unassessed by maintainers with zero comments after nearly four years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
85
Support Request:
40
|
close stale | snapcraft misreports validation errors for app names, flagging valid entries as invalid while ignoring actually invalid ones. The error message does not match schema rules. Open, zero comments, awaiting triage. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft (launchpad)#1996525
(confidence 75%)
Same misreporting behavior: misformatted app name flags the first app instead of the actual offending entry; reported on snapcraft 7.2.7, still open.
-
Duplicate Of:
snapcraft (launchpad)#1851003
(confidence 70%)
Same root cause: validation reports the first app name instead of the actual invalid app in multi-app configurations; open with zero maintainer interaction.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1996525 inaccurate error for a misformatted app name | snapcraft (launchpad) | open | Snapcraft reports error on wrong app when a misformatted app name uses underscore instead of hyphen. Issue is 1389 days old with no maintainer engagement or labels. | |
| #1851003 Error message displays name of first application when a secondary application fails name validation | snapcraft (launchpad) | open | Snapcraft schema validation names the first app instead of the actually invalid app when a secondary app name fails validation. Open ~6.8 years, no labels, zero maintainer interaction, no fix; a similar report (LP 1996525) is also open. | |
| #1919397 snapcraft doesn't run store checks locally, causing disappointment at upload time | snapcraft (launchpad) | open | Snapcraft should run store validation checks locally (e.g. external symlinks) before upload. Issue is 5+ years old with no comments; a snapcraft lint command was later added, but no evidence it covers this specific check. | |
| #1710254 snapcraft doesn't fail if the command exists in the host but not in the prime directory | snapcraft (launchpad) | closed | Bug report stating snapcraft incorrectly validates app commands during the prime step by checking the host system. The issue was closed with zero comments and no fix, indicating it was abandoned or marked stale. | |
| #1583236 snapcraft APT sources checking too strict | snapcraft (launchpad) | open | snapcraft fails builds when APT exits nonzero for non-critical warnings (e.g., outdated hash functions, unsupported PPAs). Unlabelled, zero comments, no maintainer interaction; references obsolete 2015-era sources. |