Ubuntu
man-db package

package man-db 2.5.7-4 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1

Bug #697790 reported by daniele pirani on 2011-01-05

This bug report is a duplicate of: Bug #349469: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	man-db (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: man-db

just updated, i have many repositories so maybe it's not a problems of everybody.

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: man-db 2.5.7-4
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
Architecture: amd64
Date: Wed Jan 5 19:12:51 2011
ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928.1)
SourcePackage: man-db
Title: package man-db 2.5.7-4 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1

Tags:

Revision history for this message

daniele pirani (daniel-pirani) wrote on 2011-01-05:

AptOrdering.txt Edit (173 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (888 bytes, text/plain; charset="utf-8")
Df.txt Edit (596 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (54.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (2.2 KiB, application/x-gzip)

Revision history for this message

Monkey (monkey-libre) wrote on 2011-06-22:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 349469, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.