Solving environment: failed with initial frozen solve. #1

New Issue

waffers · 2023-02-03T19:01:41Z

waffers commented

2023-02-03 19:01:41 +00:00

line 1 of the setup.bat is giving me grief:

F:\sd\tortoise-tts>conda install pytorch torchvision torchaudio pytorch-cuda=11.6 -c pytorch -c nvidia
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment:
(never completes, just spins forever)

tried with all versions of python i could think of (3.7/3.8/3.9/3.10/3.11), none solve.

cuda 11.7 installed in windows and works with stable diffusion in another conda 3.9 env.

pulled all traces of anaconda off the box, cleaned up environment variables, rebooted. clean install of the 5/22 build nets the same results. moved back to 10/22 for more of the same.

any ideas?

line 1 of the setup.bat is giving me grief: F:\sd\tortoise-tts>conda install pytorch torchvision torchaudio pytorch-cuda=11.6 -c pytorch -c nvidia Collecting package metadata (current_repodata.json): done Solving environment: failed with initial frozen solve. Retrying with flexible solve. Collecting package metadata (repodata.json): done Solving environment: \ (never completes, just spins forever) tried with all versions of python i could think of (3.7/3.8/3.9/3.10/3.11), none solve. cuda 11.7 installed in windows and works with stable diffusion in another conda 3.9 env. pulled all traces of anaconda off the box, cleaned up environment variables, rebooted. clean install of the 5/22 build nets the same results. moved back to 10/22 for more of the same. any ideas?

mrq commented

2023-02-03 21:26:37 +00:00

any ideas?

I have a few:

there's this stackoverflow thread that seems semi-promising. It shouldn't hurt to try them. I can't validate if they do work since I'd have to somehow reproduce your error to try the fixes.
I'm going to compile a guideline (or rather, an easy script), to use solely pip and a venv to forgo the need to use conda outright. I honestly only used it to quickly get something set up on Windows for TorToiSe, and its documentation mentioned using that on Windows to avoid dependency issues (that cropped up anyways).
If you're crafty, you could try and supplant your existing Stable Diffusion installation by activating its venv, and from there continuing from installing TorToiSe's dependencies.

Personally, I had conda take quite a but on the solving environment pass, but it did resolve itself eventually. I'm not too fond of conda since it's more bloat, so I was going to try and drop it anyways. I should have a replacement setup guide for it by the end of today, if time allows.

I suppose when I get a nice and easy replacement bat script to use pip+venv, I'll refer you to use that instead.

> any ideas? I have a few: * there's this [stackoverflow thread](https://stackoverflow.com/questions/63734508/stuck-at-solving-environment-on-anaconda) that seems semi-promising. It shouldn't hurt to try them. I can't validate if they do work since I'd have to somehow reproduce your error to try the fixes. * I'm going to compile a guideline (or rather, an easy script), to use solely pip and a venv to forgo the need to use conda outright. I honestly only used it to quickly get something set up on Windows for TorToiSe, and its documentation mentioned using that on Windows to avoid dependency issues (that cropped up anyways). * If you're crafty, you could try and supplant your existing Stable Diffusion installation by activating its venv, and from there continuing from installing TorToiSe's dependencies. Personally, I had conda take quite a but on the `solving environment` pass, but it did resolve itself eventually. I'm not too fond of conda since it's more bloat, so I was going to try and drop it anyways. I should have a replacement setup guide for it by the end of today, if time allows. I suppose when I get a nice and easy replacement bat script to use pip+venv, I'll refer you to use that instead.

mrq commented

2023-02-04 01:19:49 +00:00

I got a working setup with just Python 3.9 and pip in commit 5c876b81f3 and updated the setup.bat to reflect it. I suppose it's not a true fix to the issue, but it definitely cuts down on the bloat that comes with Anaconda.

I got a working setup with just Python 3.9 and pip in commit 5c876b81f32df488653e17ea333237cb7a227d13 and updated the `setup.bat` to reflect it. I suppose it's not a true fix to the issue, but it definitely cuts down on the bloat that comes with Anaconda.

waffers commented

2023-02-04 05:13:02 +00:00

anaconda loves that bloat.

confirming, just set up a new 3.9, git pull, and ran the setup. it rolled through just fine aside from activate.bat trying to run 'py' instead of 'python'. just copied the executable to py.exe as a quick work around since doskey aliases seem to always get lost when dealing with php/python/perl/bat/exe's calling each other.

works great, though. thanks for the help and for the work involved with vitalizing this project!

anaconda loves that bloat. confirming, just set up a new 3.9, git pull, and ran the setup. it rolled through just fine aside from activate.bat trying to run 'py' instead of 'python'. just copied the executable to py.exe as a quick work around since doskey aliases seem to always get lost when dealing with php/python/perl/bat/exe's calling each other. works great, though. thanks for the help and for the work involved with vitalizing this project!

waffers closed this issue

2023-02-04 05:13:49 +00:00

mrq referenced this issue from a commit

2023-02-13 13:30:11 +00:00

Merge pull request 'Update 'README.md'' (#1) from armored1065-patch-1 into main

mrq referenced this issue from a commit

2023-02-19 17:32:12 +00:00

Merge pull request 'Update 'README.md'' (#1) from armored1065-patch-1 into main

mrq referenced this issue from a commit

2023-02-24 16:18:17 +00:00

Merge pull request 'Update 'README.md'' (#1) from armored1065-patch-1 into main

Sign in to join this conversation.