package python-lockfile 1:0.12.2-1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Bug #1591541 reported by Harshad Awati
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python-lockfile (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Need to get 37.4 kB/178 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 python3-minimal amd64 3.5.1-3 [23.3 kB]
Get:2 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 python-lockfile all 1:0.12.2-1 [14.1 kB]
Fetched 37.4 kB in 1s (20.9 kB/s)
(Reading database ... 291413 files and directories currently installed.)
Preparing to unpack .../python3-minimal_3.5.1-3_amd64.deb ...
Unpacking python3-minimal (3.5.1-3) over (3.5.1-3) ...
Preparing to unpack .../python-lockfile_1%3a0.12.2-1_all.deb ...
  File "/usr/bin/pyclean", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
  File "/usr/bin/pyclean", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: error processing archive /var/cache/apt/archives/python-lockfile_1%3a0.12.2-1_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
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
ImportError: No module named 'ConfigParser'
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 1
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/python-lockfile_1%3a0.12.2-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-lockfile 1:0.12.2-1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Jun 11 23:54:18 2016
Dependencies:

ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-02-20 (111 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: python-lockfile
Title: package python-lockfile 1:0.12.2-1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Harshad Awati (harshadawati4) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in python-lockfile (Ubuntu):
status: New → Confirmed
Louis (stitch0louis)
Changed in python-lockfile (Ubuntu):
assignee: nobody → Louis (stitch0louis)
Changed in python-lockfile (Ubuntu):
importance: Undecided → High
Changed in python-lockfile (Ubuntu):
importance: High → Undecided
assignee: Louis (stitch0louis) → nobody
importance: Undecided → High
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.