apt update failure during core22 destructive-mode pulls
Metadata
Current evaluation
Core22 snapcraft pull --destructive-mode reportedly fails apt update for stage-packages when run non-root; --bind-ssh does not help. The report remains open, untriaged, and without maintainer feedback.
Suggested action: needs triage
Reason: The report identifies Snapcraft 7.3.1, a core22 snap with stage-packages, the destructive-mode pull command, and an external failure log, making it plausible but requiring root-cause investigation. There are no labels or maintainer comments, and current documentation says core22 and later destructive-mode builds require root, so maintainers must determine whether non-root operation is an intended requirement or a regression.
Evaluated by: mr-cal-bot
Impact:
48
Quick Win:
11
Complexity:
65
Confidence:
64
Actionability:
68
Issue body
Example logs https://paste.ubuntu.com/p/P9rFM6rR6T/ for a core22 based snap with a part that contains stage-packages.
This seems like a regression from core20 based destructive mode builds, where it was possible to run snapcraft as non-root user without running into permission errors during apt update.
Running `snapcraft pull --destructive-mode ...` with sudo is problematic because of lack of regular user's ssh keys/config, and `--bind-ssh` does not seem to be doing anything during destructive mode builds.
$ snap list snapcraft
Name Version Rev Tracking Publisher Notes
snapcraft 7.3.1 8931 latest/stable canonical✓ classic
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
11
Complexity:
65
Confidence:
64
Actionability:
68
|
needs triage | Core22 snapcraft pull --destructive-mode reportedly fails apt update for stage-packages when run non-root; --bind-ssh does not help. The report remains open, untriaged, and without maintainer feedback. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
11
Complexity:
58
Confidence:
84
Actionability:
65
|
needs triage | Core22 destructive-mode pulls with stage-packages reportedly hit apt permission errors, forcing sudo despite core20 working; no triage or follow-up after the initial report. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
28
Staleness:
95
Complexity:
45
Confidence:
60
Support Request:
20
|
needs triage | apt update fails during core22 destructive-mode pulls for non-root users, reported as regression from core20. No maintainer response or labels after 1226 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
20
|
close stale | Reported apt update permission regression in snapcraft destructive mode for core22. No maintainer response in over 3 years. Core22 is deprecated and snapcraft has evolved significantly. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
80
Support Request:
10
|
close stale | Regression in snapcraft causing apt update failures during core22 destructive-mode builds for non-root users. Unaddressed for over three years with zero maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
80
Support Request:
55
|
close stale | Reports apt update permission failures during core22 destructive-mode snapcraft pulls. Described as a regression from core20, but has seen no maintainer activity or follow-up in over three years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.