pip3 installation does not give expected result
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
python-pip (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
To a naive user (like me) the following should not happen. I get a suggestion to install an already-installed package. ie, installing the package does not make a difference:
[~/]$ pip3
The program 'pip3' is currently not installed. You can install it by
typing:
sudo apt install python3-pip
[~/]$ sudo apt install python3-pip
wipe your finger across the fingerprint reader
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-pip is already the newest version (9.0.1-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: python3-pip 9.0.1-2
ProcVersionSign
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 1 12:09:42 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-18 (225 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitec
SourcePackage: python-pip
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Thanks for reporting.
The package suggestion comes from the command-not-found package, but I'm not quite sure which is at fault here. (Especially since I am not able to reproduce the issue on my 17.10 system, pip3 runs as expected after installing)
Could you please post the output of the following commands:
1. dpkg -L python3-pip (tells us which files are installed by the package, which should include the pip3 binary)
2. apt policy python3-pip (just to double-check, the version number looks ok from the apport information in the summary)
3. echo $PATH (in case it can't find the binary to run in your PATH, although this sounds a bit unlikely)