Removing a `package-repositories:` entry does not affect existing containers
Metadata
Current evaluation
Removing a package-repositories entry leaves its APT source in reused build containers, risking unintended package resolution. The report remains open, untriaged, and uncommented; no resolving change was found.
Suggested action: needs triage
Reason: The Launchpad record is open with no labels, maintainer comments, or other indication of triage. The add-build-remove sequence is a concrete reproducer, and the current Craft Archives AptSourcesManager only installs or updates sources without a stale-source removal path, but affected versions and the expected cleanup scope are unspecified.
Evaluated by: mr-cal-bot
Impact:
57
Quick Win:
17
Complexity:
56
Confidence:
84
Actionability:
69
Issue body
If you have an entry in `package-repositories:`, build, then remove it, it's not removed from the container.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
57
Quick Win:
17
Complexity:
56
Confidence:
84
Actionability:
69
|
needs triage | Removing a package-repositories entry leaves its APT source in reused build containers, risking unintended package resolution. The report remains open, untriaged, and uncommented; no resolving change was found. | |
| stealth/space-bunny-alpha |
Impact:
44
Quick Win:
11
Complexity:
60
Confidence:
87
Actionability:
65
|
needs triage | Removing a package-repositories entry leaves the APT source configured in existing build containers; the report is unlabelled, untriaged, and inactive since submission. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
10
Complexity:
58
Confidence:
87
Actionability:
66
|
needs triage | Removed package-repositories entries remain in reused build containers; current code skips repository management entirely when the list is empty. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
11
Complexity:
58
Confidence:
89
Actionability:
57
|
needs triage | Removing a package-repositories entry leaves APT configuration in reused build containers; current code skips cleanup for an empty list, but the old report remains unlabelled and untriaged. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
11
Complexity:
55
Confidence:
87
Actionability:
52
|
needs triage | Removing a package-repositories entry is reported to leave the repository in existing containers; the unlabelled issue has no maintainer response or confirmed resolution. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
55
Quick Win:
30
Staleness:
95
Complexity:
45
Confidence:
40
Support Request:
15
|
needs triage | Removing a package-repositories entry from configuration does not remove it from existing containers. Unlabelled, no maintainer response, 1361 days old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Bug report stating that removing a package-repositories entry does not remove it from existing containers. The issue is 3.6 years old, has no comments, labels, or maintainer engagement, and remains untriaged. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
10
|
close stale | Reports that removing a package-repositories config entry does not remove it from existing containers. Unlabelled, zero comments, inactive for over 3.5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | Removing a package-repositories config entry does not remove corresponding packages from existing containers. Currently unassessed with no maintainer interaction for over 3.5 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.