package yaml-mode 0.0.4-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Bug #715117 reported by Heiko Busse on 2011-02-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yaml-mode (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: yaml-mode

Unfortunetely, I cannot report any details, as the problem occured when installing the relevant package directly from the ubuntu server.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: yaml-mode 0.0.4-2
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 Feb 8 11:59:38 2011
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: yaml-mode
Title: package yaml-mode 0.0.4-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Heiko Busse (heiko-busse) wrote :
era (era) wrote :

Quoting the attached DpkgTerminalLog.txt:
> install/yaml-mode: Handling install for emacsen flavor emacs-snapshot
> ln: Erzeuge symbolische Verknüpfung „./yaml-mode.el“: Le fichier existe
> emacs-package-install: /usr/lib/emacsen-common/packages/install/yaml-mode emacs-snapshot emacs-snapshot emacs22 emacs23 failed at /usr/lib/emacsen-common/emacs-package-install line 30, <TSORT> line 2.

For some reason, it's installing for emacs-snapshot twice, and the second installation fails because the file it wants to create already exists. I'm not sure if this is a bug in yaml-mode or in emacsen-common. How could you end up with emacsen-common listed twice?

era (era) wrote :

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers