Symbolic link 'pyvenv' is bloken

[wbcchsyn]

I installed package 'python3-venv', however, I cannot use command 'pyvenv' because it is a bloken symbolic link.

## OS Version

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

## Package information

$ dpkg -l python3-venv
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-==============-============-================================================>
ii python3-venv 3.8.2-0ubuntu2 amd64 pyvenv-3 binary for python3 (default python3 ver>
lines 1-6/6 (END)

## The symbolic link is bloken

$ ls -l /usr/bin/pyvenv
lrwxrwxrwx 1 root root 10 3月 13 21:20 /usr/bin/pyvenv -> pyvenv-3.8

$ file /usr/bin/pyvenv
/usr/bin/pyvenv: broken symbolic link to pyvenv-3.8

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-venv 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 6 01:33:25 2020
InstallationDate: Installed on 2020-05-05 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael Johnson (johnsom)]

I have the same problem on aarch64 20.04.

# dpkg --list | grep venv
ii python3-venv 3.8.2-0ubuntu2 arm64 pyvenv-3 binary for python3 (default python3 version)
ii python3.8-venv 3.8.2-1ubuntu1.1 arm64 Interactive high-level object-oriented language (pyvenv binary, version 3.8)

# file /usr/bin/pyvenv
/usr/bin/pyvenv: broken symbolic link to pyvenv-3.8

[Sascha Lucas (sascha-lucas)]

probably just an packaging issue? pyvenv is officially removed in python-3.8[1], so the symlink pyvenv should no longer be created?

[1] https://docs.python.org/dev/whatsnew/3.8.html#api-and-feature-removals