snapcraft should run apt-get update
Metadata
Current evaluation
2018 request for snapcraft to run apt-get update when apt caches are stale in process containers. Untouched since filing (no comments/labels); the process-container build model and in-tree apt handling have since been removed upstream.
Suggested action: close stale
Reason: The exact subsystem the report targets no longer exists: grepping the current tree for "process container", "multipass" and "lxd" returns zero matches, and the old provider lifecycle was replaced by commit 929a26fd6 ("providers: install snaps and packages via craft-providers API"), leaving only services/provider.py. Apt sources/keyring management now lives in craft-archives, and AGENTS.md states "Fixes or features that are generic or would benefit other craft apps must be made in the correct craft library", so the requested change is not implementable in this repo. The issue is also entirely untriaged (0 comments, no labels, no assignee) with only dead external references (Cirrus task 4766182000820224, apt bugs #1429285/#1709603) and no logs or reproducer. Closing as stale/obsolete rather than valid-but-open; confidence is moderate rather than high because no resolving commit directly implements the request.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
3
Complexity:
55
Confidence:
72
Actionability:
25
|
close stale | 2018 request for snapcraft to run apt-get update when apt caches are stale in process containers. Untouched since filing (no comments/labels); the process-container build model and in-tree apt handling have since been removed upstream. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
12
Complexity:
18
Confidence:
82
Actionability:
35
|
needs triage | APT refresh appears implemented in craft-parts, but the stale process-container report lacks logs or a reproducible test to confirm whether its path is fixed. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
12
Complexity:
35
Confidence:
47
Actionability:
40
|
needs triage | Stale apt-get caches could make Snapcraft builds fail in process containers; proposes refreshing old caches, with no maintainer discussion or resolution recorded. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
19
Staleness:
95
Complexity:
45
Confidence:
60
Support Request:
15
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Request to automatically update apt-get caches in snapcraft to prevent build failures in process containers. Issue is over six years old with no maintainer response or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Requests automatic apt cache updates to prevent failures in containerized builds. Unlabeled, unassigned, and inactive for nearly 7 years with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Feature request for snapcraft to automatically update apt caches in containers to prevent stale cache failures. Unaddressed for nearly 7 years with no maintainer interaction or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1583236
(confidence 45%)
Titled "snapcraft APT sources checking too strict" — same area of apt source/cache handling, though I could not retrieve its body to confirm overlap.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1583236 snapcraft APT sources checking too strict | snapcraft (launchpad) | open | Snapcraft still turns any apt-get update failure into a package-list refresh error; this old report needs a modern reproducer and a policy for distinguishing harmless source failures. |