I don't have an Ubuntu 20.04 system handy just now, but a package-search (https://packages.ubuntu.com/search?keywords=virtualenv&searchon=names&suite=focal&section=all) seems to indicate that the package is just called virtualenv on that distribution (not python-virtualenv as in Debian itself). So, perhaps that's the only change needed (to note that Ubuntu users may need apt install virtualenv instead of apt install python-virtualenv)..?

Also we need instructions that work for python2 still (not python3 as the above are for). As much as I might wish for python3 to work now ;) it doesn't yet...

Although some people might like to use virtualenvwrapper, that's certainly not a prerequisite. I don't have an Ubuntu 20.04 system handy just now, but a package-search (<https://packages.ubuntu.com/search?keywords=virtualenv&searchon=names&suite=focal&section=all>) seems to indicate that the package is just called `virtualenv` on that distribution (not `python-virtualenv` as in Debian itself). So, perhaps that's the only change needed (to note that Ubuntu users may need `apt install virtualenv` instead of `apt install python-virtualenv`)..? Also we need instructions that work for python2 still (not python3 as the above are for). As much as I might wish for python3 to work now ;) it doesn't yet...

amj commented

2021-05-06 12:45:43 +00:00

Author

Owner

Thanks for letting me know. I tested

apt install virtualenv

and it works.
I will update this ticket for that instead.

Thanks for letting me know. I tested ``` apt install virtualenv ``` and it works. I will update this ticket for that instead.

tahoe-lafs added the

fixed

label 2021-05-06 12:47:40 +00:00

amj closed this issue

2021-05-06 12:47:40 +00:00

meejah commented

2021-05-06 17:24:30 +00:00

Author

Owner

As a general "process" thing, normally a ticket should only be closed once a solution is merged into the main repository (that is, propose a PR on github fixing the instructions for affected platforms and then close this ticket once that is reviewed and merged).

tahoe-lafs removed the

fixed

label 2021-05-06 17:24:48 +00:00

meejah reopened this issue

2021-05-06 17:24:48 +00:00

amj commented

2021-05-06 17:32:21 +00:00

Author

Owner

while

apt-get install build-essential python-dev libffi-dev libssl-dev libyaml-dev virtualenv

gets all the packages installed in Ubuntu 20.04, after installing tahoe-lafs, the Tahoe-lafs wouldn't run. I am still investigating the issue.

while ``` apt-get install build-essential python-dev libffi-dev libssl-dev libyaml-dev virtualenv ``` > gets all the packages installed in Ubuntu 20.04, after installing tahoe-lafs, the Tahoe-lafs wouldn't run. I am still investigating the issue.

meejah commented

2021-05-06 18:24:55 +00:00

Author

Owner

Okay, great!
Please feel free to bug me when you have a PR/updated instructions :)

Okay, great! Please feel free to bug me when you have a PR/updated instructions :)

amj commented

2021-05-07 17:23:45 +00:00

Author

Owner

I wrote some instructions here that got it working:

https://github.com/AMJ-dev/Tahoe_update/blob/main/specials/INSTALL_UBUNTU.rst

. It is a bit long, and I am not sure yet, if it should go into "INSTALL.rst", or if it should stand alone. Please help.

I wrote some instructions here that got it working: ``` https://github.com/AMJ-dev/Tahoe_update/blob/main/specials/INSTALL_UBUNTU.rst ``` . It is a bit long, and I am not sure yet, if it should go into "INSTALL.rst", or if it should stand alone. Please help.

meejah commented

2021-05-11 19:57:00 +00:00

Author

Owner

If python3 is the default python on Ubuntu 20.04, I'm surprised that "apt install python" gives you python2 and not python3?

I don't think we want completely separate instructions for this OS -- at most, we'd want just the special instructions needed to get to the same point as the "main" Debian instructions. That is: working virtualenv + python2.

So I think the only thing that's different is "how to get python2" and the name of the virtualenv package. Right?

In any case, it's still best to express this as a PR on github so that one may examine the proposed changes. Thanks.

If python3 is the default python on Ubuntu 20.04, I'm surprised that "apt install python" gives you python2 and not python3? I don't think we want completely separate instructions for this OS -- at most, we'd want just the special instructions needed to get to the same point as the "main" Debian instructions. That is: working virtualenv + python2. So I think the only thing that's different is "how to get python2" and the name of the virtualenv package. Right? In any case, it's still best to express this as a PR on github so that one may examine the proposed changes. Thanks.