package ldm-server 2:2.2.9-1ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück

Bug #1091683 reported by Adrian Huber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ldm (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

package ldm-server installation didn't complete because update-inetd wasn't found. /usr/sbin/update-inetd was renamed by an unrecognized process to /usr/sbin/update-inetd.real. I renamed it again to /usr/sbin/update-inetd. After that installation proceeded but ltsp-build-client --arch i386 install failed. ltsp-update-image --arch i386 worked. Thin clients are booting.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: ldm-server 2:2.2.9-1ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
Uname: Linux 3.2.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: amd64
Date: Tue Dec 18 10:06:02 2012
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ldm
Title: package ldm-server 2:2.2.9-1ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Adrian Huber (adrian-huber) wrote :
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

So the problem is that some other package or process renamed update-inetd?
Then this isn't a problem with ldm, is it?
When packages depend on other packages, they can expect their executables to be present without checking for them...

Changed in ldm (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ldm (Ubuntu) because there has been no activity for 60 days.]

Changed in ldm (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.