Ubuntu
xemacs21 package

package xemacs21 21.4.22-2ubuntu1 failed to install/upgrade:

Bug #642971 reported by Christopher Weth on 2010-09-19

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

happened when updating from 0804 to 1004.
No idea why.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: xemacs21 21.4.22-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.24-24.61-generic
Uname: Linux 2.6.24-24-generic i686
NonfreeKernelModules: ath_hal
Architecture: i386
Date: Sun Sep 19 19:42:14 2010
ErrorMessage:
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
PackageArchitecture: all
SourcePackage: xemacs21
Title: package xemacs21 21.4.22-2ubuntu1 failed to install/upgrade:

Tags:

Revision history for this message

Christopher Weth (christopher-weth) wrote on 2010-09-19:

Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (12.5 KiB, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (79.9 KiB, application/x-gzip)
VarLogDistupgradeLspcitxt.gz Edit (848 bytes, application/x-gzip)
VarLogDistupgradeMainlog.gz Edit (15.4 KiB, application/x-gzip)
VarLogDistupgradeSystemstatetargz.gz Edit (382.4 KiB, application/x-gzip)
VarLogDistupgradeTermlog.gz Edit (83.4 KiB, application/x-gzip)

Revision history for this message

era (era) wrote on 2010-09-20:

Quoting the attached VarLogDistupgradeTermlog.gz:
> update-alternatives: error: Alternativen-Pfad /usr/bin/xemacs21 existiert nicht

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular problem has already been reported in bug #467446, so this bug report is being marked as a duplicate of the earlier report. 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.