You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you have an existing installation that contains an OCA module installed using pip, that perhaps was installed referring to a PR, and then this PR is merged into OCA, you may get this situation when you do pip install -r requirements.txt:
What to do? (s)witch, (i)gnore, (w)ipe, (b)ackup
The problem is that ansible runs all the steps automatically, and this one is treated as an error.
Perhaps in the ansible role we should always wipe all the OCA modules every time, or force update of them all?
One thing I do not like with the ansible approach is that in general, as the ansible role evolves, the old packages, python modules, etc.. are not going to be removed. This is something that Docker does better, as it creates from scratch every time, ensuring that there's no artifact sitting in the server that is not included in the configuration files.
cc @sbidoul perhaps you know how to force the pip install to always wipe the old pip module?
The text was updated successfully, but these errors were encountered:
This question (switch/ignore/wite/backup) is typically asked when you try to switch from a https to a ssh git reference (ie when you change from -e git+https://github.com... to -e git@github.com or vice-versa).
Currently if you have an existing installation that contains an OCA module installed using pip, that perhaps was installed referring to a PR, and then this PR is merged into OCA, you may get this situation when you do pip install -r requirements.txt:
What to do? (s)witch, (i)gnore, (w)ipe, (b)ackup
The problem is that ansible runs all the steps automatically, and this one is treated as an error.
Perhaps in the ansible role we should always wipe all the OCA modules every time, or force update of them all?
One thing I do not like with the ansible approach is that in general, as the ansible role evolves, the old packages, python modules, etc.. are not going to be removed. This is something that Docker does better, as it creates from scratch every time, ensuring that there's no artifact sitting in the server that is not included in the configuration files.
cc @sbidoul perhaps you know how to force the pip install to always wipe the old pip module?
The text was updated successfully, but these errors were encountered: