And then an attempt to move to rev 5 and the traceback. No module named conda_package_handling`` fundamentally, there's something. Conda 4.3 fixed the root cause of this issue with transactions.
I did so by reverting back to the previous revision rather than uninstalling it and its dependencies. If the file is added (meaning,. “revert files” reverts a file to its earlier version stored in revision control (which happens when you use the check in changes button).
If rerun, a different package is not in repodata each time: Identify the revision number you wish to. Conda version 4.3.30 was debugging a separate issue and tried going to a rev without a specific package installed. 问题1: conda is broken after update.
Example of conda uninstalling itself during a failed update. The only solution here, unfortunately, is to download. One robust option for reverting back to a previous installation is by utilizing the revision history feature in conda. An unexpected error has occurred.
Try to checkout revision 1124 in a new empty directory, so you won't have conflicts with already existing directories. Here are my latest two revisions before trying a revert: @evanburgess, the problem is that, when we want to roll back to an.