New package: Eternity2Solvers v0.1.0

[JuliaRegistrator]

• Registering package: Eternity2Solvers
• Repository: https://github.com/jwortmann/Eternity2Solvers.jl
• Created by: @jwortmann
• Version: v0.1.0
• Commit: fe4f36481a36ea214034777afbe0a62b647fa20a
• Reviewed by: @jwortmann
• Reference: jwortmann/Eternity2Puzzles.jl@fe4f364#commitcomment-143599575
• Description: An implementation of the Eternity II puzzle in Julia

[github-actions]

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. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• I was not able to load the package (i.e. import Eternity2Solvers failed). See the AutoMerge logs for details.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. 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.

[jwortmann]

Hello, I can't reproduce the precompile failures of the GameZero and SimpleDirectMediaLayer dependencies using Julia 1.10.4 on Windows 11.

However, I noticed that there is another blocking problem which prevents the dependencies to be loaded when my package is loaded in an arbitrary environment - this didn't manifest in my dev environment where I used using Eternity2Solvers directly from within my package directory. I will try to find a workaround for that, but I guess this PR could be closed for now.

And if anybody knows how to fix the precompile failures, tips would be welcome!

[jwortmann]

According to the open issue at JuliaMultimedia/SimpleDirectMediaLayer.jl#80 it seems that the SimpleDirectMediaLayer.jl dependency is currently incompatible with Julia 1.10 on Ubuntu. Is there anything I could do so that my package could still be added to the registry? I guess there is no mechanism to restrict packages to certain operating systems, e.g. only Windows?

[jwortmann]

I decided to rename the package to Eternity2Puzzles.jl and initiated a new PR #110870. So this PR here can be closed now (I'm unable to do that myself because it was opened by the registrator bot).

Unfortunately the CI runner indicates that the SimpleDirectMediaLayer.jl dependency is still broken on Ubuntu (failed to precompile). Does it mean that the registration of my package is blocked indefinitely, and that other packages using SimpleDirectMediaLayer.jl as a dependency (e.g. GameZero.jl) are blocked from doing new releases? I would appreciate any guidance about how to proceed.

[GunnarFarneback]

You could upper bound Julia to 1.9 for now, but it's hardly ideal. Otherwise I don't know. There is always an option of manual merges, but that's also not ideal.

[Kyjor]

@jwortmann , I know this is closed now, but this issue was fixed this morning

[jwortmann]

Thank you very much, I pushed an update in my other PR and indeed the package is successfully registered now. 👍

As a sidenote @Kyjor, it was actually reading one of your forum threads what motivated me to create this package. So thanks for the inspiration :)

[Kyjor]

@jwortmann Awesome, glad you were finally able to get it registered.

And that makes me so happy to hear! :) When I see things like that, it motivates me to keep doing what I'm doing