Not possible to close a channel for only a specific architecture

Bug #1752459 reported by Alan Pope 🍺🐧🐱 πŸ¦„ on 2018-03-01
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Snap Store Server
Kyle Fazzari

Bug Description

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?

William Grant (wgrant) on 2018-05-09
affects: snapstore → snapcraft
Sergio Schvezov (sergiusens) wrote :

closing should be arch independent.

Changed in snapcraft:
milestone: none → 2.43
assignee: nobody → Kyle Fazzari (kyrofa)
importance: Undecided → High
status: New → Triaged
importance: High → Medium
Kyle Fazzari (kyrofa) wrote :

Whoa, it's not? No kidding, on it.

Kyle Fazzari (kyrofa) wrote :

Alan, I'm not seeing this behavior. The only information snapcraft sends to the store seems to be the channel, no arch-specific stuff. Also, I just tested closing on my amd64 machine, and it's closed on my arm64 machine as well. Can you verify this, and perhaps walk me through how to reproduce it?

Changed in snapcraft:
status: Triaged → Incomplete

That's exactly my point.

I want to close _only_ the arm64 stable channel.

Tell me how I do that. I can't.

I have to close _all_ architectures stable channel. Then re-release everything *except* the one I want to close.

Kyle Fazzari (kyrofa) wrote :

Ah! I definitely didn't read the bug report that way :) .

Looking at the store API docs[1], this doesn't look possible today. wgrant, can you verify?


Changed in snapcraft:
status: Incomplete → New
summary: - Not possible to close a channel
+ Not possible to close a channel for only a specific architecture
Changed in snapcraft:
milestone: 2.43 → none
status: New → Confirmed
Sergio Schvezov (sergiusens) wrote :

We will need to write a user story for this, I suspect this is more of an "unrelease" scenario than what we designed `close` for.

Bret Barker (noise) on 2018-12-17
Changed in snapstore:
importance: Undecided → Wishlist

Note: It seems you can workaround this by closing the channel and reopening it for only the architectures you want to keep.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers