package python-lazy-object-proxy 1.2.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1698682 reported by Laurie
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
configparser (Ubuntu)
Invalid
Undecided
Unassigned
isort (Ubuntu)
Invalid
Low
Unassigned
lazy-object-proxy (Ubuntu)
Invalid
Low
Unassigned
python-wrapt (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Trying to install Spyder3 after installing Anaconda

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python-lazy-object-proxy 1.2.2-1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sun Jun 18 15:36:16 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-06-15 (3 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: lazy-object-proxy
Title: package python-lazy-object-proxy 1.2.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Laurie (ljl069) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for taking your time to report this issue and help making Ubuntu better.

It seems to be the same underlying error responsible for these three bugs, so I've taken this one which contains the longest DpkgTerminal.log and marked the other two as duplicates. Based on the following error it seems like the python-configparser package might be the root cause
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in <module>
    from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in <module>
    from ConfigParser import SafeConfigParser
ModuleNotFoundError: No module named 'ConfigParser'

I must admit I'm not quite sure how it is broken though...

Revision history for this message
James Page (james-page) wrote :

I keep tripping over this stacktrace; ConfigParser is part of python2.7; but got renamed in python3 onwards to configparser so the debpython version module is not Python 3 compatible.

If /usr/bin/python does not point to /usr/bin/python2.7 you might see this issue - is that the case in this install?

Marking 'Incomplete' pending response from reporter.

Changed in configparser (Ubuntu):
status: New → Invalid
Changed in python-wrapt (Ubuntu):
status: New → Incomplete
Changed in lazy-object-proxy (Ubuntu):
status: New → Incomplete
Changed in isort (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Changed in lazy-object-proxy (Ubuntu):
importance: Undecided → Low
Changed in python-wrapt (Ubuntu):
importance: Undecided → Low
Revision history for this message
Mattia Rizzolo (mapreri) wrote :

I'm marking it as invalid as that's clearly the reason of this failure (and the reported hasn't come back in months.
(auto-expire doesn't work on bugs with multiple tasks)

Changed in isort (Ubuntu):
status: Incomplete → Invalid
Changed in lazy-object-proxy (Ubuntu):
status: Incomplete → Invalid
Changed in python-wrapt (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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