Incompatible base detection is too strict for non-Ubuntu bases
Metadata
Current evaluation
Closed without a code fix after being deferred to internal CRAFT-3374; exact-name base validation remained unresolved.
Resolution: closed stale
Reason: The repository issue record says the item was closed without a code fix and only deferred to internal CRAFT-3374; no resolving PR or commit was identified. Its only visible comment is an automated Jira-sync notice.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
[_validate_build_plan](https://github.com/canonical/craft-application/blob/2bda2579de8a4f5733486914cd4d9c9383fbcb3e/craft_application/services/lifecycle.py#L422-L440) requires the base to be *exactly* the same, not just the same major version. While this is fine for Ubuntu, for bases like Debian and Almalinux this results in errors like:
2024-08-23 22:30:02.737 Almalinux 9 builds cannot be performed on this Almalinux 9.4 system.
### To Reproduce
See: https://github.com/canonical/charmcraft/actions/runs/10532931826/job/29188508635?pr=1824
### part yaml
```shell
n/a
```
### Relevant log output
```shell
2024-08-23 22:30:02.732 Initialising lifecycle manager in /root
2024-08-23 22:30:02.733 Project vars: {'version': 'unversioned'}
2024-08-23 22:30:02.733 Adopting part: None
2024-08-23 22:30:02.734 Using parallel build count of 1 from CPU count
2024-08-23 22:30:02.735 Called not implemented method 'YUMRepository.configure' with name 'charmcraft'
2024-08-23 22:30:02.737 Almalinux 9 builds cannot be performed on this Almalinux 9.4 system.
2024-08-23 22:30:02.737 Detailed information: Builds must be performed on a specific system to ensure that the final artefact's binaries are compatible with the intended execution environment.
2024-08-23 22:30:02.738 Recommended resolution: Run a managed build, or run on a compatible host.
2024-08-23 22:30:02.995 Emitter: Resuming control of the terminal
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed without a code fix after being deferred to internal CRAFT-3374; exact-name base validation remained unresolved. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a code fix after deferral to internal CRAFT-3374; non-Ubuntu base detection remains unresolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and deferred to internal Jira ticket CRAFT-3374. No fix was merged. The strict base version matching for non-Ubuntu systems remains unresolved. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | Validation logic requires exact base version match instead of major version, causing build failures on non-Ubuntu bases like Almalinux 9.4. Unlabelled with no maintainer response since September 2024. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
30
Confidence:
70
Support Request:
10
|
needs triage | Base validation requires exact version match instead of major version, causing build failures on non-Ubuntu bases. Open and awaiting maintainer triage. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Related To:
canonical/charmcraft#1824
(confidence 90%)
The linked CI run documents the AlmaLinux 9 versus 9.4 mismatch but did not resolve craft-application#455.
Related issues
No related issues found above the similarity threshold.