← Back to issue list

locally built snapcraft switches channels in the container

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1884576
Type
issue
State
closed
Author
~ken-vandine
Labels
—
Created
Updated
Closed

Current evaluation

Locally built Snapcraft was forced onto latest/candidate inside LXD build containers, hiding untested changes. Fixed by merged PR snapcore/snapcraft#3184 (commit 2616ab456), which checks the installed revision before providers switch channels.

Resolution: closed resolved

Reason: Maintainer ~sergiusens linked snapcore/snapcraft#3184, which was merged as commit 2616ab456 ("build providers: check revision before switching"). It adds a revision check before build providers change the Snapcraft channel, so locally built snaps are preserved in the LXD container.

Evaluated by: mr-cal-bot

No scores available.

Issue body

After building a snap of snapcraft locally and installing it on my host. I get this when building something using lxd: snapcraft 4.0.6+git5.gd7594dd1 installed "snapcraft" switched to the "latest/candidate" channel So my snapcraft change I'm attempting to test is not available in the container.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Locally built Snapcraft was forced onto latest/candidate inside LXD build containers, hiding untested changes. Fixed by merged PR snapcore/snapcraft#3184 (commit 2616ab456), which checks the installed revision before providers switch channels.
stealth/space-bunny-alpha — closed resolved Fixed by merged PR #3184 (commit 2616ab456), which checks the installed revision before build providers switch Snapcraft channels, preserving local builds for LXD.
stealth/space-bunny-alpha — closed resolved Fixed by merged PR snapcore/snapcraft#3184 (commit 2616ab456), which checks the installed revision before build providers switch Snapcraft channels.
stealth/space-bunny-alpha — closed resolved LXD refresh handling was fixed by canonical/snapcraft#2098 (7666a74a7), waiting for active refreshes to avoid unexpected channel switches on locally installed snaps.
qwen/qwen3.6-35b-a3b — — Closed without resolution. Locally built snapcraft switches to the latest/candidate channel inside LXD containers, blocking local change testing. No fix or action was taken.
qwen/qwen3.6-35b-a3b — — Closed without comments or resolution, likely abandoned. The reporter noted that locally built snapcraft switched to the latest/candidate channel inside an LXD container, preventing local changes from being available for testing.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The issue reported locally built snapcraft switching to the latest/candidate channel inside LXD containers, blocking local change testing. Likely abandoned or resolved in subsequent releases.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution, likely abandoned. Locally built snapcraft incorrectly switched to the latest/candidate channel inside LXD containers, blocking local change testing. No comments or fixes were provided.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#3184 (confidence 97%)

    Merged PR cited by the maintainer in the sole comment; merged as commit 2616ab456.

Related issues

Issue Project State Summary Similarity
#3146 build providers: snap sw to channels if injecting snapcraft merged Merged PR #3146 as commit c15f0623d, preventing revision-asserted injected snaps from being switched to latest/stable and preserving their intended tracking channels.
72%