craft-archives does not remove managed repositories that are no longer in the craft.yaml file

Metadata

Project: craft-archives
Number: #217
Type: issue
State: open
Author: lengau
Labels: Type: Bug
Created: 2025-11-19 05:27 PM UTC
Updated: 2025-11-19 05:28 PM UTC
Closed: —

Current evaluation

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.

Suggested action: needs triage

Reason: Despite the 'Type: Bug' label, there are zero comments and no maintainer response in 285 days, so it has not been assessed or prioritized. I verified in current code that installer.py/_install_repos only adds sources, keys, and preferences — there is no uninstall/remove path — so the bug is still present and not stale. The reporter explicitly notes the hard part is deciding which packages to revert to previous versions, so it needs a maintainer design decision rather than a quick fix.

Impact: 40 Quick Win: 12.0 Staleness: 65 Complexity: 70 Confidence: 75 Support Request: 5

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
2026-09-01 04:26 AM UTC	qwen/qwen3.8-27b	Impact: 40 Quick Win: 12.0 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.
2026-07-22 12:16 PM UTC	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.
2026-07-09 12:53 AM UTC	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.
2026-06-17 09:58 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 75 Complexity: 60 Confidence: 70 Support Request: 5	keep open	Removing a craft-archives repository from craft.yaml leaves it installed in the managed system. Environment cleanup is recommended over package version reversion. Open, unassigned, awaiting implementation.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.