Ubuntu
bacula package

package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #676544 reported by Sphere on 2010-11-17

This bug report is a duplicate of: Bug #321091: Bacula fails to install correctly if mysql wasn't installed before. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: bacula

I just tried installing Bacula...

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-director-mysql 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic-pae i686
NonfreeKernelModules: openafs nvidia
Architecture: i386
Date: Wed Nov 17 16:46:18 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
SourcePackage: bacula
Title: package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Sphere (s-t-erkelens) wrote on 2010-11-17:

AptOrdering.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Df.txt Edit (513 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (56.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (6.8 KiB, application/x-gzip)

Revision history for this message

James Page (james-page) wrote on 2010-11-18:

You should be able to work round this by installing mysql-server before bacula - see bug 616754.

Revision history for this message

James Page (james-page) wrote on 2010-11-18:

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 616754, 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.