Exception raised when trying to operate on a snap that I don't own nor collaborate with
Metadata
Current evaluation
Ugly traceback (KeyError in StoreReleaseError.__str__) when snapcraft release fails due to missing package_upload permission on a snap the user does not own; reported against snapcraft 2.35, no maintainer activity in ~8.6 years.
Suggested action: close stale
Reason: The issue targets snapcraft 2.35 code paths (snapcraft/storeapi/, snapcraft/_store.py, snapcraft/cli/store.py) that no longer exist in the current codebase, which uses a completely rewritten snapcraft/store/ client. The affected version is long unsupported, the issue has zero comments or labels, and a near-identical report (LP #1761488, same 'StoreReleaseError: <exception str() failed>' in 2.39.2) was closed without resolution.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
15.0
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
10
|
close stale | Ugly traceback (KeyError in StoreReleaseError.__str__) when snapcraft release fails due to missing package_upload permission on a snap the user does not own; reported against snapcraft 2.35, no maintainer activity in ~8.6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Snapcraft crashes with an unhandled KeyError when releasing a snap without upload permissions, instead of showing a clear 403 error message. Untriaged and inactive for over 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Unhandled KeyError when running snapcraft release on a snap without permissions, causing a traceback instead of a user-friendly message. Issue is over 8 years old with no activity or maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Unhandled KeyError when formatting a 403 permission error during snap release. Reported 8.5 years ago for deprecated snapcraft 2.35 with no maintainer activity or labels. | |
| qwen3.6-35b-moe-q4 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Unhandled KeyError when running snapcraft release on a snap without permissions, causing ugly stack traces. Issue is completely inactive for over 8 years on a legacy version. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft#1761488
(confidence 55%)
LP bug 1761488 reports the identical 'StoreReleaseError: <exception str() failed>' during snapcraft release in 2.39.2; closed without resolution. Ref is a LaunchPad bug ID, not a GitHub issue, hence lower confidence.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1947067 Getting error trying to release a snap | snapcraft (launchpad) | open | User reports 'You do not have permissions to modify this Snap' error when releasing a snap, despite having been granted permission. No labels, no comments, no activity for ~5 years. Store-side permission issue, not a snapcraft bug. | |
| #1761488 snapcraft 2.39.2 failed to release a snap: snapcraft.storeapi.errors.StoreReleaseError: <exception str() failed> | snapcraft (launchpad) | closed | Closed without resolution. The report details a StoreReleaseError during snapcraft 2.39.2 release attempts. With zero maintainer comments and significant age, the issue was likely abandoned. No fix or workaround was provided. |