Ubuntu
ruby1.8 package

package libruby1.8 1.8.7.249-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #600125 reported by David Nelson on 2010-06-30

This bug report is a duplicate of: Bug #512096: [MASTER] Exec format error : package failed to install/remove : installation/removal script returned error exit status 2. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ruby1.8 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: ruby1.8

This is a problem that has not gone away for some time now.... i did try uninstalling and reinstalling ruby related packages, but......... I will try again...

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libruby1.8 1.8.7.249-2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Wed Jun 30 16:02:24 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: ruby1.8
Title: package libruby1.8 1.8.7.249-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Tags:

Revision history for this message

David Nelson (commerce) wrote on 2010-06-30:

AptOrdering.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (559 bytes, text/plain; charset="utf-8")
Df.txt Edit (589 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (47.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (346.9 KiB, text/plain; charset="utf-8")

Revision history for this message

papukaija (papukaija) wrote on 2010-06-30:

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 512096, so it is being marked as such. Please look at the other bug report for two known workarounds. 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.