Your message dated Sat, 28 Jan 2023 16:58:45 -0400 with message-id <[email protected]> and subject line Re: Bug#816740: python3-venv: virtual environment was not created successfully because ensurepip is not available has caused the Debian Bug report #816740, regarding python3-venv: virtual environment was not created successfully because ensurepip is not available to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 816740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816740 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python3-venv Version: 3.5.1-2 Severity: important Dear beloved Maintainer, I recently updated my Debian unstable with the new python-3.5 packages and it rendered the pyvenv command totally unusable (that is why I am marking this report as 'important'). What are the symptoms and how to reproduce it: ============================================== $> pyvenv my_venv_name The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command. apt-get install python3-venv You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment. =========================================== So, I cannot get 'pyvenv' to workproperly. This bug seems to have been already observed in the Ubuntu python3.4 package, see: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1290847 I also noticed that the package 'python3-pip' is not a prequisite for 'python3-venv' (which may lead to strange situations in my humble opinion). Note that 'virtualenv' is still working properly, so a temporary workaround for pyvenv creation in a Python3 fashion is: virtualenv --python=python3.5 venv_name -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.3 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-venv depends on: ii python3 3.5.1-2 ii python3.5-venv 3.5.1-7 python3-venv recommends no packages. python3-venv suggests no packages. -- no debconf information
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Hi Chris (2021.04.24_11:14:11_-0400) > It has come to my attention that there are failure modes that cause > this message to show up, even if python3-venv is already installed. > From what I understand about this bug report, the original submitter > might have one of those situations. Been aware of those too, but I think we've fixed them. So, closing this bug in the hope that it's history. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
--- End Message ---
