Trying to register a snap already reserved doesn't explain the error cause
Metadata
Current evaluation
Fixed by snapcore/snapcraft#629, merged as commit 250a350b9, adding a clearer message when registering a reserved snap name.
Resolution: closed resolved
Reason: The linked PR #629 was merged as commit 250a350b9, titled “Proper message when registering a reserved snap,” directly implementing the requested error explanation.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When I try to register a snap that is reserved previously, an error is returned:
Registration failed.
This error should explain that the name is already registered by the user and snaps of that name can just be uploaded.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by snapcore/snapcraft#629, merged as commit 250a350b9, adding a clearer message when registering a reserved snap name. | |
| stealth/space-bunny-alpha | — | closed resolved | Registration errors now explain that a reserved snap name is already registered and can be uploaded directly; linked fix: snapcore/snapcraft#629. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #623 (commit fca736b61), which replaced the generic registration failure with a clearer message for an already-registered snap name. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The generic error for reserved snaps was not updated to clarify registration status. No fix or pull request was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Requesting a clearer error message for already-reserved snap names was closed without comments or resolution, indicating the enhancement was abandoned or addressed in a later release without tracking. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report requested clearer error messaging for already reserved snaps. With zero comments and no code changes, the issue was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#629
(confidence 99%)
The issue’s sole maintainer comment links PR #629, whose resolving commit is 250a350b9.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1596782 Trying to register a snap already registered doesn't explain the error cause | snapcraft (launchpad) | closed | Added a clearer error for duplicate snap registration in snapcore/snapcraft PR #623, commit fca736b61. | |
| #1602791 Error when trying to register a reserved name is missing a sentence | snapcraft (launchpad) | closed | Fixed in canonical/snapcraft#629 via commit 250a350b9, which completed the reserved-name registration error guidance. | |
| #629 Proper message when registering an already registered snap | snapcraft | merged | Merged as commit 250a350b9, adding clearer handling and dispute guidance for registering a reserved snap name after the already-registered-name fix in #623. | |
| #1598939 registering too many snaps in a short time period fails without a proper error | snapcraft (launchpad) | closed | Fixed by merged snapcore/snapcraft#630 (commit 1a5ff1f98), adding a clear error when snap registration is attempted too quickly. | |
| #1644673 Trying to register a snap name with reserved characters fails opaquely | snapcraft (launchpad) | closed | Invalid snap names now produce a detailed allowed-character error. The handling landed in PR #1247 (03105a6c4), and Snapcraft v2.34 was confirmed to display it. | |
| #1778 Add sentences to error when registering name | snapcraft | merged | Merged as snapcraft/snapcraft#1778 (commit 881a79405): extends the reserved-name registration error with extra guidance and 'choose a different name', addressing LP bug #1602791. | |
| #623 Proper message when registering an already registered snap | snapcraft | merged | Merged PR #623 (commit fca736b61, LP #1596782) improving the error shown when registering an already-registered snap name, pointing at the name-dispute claim form. |