bind9 prerm script fails if bind9 happens to be stopped at upgrade time
Bug #625044 reported by
Earl Denty
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Debian) |
Fix Released
|
Unknown
|
|||
bind9 (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: bind9
Failure occurred during upgrade to version 10.0 of ubuntu.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bind9 1:9.7.0.dfsg.P1-1
ProcVersionSign
Uname: Linux 2.6.31-22-generic i686
Architecture: i386
Date: Thu Aug 26 20:35:06 2010
ErrorMessage:
ErrorMessage: subprocess installed post-installation script killed by signal (Interrupt)
SourcePackage: bind9
Title: package bind9 1:9.7.0.dfsg.P1-1 failed to install/upgrade:
Changed in bind9 (Debian): | |
status: | Unknown → Fix Released |
tags: | added: dist-upgrade |
To post a comment you must log in.
Hello Earl, thanks for taking the time to file this bug report and help us make Ubuntu better.
The bind9 prerm script (which is run before we remove the old version) stops bind9. Unfortunately, if bind9 is not running at the time, it registers as an error.
For your situation, you can start bind9 before the upgrade to work around this issue.
Marking as triaged, as the prerm script should be able to check to see if bind9 is running before stopping it.
Setting Importance to Low, as this will only affect users who happen to have bind9 stopped while upgrading.