Issue with LIBRARIES update

[CarloParisi]

---

Issue Description

What did you expect to see happen?

After ~8 months I decided to rerun a RAVEN input deck. Before running it I followed the procedure described on the RAVEN website, updating the codes AND the libraries.
The code is being executed on INL FALCON HPC.

0. module load raven-devel

Then :

1. git pull
2. scripts/establish_conda_env.sh --install

The libraries were correctly updated.

What did you see instead?

I run the old input deck after the SW updates, and I got the following message:

ERROR: Some required Python libraries have incorrect versions for running RAVEN as configured:

-> WRONG VERSION: lib "matplotlib" need "3.2" but found "3.4.2"

Try installing libraries using instructions on RAVEN repository wiki at https://github.com/idaholab/raven/wiki/Installing_RAVEN_Libraries.

Do you have a suggested fix for the development team?

I contacted @wangcj05 and he suggested me to manually update the file ./raven/dependencies.xml . I did it changing the matplotlib from 3.2 to 3.4.2.

After that change, the code run without any problem.

Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

Input file is about MC sampling and basic statistics calculations.
R5RAVEN_153_LHS_FLECHT_A5.xml.zip

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• 1. Is it tagged with a type: defect or task?
• 2. Is it tagged with a priority: critical, normal or minor?
• 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• 1. If the issue is a defect, is the defect fixed?
• 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?