SNAPCRAFT_BUILD_ENVIRONMENT_* change doesn't apply to existing VMs
Metadata
Current evaluation
Closed by maintainer sergiusens (2019-04-17) as intended behaviour: SNAPCRAFT_BUILD_ENVIRONMENT_* are development/debugging-only variables, so no change was made to apply them to an existing Multipass VM.
Resolution: closed not a bug
Reason: Maintainer ~sergiusens closed the report on 2019-04-17 stating the SNAPCRAFT_BUILD_ENVIRONMENT_ variables 'should only be used for development and debugging', so failure to reconfigure an already-provisioned Multipass VM is working as designed. No code change or resolving PR was made; the whole lifecycle/multipass build environment (including the dup bug #1814729) was later removed from Snapcraft.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed by maintainer sergiusens (2019-04-17) as intended behaviour: SNAPCRAFT_BUILD_ENVIRONMENT_* are development/debugging-only variables, so no change was made to apply them to an existing Multipass VM. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed by maintainer sergiusens (2019-04-17) as intended behaviour: SNAPCRAFT_BUILD_ENVIRONMENT_* are development/debugging-only vars, so no fix to apply them to existing Multipass VMs was made. | |
| stealth/space-bunny-alpha | — | closed stale | Closed with no recorded fix, explanation, or recent activity. Launchpad bug #1814729 separately tracks the same issue with Multipass CPU and memory settings. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix or resolution. The report noted SNAPCRAFT_BUILD_ENVIRONMENT_* changes fail to apply to existing VMs. With zero comments and no linked pull request, it appears abandoned or closed as stale. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. SNAPCRAFT_BUILD_ENVIRONMENT_* changes failing to apply to existing VMs were left unaddressed with zero comments, indicating the report was abandoned or marked stale. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution due to inactivity. SNAPCRAFT_BUILD_ENVIRONMENT_* changes failing to apply to existing VMs remain unaddressed. No fix or workaround was implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution, likely abandoned. SNAPCRAFT_BUILD_ENVIRONMENT_* changes do not apply to existing VMs, requiring recreation or dynamic updates. No fix or workaround was implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
snapcraft (launchpad)#1814729
(confidence 80%)
Same underlying behaviour: SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY/CPU ignored when an existing Multipass VM is reused; maintainer confirmed vars apply only at VM creation and advised purging the instance. Still open.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1814729 Setting SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY doesn't take effect | snapcraft (launchpad) | open | Feature request: SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY/CPU are ignored when an existing Multipass VM is reused; maintainer confirmed the vars only apply at VM creation and advised purging the instance. Not implemented | |
| #6025 Snapcraft ignores SNAPCRAFT_BUILD_ENVIRONMENT_* environment variables on MacOS | snapcraft | open | Documented SNAPCRAFT_BUILD_ENVIRONMENT_CPU/MEMORY are ignored on macOS; maintainer confirms Multipass CPU/memory hardcoded and points to upstream craft-providers#531. Docs still promise the vars work. | |
| #1809068 SNAPCRAFT_ environment variables not exposed to version-script | snapcraft (launchpad) | closed | Closed after maintainers directed users from version-script to snapcraftctl set-version; no fix was cited for the missing SNAPCRAFT_* variables. | |
| #4307 SNAPCRAFT_BUILD_ENVIRONMENT apparently takes precedence over "--use-lxd" | snapcraft | closed | Fixed by merged PR #4329 (commit 7f8d4cff9): --use-lxd now overrides SNAPCRAFT_BUILD_ENVIRONMENT, matching documented precedence. |