We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not sure if this was done intentionally for some reason, but the tag for 1_6_3 has an extra _ in it's name between the v and the 1
1_6_3
_
v
1
v_1_6_3
I noticed this because it breaks some of the automation in the Spack package manager.
The text was updated successfully, but these errors were encountered:
Tags haven't been super consistent over the years (just noticed v1.5.0 there too). Would adding a v1_6_3 tag suffice for your needs?
v1.5.0
v1_6_3
Sorry, something went wrong.
Yes, that's what Spack's automagic machinery expects so builds will work smoothly.
Thanks!!
Done! Have a great day. :)
Perfect!
No branches or pull requests
Not sure if this was done intentionally for some reason, but the tag for
1_6_3
has an extra_
in it's name between thev
and the1
I noticed this because it breaks some of the automation in the Spack package manager.
The text was updated successfully, but these errors were encountered: