Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot load v0.3 via Pkg #22

Closed
dkarrasch opened this issue Jul 4, 2019 · 5 comments
Closed

Cannot load v0.3 via Pkg #22

dkarrasch opened this issue Jul 4, 2019 · 5 comments

Comments

@dkarrasch
Copy link
Contributor

When I simply try to ]add GeophysicalFlows, I am getting delivered version 0.2.0. Is that a problem on my end, or is it related to registering/tagging etc.? Usually, when a package has a Project.toml, you're not supposed to have a REQUIRE file, but this one has both. I can put my package status in here if that's necessary, but wanted to quickly check if that issue has an "easy fix" without digging into all depencies installed in my Julia.

@dkarrasch
Copy link
Contributor Author

It seems that the latest version has not been registered in the Julia registry:
https://github.com/JuliaRegistries/General/blob/master/G/GeophysicalFlows/Versions.toml
I guess you will need to install the Registrator first, and then tag manually or by the TagBot. Anyway, it would be very helpful if users got delivered the latest stable version, without needing to check out master.

@navidcy
Copy link
Member

navidcy commented Jul 5, 2019

@dkarrasch I wasn't doing the latest Registrator steps. I was following the previous tagging procedures with REQUIRE files...
Thanks for pointing this out.

@dkarrasch
Copy link
Contributor Author

Haha, I was typing a long message while you edited yours. You seem to have found everything.

Great package, by the way. I'm collaborating with @natschil with whom you already had contact.

@dkarrasch
Copy link
Contributor Author

I think, what you can do, after installing the registrator app, is to call it from right here and register the current version, which the registrator will find in the Project.toml anyway.

@navidcy
Copy link
Member

navidcy commented Jul 5, 2019

#23 fixes this; I'm closing the issue.

Thanks for your nice remarks!

@navidcy navidcy closed this as completed Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants