pip install --user fails

Bug #1373565 reported by Shock
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-pip (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I want to install a module in ~/.local which pip install --user should do, according to the docs but instead it fails. Here's the output:

$ pip install --install-option="--user" TermRecord
Downloading/unpacking TermRecord
  Downloading TermRecord-1.1.3.tar.gz (49kB): 49kB downloaded
  Running setup.py (path:/tmp/pip_build_shock/TermRecord/setup.py) egg_info for package TermRecord

Downloading/unpacking Jinja2>=2.6 (from TermRecord)
  Downloading Jinja2-2.7.3.tar.gz (378kB): 378kB downloaded
  Running setup.py (path:/tmp/pip_build_shock/Jinja2/setup.py) egg_info for package Jinja2

    warning: no files found matching '*' under directory 'custom_fixers'
    warning: no previously-included files matching '*' found under directory 'docs/_build'
    warning: no previously-included files matching '*.pyc' found under directory 'jinja2'
    warning: no previously-included files matching '*.pyc' found under directory 'docs'
    warning: no previously-included files matching '*.pyo' found under directory 'jinja2'
    warning: no previously-included files matching '*.pyo' found under directory 'docs'
Requirement already satisfied (use --upgrade to upgrade): markupsafe in /usr/lib/python2.7/dist-packages (from Jinja2>=2.6->TermRecord)
Installing collected packages: TermRecord, Jinja2
  Running setup.py install for TermRecord
    changing mode of build/scripts-2.7/TermRecord from 664 to 775
    error: could not create '/usr/local/share/TermRecord': Permission denied
    Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip_build_shock/TermRecord/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-zhS0F6-record/install-record.txt --single-version-externally-managed --compile --user:
    running install

running build

running build_scripts

creating build

creating build/scripts-2.7

copying and adjusting src/TermRecord -> build/scripts-2.7

changing mode of build/scripts-2.7/TermRecord from 664 to 775

running install_data

creating /usr/local/share/TermRecord

error: could not create '/usr/local/share/TermRecord': Permission denied

----------------------------------------
Cleaning up...
Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip_build_shock/TermRecord/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-zhS0F6-record/install-record.txt --single-version-externally-managed --compile --user failed with error code 1 in /tmp/pip_build_shock/TermRecord
Storing debug log for failure in /home/shock/.pip/pip.log

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-pip 1.5.4-1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 24 21:47:31 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-02 (145 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: python-pip
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Shock (mmiron) wrote :
Revision history for this message
Shock (mmiron) wrote :

Attached pip log file.

Revision history for this message
anatoly techtonik (techtonik) wrote :

Have you tried with a newer `pip`? pip install --user?

Changed in python-pip (Ubuntu):
status: New → Incomplete
Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for python-pip (Ubuntu) because there has been no activity for 60 days.]

Changed in python-pip (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.