#3696 reopened defect

Fix for Ubuntu 20.4 bug on Python-virtualenv

Reported by: amj Owned by: amj
Priority: major Milestone: Automate Release Process
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description (last modified by amj)

fixing "python-virtualenv has no installation candidate". Solution:

Use

apt install virtualenv

Change History (12)

comment:1 Changed at 2021-05-05T15:52:30Z by maylee

  • Milestone changed from undecided to Automate Release Process
  • Owner set to amj

comment:2 Changed at 2021-05-05T15:55:13Z by amj

  • Description modified (diff)

comment:3 Changed at 2021-05-05T22:13:52Z by meejah

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...

comment:4 Changed at 2021-05-06T12:45:43Z by amj

Thanks for letting me know. I tested

apt install virtualenv

and it works.

I will update this ticket for that instead.

Last edited at 2021-05-06T12:49:05Z by amj (previous) (diff)

comment:5 Changed at 2021-05-06T12:47:40Z by amj

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

comment:6 Changed at 2021-05-06T12:48:10Z by amj

  • Description modified (diff)

comment:7 Changed at 2021-05-06T17:24:30Z by meejah

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).

comment:8 Changed at 2021-05-06T17:24:48Z by meejah

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:9 Changed at 2021-05-06T17:32:21Z by amj

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.

comment:10 Changed at 2021-05-06T18:24:55Z by meejah

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

comment:11 Changed at 2021-05-07T17:23:45Z by amj

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.

Last edited at 2021-05-10T09:10:18Z by amj (previous) (diff)

comment:12 Changed at 2021-05-11T19:57:00Z by meejah

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.

Note: See TracTickets for help on using tickets.