← Back to issue list

snapcraft use cached packages across VMs

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1869544
Type
issue
State
open
Author
~keshavnrj
Labels
Created
Updated
Closed

Current evaluation

Feature request to cache apt packages centrally across snapcraft build VMs so they survive `snapcraft clean`. No labels or comments in 6+ years; premise tied to outdated-version Launchpad bug 1869542.

Suggested action: close stale

Reason: The issue has had zero comments, no labels, and no maintainer interaction for over 6 years, and its specific trigger — Launchpad bug 1869542 forcing `snapcraft clean` — is documented as an outdated-version bug unaddressed for over six years, so the concrete problem it describes is no longer applicable to current snapcraft. Confidence is moderate because the repo tools could not pin a snapcraft SHA, so I could not verify whether a cross-VM package cache was since implemented.

Impact: 35 Quick Win: 14.0 Staleness: 90 Complexity: 60 Confidence: 55 Support Request: 30

Issue body

snapcraft not using a central store to cache packages when building inside VMs. Which requires downloading same package again and again to build snaps. This particularly happen when this bug(https://bugs.launchpad.net/snapcraft/+bug/1869542) of snapcraft is triggered and there is no way to pass through it without using `snapcraft clean` command (which will delete the VM). This clears up the complete VM and forgets all downloaded packages by apt.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 14.0
Staleness: 90
Complexity: 60
Confidence: 55
Support Request: 30
close stale Feature request to cache apt packages centrally across snapcraft build VMs so they survive `snapcraft clean`. No labels or comments in 6+ years; premise tied to outdated-version Launchpad bug 1869542.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 45
Confidence: 85
Support Request: 15
close stale Feature request to enable package caching across VMs in snapcraft builds to prevent redundant downloads. Unanswered and inactive for over six years.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 35
Confidence: 92
Support Request: 10
close stale Feature request to cache packages across VMs to avoid repeated downloads during snap builds. Inactive for over 6 years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 60
Confidence: 85
Support Request: 10
close stale Feature request to implement central package caching across VMs in Snapcraft to prevent repeated downloads during builds. Currently unlabelled and inactive for over six years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 55
Confidence: 85
Support Request: 20
close stale Snapcraft fails to cache packages across VMs, causing redundant downloads when builds fail or snapcraft clean wipes the environment. Open with zero comments and 52 days of inactivity, awaiting triage.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1869542 (confidence 80%)

    Explicitly linked in the issue body as the bug that forces `snapcraft clean` and wipes the VM's apt cache; corpus notes it is unaddressed on an outdated version.

Related issues

Issue Project State Summary Similarity
#1841618 snapcraft should run apt-get update snapcraft (launchpad) open Feature request (2019) for snapcraft to refresh stale apt-get caches in process containers to avoid build failures. Open ~7 years with zero comments, no labels, no maintainer response; no general cache-refresh logic found in the build path.
77%
#4713 Shared caches for deb and snap packages snapcraft open Feature request to add a shared cache for deb/snap packages (like Charmcraft's python cache) to avoid re-downloading artifacts across pack/clean/pack cycles. Open since 2022, last activity 536 days ago, no labels, only a bot Jira-sync comment.
74%
#1626766 Make snapcraft work with ccache snapcraft (launchpad) open Request that snapcraft automatically pick up a host-configured ccache (via $PATH) when compiling parts. Very old (filed ~10 years ago, last activity ~7 years ago), no labels, no maintainer response, and the premise is outdated: modern snapcraft builds run in a confined core20/core22 base where the host PATH/ccache is not inherited.
71%