package python-cryptography 1.2.3-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-cryptography (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
went wrond during updatg
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-cryptography 1.2.3-1ubuntu0.1
ProcVersionSign
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sat Jan 14 18:11:28 2017
DuplicateSignature:
package:
Processing triggers for man-db (2.7.5-1) ...
dpkg: error processing package python-cryptography (--configure):
package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2016-07-31 (167 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.18
SourcePackage: python-cryptography
Title: package python-cryptography 1.2.3-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.