New package: Silo_jll v4.12.0+0

[jlbuild]

Autogenerated JLL package registration

• Registering JLL package Silo_jll.jl
• Repository: https://github.com/JuliaBinaryWrappers/Silo_jll.jl
• Version: v4.12.0+0
• Commit: 9aeb816a88bbf35a51780c86355b17f8c4e2d0ee
• Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/13d782178468bf5f6040b14629125bce0cf70fb5
• Created by: @eschnett

[github-actions[bot]]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new _jll package registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round (~20 minutes).

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[eschnett]

[noblock] HDF5_jll 2.0.0 does not ship binaries for libgfortran_version=4.0.0 any more. weirdly, registering it succeeded, but registering another package that depends on it (Silo_jll 4.12.0) is now failing because the registrator tests with julia 1.6 which uses the old libgfortran version https://github.com/JuliaRegistries/General/pull/143943 .

i assume the correct remedy is to increase the julia compat bound for HDF5_jll? or should we instead update the registrator to stop testing old architectures?

Or we can ignore this and merge anyway?

[eschnett]

This build of Silo is broken. Will resubmit a new PR.