Hello team,
This is Michael and it is my first time setting up yugabyte. I want to start working on my first contribution, but I am running into a virtual env issue.
Thank you so much for your time.
Hi @MichDoDoDo
What is your OS? Looks like windows on the screenshot?
That is WSL2 … The CLI colors + Windows explorer (browsing WSL2) is a dead giveaway.
Hello @dorian_yugabyte,
PC on win10 OS, using ubuntu 22.04.05 LTS. Hope this helps clear things up 
.
So venv/bin/activate is missing. Do you have a venv/Scripts/activate? Maybe try editing build/yugabyte-bash-common/src/create_venv.sh to change line 241 “/bin/activate” to “Scripts/activate”. Alternatively, try to fix your python so that it creates venv in a linux-like way. Maybe you installed python outside of WSL? Consider checking out python - Installing venv for python3 in WSL (Ubuntu) - Stack Overflow
Also try making frequent use of --clean-venv for yb_build.sh until you solve the issue.
Hello Jason,
Thank you for reaching out and offering help with this issue. Addressing the first question, I do not have a venv/Scripts/activate. If I were to add my own activate script would a shell script be the proper way (linux - How to activate python virtualenv through shell script? - Super User) ?
Can you try ./yb_build.sh release --clean-venv? If that still gives venv-related issue, try python3 -m venv /tmp/mytestvenv and see whether /tmp/mytestvenv/bin/activate exists
If I were to add my own activate script would a shell script be the proper way
that looks unrelated
Of course! I tried running ./yb_build.sh release --clean-venv and still getting the same error. When running python3 -m venv /tmp/mytestvenv I do see that mytestvenv has the activate file.
Maybe it is picking up a different python when creating? The logic is in build/yugabyte-bash-common/src/detect_python.sh to set yb_python_interpreter. You can investigate the logic or try manually creating the venv by rm -r build/venv followed by python3 -m venv build/venv then run ./yb_build.sh release without --clean-venv
Great Jason, I was able to pass in to the next step. I am currently building and wanted to ask, is there a reason why version.txt was deleted? I see that here was a FileNotFoundError: [Errno 2] No such file or directory: '/home/michdo/yugabyte-db/version.txt' I wonder if it was deleted during ./yb_build.sh release.
It is normally a symlink. Maybe windows does not like it? What does git config core.symlinks show? You can bring those files back with git checkout -f.
Running git config core.symlinks does not show anything.
does not show anything
good
did you read and complete steps in Build from source code on Ubuntu | YugabyteDB Docs ?