← Back to issue list

Incompatible base detection is too strict for non-Ubuntu bases

View original Github issue

Metadata

Project
craft-application
Number
#455
Type
issue
State
open
Author
lengau
Labels
Created
2024-09-11 14:45:04+00:00
Updated
2025-05-23 17:26:58+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

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

No evaluation history available.