← Back to issue list

Not possible to close a channel for only a specific architecture

View original Launchpad issue

Metadata

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

Current evaluation

Request to close a snap channel for a specific architecture only (e.g. undo accidental stable release on arm64). Open ~8.5 years, zero comments, no labels, no maintainer engagement. Related Launchpad bug #1732501 still open.

Suggested action: needs triage

Reason: No maintainer has ever responded, labelled, or assigned this issue (0 comments, no labels, 3106 days old). The related Launchpad bug #1732501 is also open with zero engagement. The underlying need (per-arch channel close) is a legitimate feature gap — snapcraft close only operates on the local arch — but it has never been triaged. Cannot close as stale since the problem is likely still reproducible and no fix has landed; needs a maintainer to decide whether to implement or document a workaround.

Impact: 30 Quick Win: 18.0 Staleness: 90 Complexity: 40 Confidence: 65 Support Request: 15

Issue body

Build a snap and accidentally release it to the stable channel on an architecture other than the one your primary workstation runs. (e.g. workstation is amd64, you published arm64). There seems to be no straightforward way to close a channel. "snapcraft close snapname" works fine for your workstation arch, but no good for closing the accidental release to stable on arm64. How is a developer supposed to undo these kinds of mistakes?

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 90
Complexity: 40
Confidence: 65
Support Request: 15
needs triage Request to close a snap channel for a specific architecture only (e.g. undo accidental stable release on arm64). Open ~8.5 years, zero comments, no labels, no maintainer engagement. Related Launchpad bug #1732501 still open.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 85
Support Request: 10
close stale Reports missing CLI functionality to close a specific architecture channel in snapcraft. Unaddressed for over 8 years with no comments or maintainer interaction.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 75
close stale Reports inability to close a snap channel for a specific architecture using snapcraft, asking how to revert an accidental release. The issue has no comments, labels, or maintainer interaction for over 8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 60
Support Request: 40
close stale Reporter cannot close a snap channel for a specific architecture using snapcraft CLI. Issue is over 8 years old with no maintainer response or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 25
Confidence: 85
Support Request: 60
close stale Snapcraft cannot close a channel for a specific architecture, preventing developers from undoing accidental multi-arch releases. The issue remains open with zero comments and years of inactivity, awaiting triage.

Update history

No update history recorded yet.

Related work

  • Duplicate Of: snapcraft (launchpad)#1732501 (confidence 85%)

    Identical title and scope: 'it's not possible to close a channel for only one architecture'. Both open, both unaddressed.

Related issues

Issue Project State Summary Similarity
#1732501 it's not possible to close a channel for only one architecture snapcraft (launchpad) open Feature request: snapcraft close command lacks an architecture argument, so closing a channel affects all architectures. No maintainer response, no labels, no comments. Related Launchpad bug #1752459 also open with no activity.
86%