package bdii 5.2.5-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1045295 reported by Florido Paganelli
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
bdii (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

please setup apparmor for bdii on debian/ubuntu packages

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bdii 5.2.5-2
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Mon Sep 3 13:54:45 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
PackageArchitecture: all
SourcePackage: bdii
Title: package bdii 5.2.5-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.bdii.bdii.slapd.conf: 2012-09-03T13:54:42.747818
mtime.conffile..etc.bdii.bdii.top.slapd.conf: 2012-09-03T13:54:42.747818

Revision history for this message
Florido Paganelli (bjaast) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Roman Yepishev (rye) wrote :

That happens because apparmor prevents the files from being accessed.

Quick and fast hack is to switch profile to complain mode but this is a packaging problem.

sudo apparmor_parser -C -r /etc/apparmor.d/usr.sbin.slapd

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

This bug was fixed in the package bdii - 5.2.17-4

---------------
bdii (5.2.17-4) unstable; urgency=low

  * Improve purging - fixes piuparts warnings
  * Update Homepage URL

 -- Mattias Ellert <email address hidden> Wed, 20 Mar 2013 15:52:48 +0100

Changed in bdii (Ubuntu):
status: Confirmed → Fix Released
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.