milljm
commented
4 years ago This truly might be grounds for a 'start over' event on our moose channel. Right now, installing moose with Conda for Macintosh, is likely borked.
Linux is fine, because the build hash is generated based on jinja2 templating functions in play (and I only added one for Mac [osx])
It looks as though build-number is not the overbearing all-encompassing this-is-what-is-installed-if-highest... is the correct way to operate.
I see a higher PETSc build number available:
[edit moose_backup] https://mooseframework.inl.gov/conda/moose_backup/osx-64/
(moose-petsc-3.11.4-h42030b3_5.tar.bz2)
But it was moose-petsc-3.11.4-h993298a_4.tar.bz2 which was installed during the Conda Initialization step: https://civet.inl.gov/job/482724/
Whats worse, is that I don't know the hash until it's built. -This is not exactly true. But certainly is going to make things difficult when integrating with Civet automatically.
I might be separating conda-moose into individual submodules, containing separate recipes (the way conda-forge does it). I think this way, only one moose-package is built/updated at a time, ensuring that the next-thing-that-needs-building will know about the hash of its predecessor.