← Back to team overview

ubuntu-389-directory-server team mailing list archive

[Bug 1652476] Re: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

 

auto-configuring it is not possible because it needs a dirsrv instance
around in order to work

the fix is to use an error-handler for postinst like for 389-ds-base,
then it would still fail to start the service of course but that would
not fail the install

** Changed in: 389-admin (Ubuntu)
     Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-admin in Ubuntu.
https://bugs.launchpad.net/bugs/1652476

Title:
  package 389-admin 1.1.43-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in 389-admin package in Ubuntu:
  Confirmed

Bug description:
  package 389-admin 1.1.43-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: 389-admin 1.1.43-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   libpam-cgfs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Dec 25 03:21:17 2016
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationDate: Installed on 2016-11-26 (28 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: 389-admin
  Title: package 389-admin 1.1.43-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-admin/+bug/1652476/+subscriptions


References