Ubuntu
xemacs21 package

package xemacs21 21.4.22-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #669709 reported by Tom Fisher on 2010-11-02

This bug report is a duplicate of: Bug #467446: update-alternatives: error: alternative path /usr/bin/xemacs21 doesn't exist.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xemacs21 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: xemacs21

It did not install.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: xemacs21 21.4.22-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
Architecture: amd64
Date: Wed Oct 27 14:56:51 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
SourcePackage: xemacs21
Title: package xemacs21 21.4.22-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Tags:

Revision history for this message

Tom Fisher (wandergeld) wrote on 2010-11-02:

AptOrdering.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Df.txt Edit (516 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (49.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (28.1 KiB, application/x-gzip)

Revision history for this message

era (era) wrote on 2010-11-02:

Quoting the attached DpkgTerminalLog.gz:
> Setting up xemacs21 (21.4.22-2ubuntu1) ...
> update-alternatives: error: alternative path /usr/bin/xemacs21 doesn't exist.
> dpkg: error processing xemacs21 (--configure):
> subprocess installed post-installation script returned error exit status 2

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