[hardy]: bind9 does not remove /var/lib/bind on purge

Bug #191685 reported by Jamie Strandboge on 2008-02-13
2
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
High
LaMont Jones

Bug Description

Binary package hint: bind9

Running:
$ sudo apt-get remove --purge bind9
$ sudo apt-get install bind9

results in:
Setting up bind9 (1:9.4.2-3) ...
mkdir: cannot create directory `/var/lib/bind': File exists
dpkg: error processing bind9 (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 bind9
E: Sub-process /usr/bin/dpkg returned an error code (1)

It works find without '--purge'

LaMont Jones (lamont) wrote :

bind9 has historically not purged the long-lived directories, stemming from the bind8 vs bind9 upgrades and not wanting users who were switching to lose their data.

The base issue here is that the existance of /var/lib/bind should not be fatal.

Changed in bind9:
assignee: nobody → lamont
importance: Undecided → High
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bind9 - 1:9.4.2-4

---------------
bind9 (1:9.4.2-4) unstable; urgency=low

  * incorporate ubuntu apparmor change from Jamie Strandboge,
    with changes:
    - Add apparmor profile, reload apparmor profile on config
    - Add a note about apparmor to README.Debian
    - conflicts/replaces old apparmor versions
  * db.root: include AAAA RRs. Closes: #464111
  * Don't die when /var/lib/bind already exists. LP: #191685
  * build: turn on optimization. Closes: #435194

 -- LaMont Jones <email address hidden> Mon, 03 Mar 2008 18:58:30 +0000

Changed in bind9:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers