py-sfepy: update to v2021.3#26865
Conversation
|
@adamjstewart Wondering why spackbot didn't run on this PR 🤔 |
I disabled github actions on my fork, to prevent running all the checks for every commit prior to the PR. Might that be related? |
spackbot-app
bot
added
dependencies
new-variant
new-version
python
update-package
labels
|
I have just fixed the tarball url... |
| url = "https://github.com/sfepy/sfepy/archive/release_2021.3.tar.gz" | ||
|
|
||
| version('2017.3', sha256='d13642b7abed63b83b7eaef4dfce6e84a5afc5798bc7ffa1c413e3e44b5e5996') | ||
| version('2021.3', sha256='822407595e0af5aeaca6ca50e88e46658b5021e177244cbb763dd260e94eda81') |
There was a problem hiding this comment.
Spack's policy is not to remove old versions without first deprecating them to give users time to migrate to the new release, see https://spack.readthedocs.io/en/latest/packaging_guide.html#deprecating-old-versions
There was a problem hiding this comment.
Thanks for pointing that out - I also tried to make the new dependencies conditional based on the version. Conditional variants are not available yet, right?
There was a problem hiding this comment.
Correct, although you can add conflicts that prevent a variant from being used for older versions. I think @becker33 was working on conditional variants?
3 participants
No description provided.