package python-ldb 1:1.1.17-1 failed to install/upgrade: пакет python-ldb не готов к настройке настройка невозможна (текущее состояние: «half-installed»)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ldb (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Не знаю ,возможно медленный интернет .
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: python-ldb 1:1.1.17-1
ProcVersionSign
Uname: Linux 3.16.0-44-generic i686
ApportVersion: 2.14.7-0ubuntu8.5
AptOrdering:
aircrack-ng: Install
ieee-data: Install
python-ldb: Configure
aircrack-ng: Configure
ieee-data: Configure
Architecture: i386
Date: Sun Oct 4 16:28:01 2015
DpkgHistoryLog:
Start-Date: 2015-10-04 16:27:48
Commandline: apt-get install aircrack-ng
Install: aircrack-ng:i386 (1.2-0~beta3-1), ieee-data:i386 (20140613.1, automatic)
ErrorMessage: пакет python-ldb не готов к настройке настройка невозможна (текущее состояние: «half-installed»)
InstallationDate: Installed on 2015-08-23 (41 days ago)
InstallationMedia: Zorin 9 trusty - Release i386 (20140712)
SourcePackage: ldb
Title: package python-ldb 1:1.1.17-1 failed to install/upgrade: пакет python-ldb не готов к настройке настройка невозможна (текущее состояние: «half-installed»)
UpgradeStatus: Upgraded to utopic on 2015-08-28 (36 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since it seems likely to me that this is a local configuration problem, rather than 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.