search

Open-MSS / MSS

A QT application, a OGC web map server, a collaboration server to plan atmospheric research flights.
https://open-mss.github.io
Apache License 2.0
61 stars 77 forks source link

Automatic updater does not work correctly #1409

Closed jgrooss closed 2 years ago

jgrooss commented 2 years ago

currently the newest mss version is 6.0.5 If on 6.0.4 UI the updater in the Help menu of the UI is executed, it does not reckognise the new version. Similar behaviour was seen before

ReimarBauer commented 2 years ago

Worked for me yesterday automatically but it took some minutes. I am also not sure if I had overseen the small window because it pops up on my second screen.

jgrooss commented 2 years ago

In my case the popup updater panel sais "Newest Version 6.0.4 / Nothing to do"

ReimarBauer commented 2 years ago

This may be related to the version of conda, please show me the output of conda --version

jgrooss commented 2 years ago

$ conda --version conda 4.8.5

ReimarBauer commented 2 years ago

I do have conda 4.12 this is currently the most recent one. Likly I have done that update manually.

ReimarBauer commented 2 years ago

I reproduces this when the conda version is too old it can't update.

One has first to 

conda update -n base conda -c defaults

conda and mamba gets also updated in newer versions to newest version. We can't solve this for the user by our updater.

ReimarBauer commented 2 years ago

We should implement this before we search for updates. This should solve that one is blocked by a stone age old version of the installer.

conda update -n base conda -c defaults

ReimarBauer commented 2 years ago

We should implement this before we search for updates. This should solve that one is blocked by a stone age old version of the installer.

conda update -n base conda -c defaults

recent version of MSS are completly based on conda-forge. Only on a very old version an update of defaults will help. I think we better ask for a new installation in such a case.

jgrooss commented 2 years ago

I tried to use the updater in 7.0.1 and it didn't work again, showing the following message:

mamba search mss
Traceback (most recent call last):
  File "/...xxx.../software/anaconda3/bin/mamba", line 7, in <module>
    from mamba.mamba import main
  File "/...xxx.../software/anaconda3/lib/python3.7/site-packages/mamba/mamba.py", line 53, in <module>
    from mamba.utils import get_index, to_package_record_from_subjson, _supplement_index_with_system
  File "/...xxx.../software/anaconda3/lib/python3.7/site-packages/mamba/utils.py", line 7, in <module>
    from .FastSubdirData import FastSubdirData
  File "/...xxx.../software/anaconda3/lib/python3.7/site-packages/mamba/FastSubdirData.py", line 23, in <module>
    from conda._vendor.auxlib.ish import dals
ModuleNotFoundError: No module named 'conda._vendor.auxlib'
mamba list -f mss
Traceback (most recent call last):
  File "/...xxx.../software/anaconda3/bin/mamba", line 7, in <module>
    from mamba.mamba import main
  File "/...xxx.../software/anaconda3/lib/python3.7/site-packages/mamba/mamba.py", line 53, in <module>
    from mamba.utils import get_index, to_package_record_from_subjson, _supplement_index_with_system
  File "/...xxx.../software/anaconda3/lib/python3.7/site-packages/mamba/utils.py", line 7, in <module>
    from .FastSubdirData import FastSubdirData
  File "/...xxx.../software/anaconda3/lib/python3.7/site-packages/mamba/FastSubdirData.py", line 23, in <module>
    from conda._vendor.auxlib.ish import dals
ModuleNotFoundError: No module named 'conda._vendor.auxlib'

(original path was replaced with ...xxx...)

ReimarBauer commented 2 years ago

The conda version in the base environment is outdated. see https://github.com/mamba-org/mamba/issues/1583#issuecomment-1109727272

which version of anaconda do you have?

ReimarBauer commented 2 years ago

We should catch the error and give a hint how to solve the problem manually.

jgrooss commented 2 years ago

How could I update the conda version? "conda update conda" does not change the behaviour

jgrooss commented 2 years ago

My conda Version is now 4.13.0

ReimarBauer commented 2 years ago

in the environment where you have mss installed

show the output of:

jgrooss commented 2 years ago 
mamba --version
mamba 0.24.0
conda 4.13.0
jgrooss commented 2 years ago 
mamba list conda
# packages in environment at /...xxx.../software/anaconda3/envs/mssenv:
#
# Name                    Version                   Build  Channel
conda                     4.13.0          py310hff52083_1    conda-forge
conda-package-handling    1.8.1           py310h5764c6d_1    conda-forge

mamba list mamba
# packages in environment at /...xxx.../software/anaconda3/envs/mssenv:
#
# Name                    Version                   Build  Channel
libmamba                  0.24.0               hd8a31e3_1    conda-forge
libmambapy                0.24.0          py310hab0e683_1    conda-forge
mamba                     0.24.0          py310hf87f941_1    conda-forge
ReimarBauer commented 2 years ago

mamba seems now to be a py3.10 version, while the error happens in a python 3.7 environment Have you changed for the output the python version?

If it is now on py3.10 because of the update, try a msui --update next. Does it show the same failure?

ReimarBauer commented 2 years ago

I'm a step further by

conda create -n mss7 mamba python==3.7
conda activate mss7
(mss7) mamba install mss==7.0.0

I even cannot install mss 7.0.0 in such a python 3.7 environment

Traceback (most recent call last):
  File "/home/reimar/miniconda3/envs/mss7/bin/mamba", line 7, in <module>
    from mamba.mamba import main
  File "/home/reimar/miniconda3/envs/mss7/lib/python3.7/site-packages/mamba/mamba.py", line 53, in <module>
    from mamba.utils import get_index, to_package_record_from_subjson, _supplement_index_with_system
  File "/home/reimar/miniconda3/envs/mss7/lib/python3.7/site-packages/mamba/utils.py", line 7, in <module>
    from .FastSubdirData import FastSubdirData
  File "/home/reimar/miniconda3/envs/mss7/lib/python3.7/site-packages/mamba/FastSubdirData.py", line 23, in <module>
    from conda._vendor.auxlib.ish import dals
ModuleNotFoundError: No module named 'conda._vendor.auxlib'

It should not crash, but also not be installable because we have no build for python 3.7 since long.

The last mss version for python 3.7 on our build channel is 6.1.1

Could it be that you have used an own build?

ReimarBauer commented 2 years ago

upstream idea reported https://github.com/mamba-org/mamba/issues/1832

jgrooss commented 2 years ago

msui --update works and tells me 'Your MSS is up to date.' I didn't change any python version on purpose, but I may have done it. I don't know

jgrooss commented 2 years ago

I don't understand this discussion. Which installer version would be "stone age"? This discussion gives me no hint how to overcome this error message.

ReimarBauer commented 2 years ago

I maybe misunderstand your answer 

msui --update
works and tells me 'Your MSS is up to date.'

Which version do you have now?

7.0.1 is the recent version of MSS

When you used before python 3.7 then you would have had mss 6.1.1 before, don't you? A mss-7.0.0 is no official built for python-3.7. Same with 7.0.1 we have excluded python 3.7.

ReimarBauer commented 2 years ago

@jgrooss and me tracked that problem down today. It happens when in a anaconda3 setup python 3.7 is the default python interpreter in the base and additional mamba was installed in the base.

At the time the updater runs it finds the outdated mamba version and crashes because that is first in the path.

This makes it looking like an installed MSS in py-3.7 which isn't there.

This gives some option we can look at for improvement.