python3 in /usr/local/bin can cause python3 packages to fail to install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python2.7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Committed
|
Undecided
|
Unassigned | ||
python3.5 (Debian) |
Fix Released
|
Unknown
|
|||
python3.5 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Brian Murray | ||
Zesty |
Fix Released
|
High
|
Brian Murray |
Bug Description
[Impact]
An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5.
[Test Case]
1) Ensure the version of python3.5 from the release pocket is installed
2) Install python3 using the instructions at https:/
3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
4) Upgrade to a newer version of python3.5 from -proposed
Observe the following Traceback:
Setting up python3.5-minimal (3.5.3-1) ...
Traceback (most recent call last):
File "/usr/lib/
import importlib.
File "/usr/lib/
import types
File "/usr/lib/
import functools as _functools
File "/usr/lib/
from weakref import WeakKeyDictionary
File "/usr/lib/
from _weakref import (
ImportError: cannot import name '_remove_
dpkg: error processing package python3.5-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3-minimal:
python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.
dpkg: error processing package python3-minimal (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
python3.5-minimal
python3-minimal
With the version of python3.5 from -proposed this Traceback will not be encountered.
[Regression Potential]
It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg.
[Original Description]
Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04.
Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts).
ProblemType: PackageDistroRe
Package: python3 3.5.1-4
ProcVersionSign
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Fri Apr 14 19:27:33 2017
ErrorMessage: pre-dependency problem - not installing python3
InstallationDate: Installed on 2015-05-01 (714 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageV
dpkg 1.18.10ubuntu2
apt 1.4SourcePackage: python3-defaults
Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
tags: | removed: need-duplicate-check |
summary: |
- package python3 3.5.1-4 failed to install/upgrade: pre-dependency - problem - not installing python3 + python3 in /usr/local/bin can cause python3 packages to fail to install |
Changed in python3-defaults (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
affects: | python3-defaults (Ubuntu) → python3.5 (Ubuntu) |
Changed in python3.5 (Ubuntu Xenial): | |
assignee: | nobody → Matthias Klose (doko) |
no longer affects: | python2.7 (Ubuntu Yakkety) |
no longer affects: | python3.5 (Ubuntu Yakkety) |
Changed in python3.5 (Debian): | |
status: | Unknown → Fix Released |
Changed in python3.5 (Ubuntu Xenial): | |
status: | New → In Progress |
assignee: | Matthias Klose (doko) → Brian Murray (brian-murray) |
importance: | Undecided → High |
Changed in python3.5 (Ubuntu Zesty): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Brian Murray (brian-murray) |
description: | updated |
tags: | added: id-59690d2a51b99cb84a07b129 |
Status changed to 'Confirmed' because the bug affects multiple users.