apt package cache marks packages that don't exist
Metadata
Current evaluation
Apt stage-package marking could falsely report a valid architecture-qualified package as missing. Fixes from PRs #1446 and #1468 are now in the codebase.
Suggested action: close resolved
Reason: mr-cal stated on 2026-02-10 that #1446 could solve this; merged commit cf118b5f is in HEAD and changes AptCache.mark_packages to resolve all candidates before marking dependencies, the path that raised PackageNotFound. Commit c2836c97 (#1468) also refreshes apt before marking, although the lack of a reliable reproducer leaves some residual uncertainty.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
23
Complexity:
34
Confidence:
86
Actionability:
76
|
close resolved | Apt stage-package marking could falsely report a valid architecture-qualified package as missing. Fixes from PRs #1446 and #1468 are now in the codebase. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
25
Complexity:
40
Confidence:
80
Actionability:
60
|
close resolved | craft-parts marks packages to install then fails to find them due to apt cache or python-apt usage issues. Maintainer suggests PR #1446 may have resolved it. | |
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
22
Staleness:
40
Complexity:
55
Confidence:
60
Support Request:
10
|
keep open | craft-parts marks a stage-package then fails with PackageNotFound, suspected stale apt cache or python-apt misuse; unreproducible. Maintainer noted in Feb 2026 it could be solved by PR #1446 (merged two-pass mark_packages fix). | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
45
Confidence:
75
Support Request:
5
|
needs triage | craft-parts marks non-existent packages for installation, triggering a PackageNotFound error. Open for over two years with no labels or maintainer triage, awaiting review. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
45
Confidence:
85
Support Request:
10
|
needs triage | Bug where apt cache marks non-existent packages causing fetch failures. Unlabelled and awaiting maintainer triage despite recent author comment referencing a potential fix. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-parts#1446
(confidence 90%)
Merged commit cf118b5f introduces two-pass candidate resolution in AptCache.mark_packages, directly affecting the reported failure path.
-
Likely Fixed By:
craft-parts#1468
(confidence 76%)
Commit c2836c97 refreshes the apt package list before marking stage packages, addressing the stale-cache hypothesis.
Related issues
No related issues found above the similarity threshold.