Open simonjwright opened 9 months ago
The different selected version likely comes from --select
attempting to find a gprbuild
compatible with the gnat
already selected. Was there one in your second run? --install
won't attempt to do that, so it will select the newest version, provided by the external one in that case.
As for the error, it should have been fixed after #1533. It is possible you have to invalidate the action caches in your org.
In the ubuntu-latest workflow of the Ada example in my fork of sdl2-examples, we’re seeing that
alr --non-interactive toolchain --install gprbuild
installs the external gprbuild gprbuild=2021.0.0+0778alr --non-interactive toolchain --select gprbuild
sets gprbuild-22.0.1 in the configurationThe workflow uses the
version: "nightly"
.The run above was today, and succeeded, but a similar run executed today in the repo of which mine is a fork failed with "ERROR: Requested tool configured as gprbuild=22.0.1 but not installed: gprbuild".
Would this problem go away if Alire didn’t choose the external gprbuild when a 'normal' (?) crate is available?