build: only use python-apt-wheels repo for python-apt
Metadata
Current evaluation
Merged #5276 (d359fbf86), restricting python-apt-wheels to python-apt dependencies so unrelated package updates no longer use that repository.
Resolution: closed resolved
Reason: PR #5276 was approved and merged as commit d359fbf86. It scopes python-apt-wheels to python-apt, preventing unrelated dependency updates from resolving through that repository.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `make lint`?
- [x] Have you successfully run `make test`?
---
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #5276 (d359fbf86), restricting python-apt-wheels to python-apt dependencies so unrelated package updates no longer use that repository. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #5276 in d359fbf86, restricting the python-apt-wheels index to python-apt so unrelated builds no longer use that repository. | |
| stealth/space-bunny-alpha | — | closed resolved | PR #5276 (commit d359fbf86) merged into snapcraft, restricting the python-apt-wheels uv index to python-apt only via `explicit = true` in pyproject.toml. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #5276 (d359fbf86): builds now use python-apt-wheels only for python-apt, avoiding that repository for unrelated package updates. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged after two approvals and passing CI checks. The change restricts the build process to exclusively use the python-apt-wheels repository for python-apt, modifying a single file with four added lines. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a build configuration update restricting python-apt installation to the python-apt-wheels repository. The change passed automated lint and test checks and was integrated without additional review comments. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1022 build: only use python-apt-wheels repo for python-apt | craft-parts | merged | Merged in #1022 via commit 1d345d03, limiting the python-apt-wheels uv index to the python-apt dependency. | |
| #821 build: only use python-apt-wheels repo for python-apt | rockcraft | merged | Merged in canonical/rockcraft#821 (commit e6645a56), restricting python-apt-wheels lookups to python-apt updates rather than every package update. | |
| #659 build(deps): only use python-apt-wheels repo for python-apt | craft-application | merged | Merged PR #659 (commit 57808c5b) set the python-apt-wheels uv index to explicit = true and pinned it via [tool.uv.sources] to python-apt only, so uv stops querying that repo for every wheel. | |
| #2188 build: fix issue where python-apt-wheels repo was used for all packages | charmcraft | merged | Merged PR #2188 (commit 2ccd8f32) fixed package sourcing by restricting python-apt-wheels to python-apt instead of using it for every package. | |
| #1792 build: use python-apt wheels simple repository | craft-parts | merged | Merged PR #1792 updates pyproject.toml and uv.lock to source python-apt wheels from lengau.github.io instead of people.canonical.com. |