unable to install python3.4 dev on fresh ubuntu cloud image

[Sergey Skripnick]

Latest cloud ubuntu trusty image (06-Oct-2015 10:34) https://cloud-images.ubuntu.com/trusty/current/

apt-get update && apt-get upgrade # works fine

# apt-get install python3.4-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3.4-dev : Depends: python3.4 (= 3.4.0-2ubuntu1.1) but 3.4.3-1ubuntu1~14.04.1 is to be installed
                 Depends: libpython3.4-dev (= 3.4.0-2ubuntu1.1) but it is not going to be installed
                 Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

# apt-get install libpython3.4-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpython3.4-dev : Depends: libpython3.4-stdlib (= 3.4.0-2ubuntu1.1) but 3.4.3-1ubuntu1~14.04.1 is to be installed
                    Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python3.4-dev (not installed)
ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
Uname: Linux 3.13.0-65-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
Date: Tue Oct 6 17:36:17 2015
SourcePackage: python3.4
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian Moyles (bmoyles)]

We encountered the same and were able to overcome it by force-downgrading python3.4, python3.4-minimal, libpython3.4-stdlib, and libpython3.4-minimal to the current version available in the repositories with
apt-get install -y \
  python3.4=3.4.0-2ubuntu1.1 \
  python3.4-minimal=3.4.0-2ubuntu1.1 \
  libpython3.4-stdlib=3.4.0-2ubuntu1.1 \
  libpython3.4-minimal=3.4.0-2ubuntu1.1

At-a-glance, it looks like the cloud image was (accidentally?) built with a newer version of python 3.4 than what is available for the LTS (3.4.3 doesn't look like it hit Ubuntu until Vivid?)

[Launchpad Janitor (janitor)]

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

[Daniel Kraft (daniel-kraft)]

Affects me too, but forced downgrading destroys python libraries it seems:

virtualenv -p /usr/bin/python3 env
Running virtualenv with interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in env/bin/python3
Also creating executable in env/bin/python
Installing setuptools, pip...
  Complete output from command /home/user/jobs/env/bin/python3 -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip:
  Traceback (most recent call last):
  File "/usr/lib/python3.4/queue.py", line 4, in <module>
    import threading
ImportError: No module named 'threading'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/share/python-virtualenv/pip-1.5debian1-py2.py3-none-any.whl/pip/__init__.py", line 9, in <module>
  File "/usr/share/python-virtualenv/pip-1.5debian1-py2.py3-none-any.whl/pip/log.py", line 8, in <module>
  File "/usr/share/python-virtualenv/pip-1.5debian1-py2.py3-none-any.whl/pip/backwardcompat/__init__.py", line 33, in <module>
  File "/usr/lib/python3.4/queue.py", line 6, in <module>
    import dummy_threading as threading
  File "/usr/lib/python3.4/dummy_threading.py", line 45, in <module>
    import threading
ImportError: No module named 'threading'
----------------------------------------
...Installing setuptools, pip...done.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 2339, in <module>
    main()
  File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 825, in main
    symlink=options.symlink)
  File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 993, in create_environment
    install_wheel(to_install, py_executable, search_dirs)
  File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 961, in install_wheel
    'PIP_NO_INDEX': '1'
  File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 903, in call_subprocess
    % (cmd_desc, proc.returncode))
OSError: Command /home/user/jobs/env/bin/python3 -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip failed with error code 1

[Philipp Noack (philipp-noack-b)]

Same problem here with the newest trusty lxc image/template.

[NetBUG (darikcr)]

Can confirm the bug.
However, workaround in #2 helped.
Ubuntu Cloud, Azure.

[Konstantinos Papadopoulos (konstantinos.papadopoulos)]

Bug confirmed.

I get the same error reported in the bug description when creating a fresh image through vagrant and using the https://atlas.hashicorp.com/ubuntu (ubuntu/trusty64), v20150930.0.0 box.

[G-ubuntuone-k (g-ubuntuone-k)]

I am seeing this issue as well. I have multiple systems setup off the same downloaded 14.04 LTS image (from a few months ago). I just installed python3.4-dev on 2 systems last week with no issues, but today encountered this issue on another system. Is something messed up with what is in the repository?

[G-ubuntuone-k (g-ubuntuone-k)]

I found the needed files in the trusty-proposed repository:
deb http://archive.ubuntu.com/ubuntu/ trusty-proposed restricted main multiverse universe

Did the 3.4.3 files get moved out of the normal repository into proposed recently?

[Axel Beckert (xtaran)]

This issue has been caused because the python3.4 upload to trusty-updates from 24th of September has been reverted yesterday and has been replaced by the previous upload. See https://bugs.launchpad.net/bugs/1500768

[graingert (tagrain)]

Where can I get a vagrant cloud image without this problem?

[Martynas Sklizmantas (saint-ghost)]

for virtualenv problem (#4) i have solved it by reinstalling libpython3.4-stdlib:

apt-get install --reinstall libpython3.4-stdlib

[Launchpad Janitor (janitor)]

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

[Alex (aleksey-vasilenko)]

Can't even install libreoffice:

  The following packages have unmet dependencies:
   libreoffice : Depends: python3-uno (>= 4.0~) but it is not going to be installed

[Alex (aleksey-vasilenko)]

python3.4 et al. were updated. The problem is gone.

[Steve Langasek (vorlon)]

this issue does not affect current cloud images.