"Fatal" warning during MOOSE update

[EdSheltonUKAEA]

I'm trying to do a Conda/Mamba and MOOSE update and got the following when attempting to do the git rebase:

(moose) eshelton@K0214:~$ cd /projects/moose
(moose) eshelton@K0214:/projects/moose$ git fetch origin
remote: Enumerating objects: 19833, done.
remote: Counting objects: 100% (12117/12117), done.
remote: Compressing objects: 100% (2079/2079), done.
remote: Total 19833 (delta 10437), reused 11338 (delta 9968), pack-reused 7716
Receiving objects: 100% (19833/19833), 17.08 MiB | 8.36 MiB/s, done.
Resolving deltas: 100% (14937/14937), completed with 1892 local objects.
From https://github.com/idaholab/moose
c9f69be..c5bcc5d master -> origin/master

• [new branch] 2023-11-08-release -> origin/2023-11-08-release
• [new branch] assembly-refactors-25666 -> origin/assembly-refactors-25666
  e8c7f09..c835ce5 devel -> origin/devel
  9f83051..3833a5c next -> origin/next
  c9f69be..c5bcc5d scheduled -> origin/scheduled
• [new branch] thm-joss-paper-review -> origin/thm-joss-paper-review
• [new tag] 2023-11-08 -> 2023-11-08
  (moose) eshelton@K0214:~/projects/moose$ git rebase origin/master
  First, rewinding head to replay your work on top of it...
  error: Updating the following directories would lose untracked files in them:
  modules/heat_conduction/src

Aborting
fatal: Could not detach HEAD
(moose) eshelton@K0214:~/projects/moose$

The "Aborting" and "fatal" messages don't look like good news!
I don't think I've ever had a problem like this before running the git fetch and rebase commands.
Has the MOOSE update procedure changed, or is there a problem here.
Is it safe for me to proceed with the clobberall and make in my project directory, or is this likely to fail if the git update didn't work?

[GiudGiud]

Hello

Did you put work in the heat conduction module?

That module was renamed to heat transfer. The rebase should have worked but maybe it got confused because of the sym links we now have in the former heat conduction module.

How many commits are we talking about here? Could we consider doing this manually?

Is this branch public?

Guillaume

[GiudGiud]

I d delete mamba and re-install with conda.

We actually made the switch from mambaforge to miniforge so it would not be surprising to have difficulties download new packages

[EdSheltonUKAEA]

OK. Thanks. I'll work with colleagues who know more about the software operating systems behind MOOSE to try to resolve these problems.

[GiudGiud]

How and in what folder should I run update_and_rebuild_wasp?

This should be done in the moose/scripts folder. But not if you are using conda. If you are using conda, the conda-downloaded packages will include moose-wasp.

If they dont, the conda update is failing. And the easiest way to fix it are either a new conda environment or simply wipe conda and install it again. Since we also transitioned from mambaforge to miniforge, I would recommend the latter

[milljm]

If you choose to reinstall Conda, please be sure to re-follow our instructions: https://mooseframework.inl.gov/getting_started/installation/conda.html

There is a one-liner folks seems to forget: conda update --all immediately after installing Conda. This is necessary to get the very latest actual version of conda which has the correct package solver in it.

[EdSheltonUKAEA]

Hi - I was able to get a colleague to help me do a complete removal and reinstall of MOOSE and the supporting software package management tools on both my laptop and shared desktop, so this is all sorted now. Thanks again for the advice and help.
Ed