Ubuntu
util-linux package

package mount 2.17.2-3.3ubuntu4 failed to install/upgrade: sub-processo novo script pre-installation retornou estado de saída de erro 127

Bug #719943 reported by Raf on 2011-02-16

This bug report is a duplicate of: Bug #719754: package mount 2.17.2-3.3ubuntu4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 127. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	util-linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: util-linux

Problem with update and install

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: mount 2.17.2-3.3ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
AptOrdering:
mount: Install
mount: Configure
Architecture: amd64
Date: Wed Feb 16 07:51:16 2011
DpkgTerminalLog:
Preparando para substituir mount 2.17.2-3.3ubuntu4 (usando .../mount_2.17.2-9.1ubuntu1_amd64.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 49: dpkg-vendor: not found
dpkg: erro processando /var/cache/apt/archives/mount_2.17.2-9.1ubuntu1_amd64.deb (--unpack):
sub-processo novo script pre-installation retornou estado de saída de erro 127
ErrorMessage: sub-processo novo script pre-installation retornou estado de saída de erro 127
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110212)
SourcePackage: util-linux
Title: package mount 2.17.2-3.3ubuntu4 failed to install/upgrade: sub-processo novo script pre-installation retornou estado de saída de erro 127

Tags:

Revision history for this message

Raf (rmtx28) wrote on 2011-02-16:

Dependencies.txt Edit (764 bytes, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (57.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-02-16:

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 #719754, 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.