Handling of conflicting conffiles broken
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Debian) |
Fix Released
|
Unknown
|
|||
| dpkg (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Binary package hint: dpkg
dpkg 1.14.16.6ubuntu4 in hardy-updates does weird stuff with packages and conffile conflicts.
Consider this:
Package A has conffile /etc/foo.conf
Package B1 has conffile /etc/foo.conf
Package B2 has conffile /etc/foo.conf and declares that it replaces Package A
If Package A is unpacked but not configured, the unpack of Package B1 will correctly blow up with a file conflict, the unpack of package B2 will correctly replace and take over the conffile
If Package A is fully installed, the unpack of Package B1 will *succeed* (this is the problem) as if Package B1 had declared that it replaced Package A. Package B2 installs and behaves as expected, replacing and taking over the conffile
Turns out this is Debian bug #508392, fixed in 1.14.24 (not sure when it was introduced)
| Andrew Pollock (apollock) wrote | #1 |
| Andrew Pollock (apollock) wrote | #2 |
| Andrew Pollock (apollock) wrote | #3 |
| Philip Muškovac (yofel) wrote | #4 |
| Changed in dpkg (Ubuntu): | |
| status: | New → Fix Released |
| importance: | Undecided → High |
| Changed in dpkg (Debian): | |
| status: | Unknown → Fix Released |
This was fixed a long time ago in that case.