Ubuntu
anjsp package

package anjsp 1.1.3-1ubuntu2 failed to install/upgrade: サブプロセス installed post-installation script はエラー終了ステータス 1 を返しました

Bug #704252 reported by kenchan on 2011-01-18

This bug report is a duplicate of: Bug #222870: anjsp: Wrong number of arguments: require, 3 (xemacs21). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: anjsp

????

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: anjsp 1.1.3-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
Architecture: i386
Date: Tue Jan 18 11:13:07 2011
ErrorMessage: サブプロセス installed post-installation script はエラー終了ステータス 1 を返しました
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: anjsp
Title: package anjsp 1.1.3-1ubuntu2 failed to install/upgrade: サブプロセス installed post-installation script はエラー終了ステータス 1 を返しました

Tags:

Revision history for this message

kenchan (kenchan-sun) wrote on 2011-01-18:

AptOrdering.txt Edit (123 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Df.txt Edit (483 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (122.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.6 MiB, text/plain; charset="utf-8")

Revision history for this message

era (era) wrote on 2011-01-18:

Quoting the attached DpkgTerminalLog.txt:
> While compiling toplevel forms in file /usr/share/xemacs21/site-lisp/anjsp/anjsp.el:
> !! Wrong number of arguments ((require 3))
> >>Error occurred processing anjsp.el:
> Wrong number of arguments: require, 3

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