package mercurial-common 3.7.3-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1593099 reported by Evgen Zakarliuka
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
mercurial (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

after command sudo apt install mercurial this package do not install.
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 mercurial-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mercurial-common 3.7.3-1ubuntu1
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: Thu Jun 16 09:13:17 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-06-15 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: mercurial
Title: package mercurial-common 3.7.3-1ubuntu1 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
Evgen Zakarliuka (people147) wrote :
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 mercurial (Ubuntu):
status: New → Confirmed
Revision history for this message
Doran D. Smith (dorandsmith) wrote :

Don't know if this is a real bug -- the system generated the report, not me. Am trying to fix a problem with a first sypder install. spyder found a file in python2.7 that was bad. Would not allow spyder to launch. Deleting the bad file and "install --reinstall" did not work. So I deleted all of the python2.7 lib and bin directories, thinking a reinstall or install would find all the missing directories. My bad..... system still thinks python2.7 is installed. Am now studying how to force a fresh install over the top of the old one - if that option exists. So I think this is a problem I created. Sorry.

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.