craft-archives does not remove managed repositories that are no longer in the craft.yaml file
Metadata
Current evaluation
Confirmed bug: repositories installed by craft-archives remain configured after removal from craft.yaml; the repro is clear, but safe package rollback and cleanup behavior remain unresolved.
Suggested action: keep open
Reason: The maintainer-authored bug has a clear two-pack PPA reproducer, and the current installer processes only repositories supplied by the latest run, installing sources, keys, and preferences without corresponding removal logic. The maintainer explicitly identifies package rollback as the hard unresolved part and recommends cleaning the environment, so the bug is valid but requires design work rather than closure.
Evaluated by: mr-cal-bot
Impact:
58
Quick Win:
8
Complexity:
80
Confidence:
93
Actionability:
69
Issue body
### Bug Description
If you remove a craft-archives managed repository from your *craft.yaml file, it doesn't remove it from the managed system.
The hard part of solving this is figuring out which packages to return to their previous versions, so the best solution right now is to just clean the environment instead.
### To Reproduce
1. Run a pack with the YAML below.
2. Comment out the repositories
3. Run a pack again, and note that the repository is still there.
### part yaml
```shell
package-repositories:
- type: apt
ppa: snappy-devs/snapcraft-daily
```
### Relevant log output
```shell
n/a
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
8
Complexity:
80
Confidence:
93
Actionability:
69
|
keep open | Confirmed bug: repositories installed by craft-archives remain configured after removal from craft.yaml; the repro is clear, but safe package rollback and cleanup behavior remain unresolved. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
17
Complexity:
60
Confidence:
70
Actionability:
60
|
keep open | craft-archives does not remove managed repositories that are no longer in the craft.yaml file. Issue is open with no maintainer response after 305 days. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
12
Staleness:
65
Complexity:
70
Confidence:
75
Support Request:
5
|
needs triage | craft-archives leaves apt sources and keyrings installed when a package-repository is removed from craft.yaml; no removal logic exists in installer.py. Open 285 days, zero comments, no maintainer acknowledgement, though labelled Type: Bug. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
60
Confidence:
80
Support Request:
10
|
needs triage | Bug where removing a craft-archives repository from craft.yaml leaves it installed on the system. No maintainer response or activity for 244 days. Requires assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
65
Confidence:
85
Support Request:
0
|
needs triage | Bug where removing a managed repository from craft.yaml leaves it in the system. Reported by maintainer 231 days ago with no team response. Suggests environment cleanup as a workaround. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.