snapcraft can generage snaps with a name longer than 107 characters
Metadata
Current evaluation
Snapcraft only limits the generated snap file name, not the snap name itself, so it can build snaps whose names exceed the store's 107-character limit and fail at upload. Open since 2016, no labels or comments, untriaged.
Suggested action: needs triage
Reason: The issue has zero comments, no labels, and no maintainer response in ~10 years, so it has never been assessed, making needs_triage the correct default. It is not a candidate for close_stale because the underlying problem (store enforces a 107-char name limit that snapcraft doesn't validate) is likely still reproducible and the fix is a simple validation addition; it is a real bug/missing validation, not a support request. Confidence is moderate because code inspection tools were unavailable, so I could not verify whether name-length validation was added in a later version.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
18.75
Staleness:
90
Complexity:
25
Confidence:
60
Support Request:
10
|
needs triage | Snapcraft only limits the generated snap file name, not the snap name itself, so it can build snaps whose names exceed the store's 107-character limit and fail at upload. Open since 2016, no labels or comments, untriaged. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Snapcraft allows generating snap packages with names exceeding the 107-character limit enforced by the Snap Store, causing upload failures. The issue remains untriaged with no maintainer comments or labels after nearly 10 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Decade-old unaddressed request to enforce a 107-character limit on snap package names, matching Snap Store constraints. No maintainer response or reproduction details provided. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Snapcraft allows generating snap packages with names exceeding the Snap Store's 107-character limit, causing upload failures. The issue remains open with no maintainer interaction or labels after nearly a decade. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
90
Support Request:
5
|
close stale | snapcraft permits snap names over 107 characters, causing Snap Store upload failures. Validation only restricts generated filenames. Unassigned with no comments or recent activity, it requires triage to enforce the store limit on snap names. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft (launchpad)#1590620
(confidence 80%)
Identical title and content on Launchpad; same bug tracked in both places, still open and untriaged there.
-
Related To:
snapcraft (launchpad)#1634038
(confidence 60%)
Same theme: snapcraft should validate name/namespace constraints before upload to avoid post-build store rejections.
-
Related To:
snapcraft (launchpad)#1886223
(confidence 45%)
Also concerns snap naming guidance/standards in snapcraft, though a different specific problem.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1981205 Snapcraft produces too long instance name, instance launch fails | snapcraft (launchpad) | closed | Abandoned without resolution. Snapcraft generated LXC instance names exceeding the 63-character limit, causing launch failures. The suggested hashed naming approach was not implemented. | |
| #1693798 snapcraft builds a snap that won't install if + is in the name | snapcraft (launchpad) | closed | Fixed by enforcing strict snap name validation during the build process. Snapcraft now rejects names containing invalid characters like plus signs, preventing the generation of uninstalleable packages. | |
| #1777659 Snapcraft version string doesn't allow certain characters | snapcraft (launchpad) | open | Snapcraft rejects version strings containing underscores (e.g. '2018_931-01') even though the version field is described as 'just for humans'. No maintainer response, no labels, 0 comments, ~8 years old. |