Error about mamba installation cannot declare variable 'moose_server' to be of abstract type 'MooseServer' #25729
-
|
I do like this for a new version #25358 Then I install the MOOSE environment again. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 11 replies
-
|
Can you perform the following commands and report the results: mamba activate moose
cd ~/projects/moose
scripts/versioner.py wasp --yaml | grep install
mamba list | grep mooseI want to see what version of wasp your version of MOOSE requires... and what you have currently installed. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like you have a very updated set of Conda packages, but your version of MOOSE is fairly old. Can you update your version of MOOSE? Or are you busy working on a specific checkout? If you need to downgrade the Conda environment I can help with that... |
Beta Was this translation helpful? Give feedback.
-
|
So what do you mean? Have you mentioned the two ways: downgrade the Conda environment or upgrade the version of MOOSE. Which one should I choose? |
Beta Was this translation helpful? Give feedback.
-
|
And I edited the discussion to tell you the full story of what happened |
Beta Was this translation helpful? Give feedback.
-
|
We would prefer you stay as up-to-date as possible :) In that case: cd ~/projects/moose
git fetch origin
git pullshould bring you in-line with what you have for your Conda environment. Afterwards, you'll want to clean out the failed previous build, and start anew: cd ~/projects/moese
git clean -xfd # save any uncommitted work.
# But it sounds like you won't have any
cd test
make -j 6FYI, the Conda packages and your MOOSE repository hold a very tight bond on where they need to be. Basically, when you update one, you should update the other... What I mean by that, is when ever you: mamba update --all # or mamba update moose-devyou should also: git fetch origin
git pulland vice versa. |
Beta Was this translation helpful? Give feedback.
-
|
I just read your updated post. Ahh yeah... You basically performed a clean reinstall, which will grab the latest available Conda packages. |
Beta Was this translation helpful? Give feedback.
-
|
Oppps, It seems that it cannot find libmesh? em.... |
Beta Was this translation helpful? Give feedback.
-
|
Then I try to do the run scripts/update_and_rebuild_wasp.sh, it cannot work, either |
Beta Was this translation helpful? Give feedback.
-
|
I think this is happening because you were operating in the mamba activate mooseand then try! |
Beta Was this translation helpful? Give feedback.
We would prefer you stay as up-to-date as possible :)
In that case:
should bring you in-line with what you have for your Conda environment. Afterwards, you'll want to clean out the failed previous build, and start anew:
FYI, the Conda packages and your MOOSE repository hold a very tight bond on where they need to be. Basically, when you update one, you should update the other... What I mean by that, is when ever you:
mamba update --all # or mamba update moose-devyou should also: