Ubuntu
tzdata package

package tzdata 2009r-0ubuntu9.10 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 128 zur?ck

Bug #487848 reported by Paul Bußmann on 2009-11-24

This bug report is a duplicate of: Bug #442941: debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128 - Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tzdata (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: tzdata

failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

ProblemType: Package
Architecture: i386
Date: Mon Nov 23 14:53:34 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 128 zurück
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: tzdata 2009r-0ubuntu9.10
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: tzdata
Title: package tzdata 2009r-0ubuntu9.10 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 128 zurück
Uname: Linux 2.6.31-15-generic i686

Tags:

Revision history for this message

Paul Bußmann (paul-medwyn) wrote on 2009-11-24:

AptOrdering.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (505 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (48.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2009-11-26:

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 488786, 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. Please continue to report any other bugs you may find.