Skip to content

New package: Silo_jll v4.12.0+0#143943

Closed
jlbuild wants to merge 1 commit intomasterfrom
registrator-silo_jll-f5d339c9-v4.12.0+0-31a76a2111
Closed

New package: Silo_jll v4.12.0+0#143943
jlbuild wants to merge 1 commit intomasterfrom
registrator-silo_jll-f5d339c9-v4.12.0+0-31a76a2111

Conversation

@jlbuild
Copy link
Contributor

@jlbuild jlbuild commented Dec 8, 2025

Autogenerated JLL package registration

@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

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
Copy link
Contributor

eschnett commented Dec 9, 2025

[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 #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
Copy link
Contributor

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

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 10, 2025
UUID: f5d339c9-093b-5756-8f08-ceae06537255
Repo: https://github.com/JuliaBinaryWrappers/Silo_jll.jl.git
Tree: 612c499e1d645935958907a6f0b4a790483f0e3b

Registrator tree SHA: be588f25c435fa5b456b986adf2f5c02bd3298f2
@jlbuild jlbuild force-pushed the registrator-silo_jll-f5d339c9-v4.12.0+0-31a76a2111 branch from f8413f2 to 78ed362 Compare December 10, 2025 23:55
@github-actions
Copy link
Contributor

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

@github-actions github-actions bot added the stale label Jan 10, 2026
@DilumAluthge
Copy link
Member

[noblock]

@eschnett Can I close this PR?

@eschnett
Copy link
Contributor

Yes please

@DilumAluthge DilumAluthge deleted the registrator-silo_jll-f5d339c9-v4.12.0+0-31a76a2111 branch January 14, 2026 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants