I’ve published a new release of the “mold_lib” crate (a month ago, or so), but the Alire Crate Status page has not been updated, yet. Do I have to configure anything in the alire.toml file, or during alr publish, to update it? How is that page updated?
There’s nothing you need to configure. It looks like the CI that builds the crate status pages is using an older version of Alire (version 2.0.2) which uses an older community index branch (stable-1.3.0). Since Alire 2.1.0 was released, new crates and updates are published to the most recent community index branch (stable-1.4.0), which is not picked up by the CI that builds those pages.
I’ve raised an issue to make the maintainers aware of the problem.
FYI this has been fixed now and the CI is gradually building all the updates to the various crates.
One thing I’ve noticed in the crates status is that GNAT FSF 15 doesn’t run on centos-9 since gprbuild 25 requires a newer glibc version (>= 2.35). This means that all crates seem to fail to build on centos-9 with GNAT FSF 15. The builds fail with an error message like:
/root/.local/share/alire/toolchains/gprbuild_25.0.1_9a2e6cfb/bin/gprbuild: /lib64/libc.so.6: version `GLIBC_2.35' not found (required by /root/.local/share/alire/toolchains/gprbuild_25.0.1_9a2e6cfb/bin/gprbuild)
I’m not sure if this GLIBC_2.35 requirement is expected or not for GNAT FSF 15.