leftover /etc/init.d/bind9.dpkg-dist on each upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Debian) |
Fix Released
|
Unknown
|
|||
bind9 (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: bind9
When doing a server upgrade with all server tasks installed I get a .dpkg-dist file in /etc/default/
It turns out that:
/usr/share/
is different from
/etc/default/bind9
and this cause the postinst script to write a dpkg-dist file.
But it gets stranger, when I tried to track this, I logged into a clean karmic chroot and ran:
# apt-get install bind9
# cd /
# md5sum -c --quiet /var/lib/
usr/share/
md5sum: WARNING: 1 of 32 computed checksums did NOT match
?!?
Related branches
Changed in bind9 (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Confirmed |
summary: |
- leftover /etc/init.d/bind9.dpkg-dist on 9.10 -> 10.04 + leftover /etc/init.d/bind9.dpkg-dist on each upgrade |
Changed in bind9 (Debian): | |
status: | Unknown → New |
Changed in bind9 (Debian): | |
status: | New → Fix Released |
The same md5sum error is produced in lucid for me (in a clean chroot).