reassign 287978 dpkg severity 287978 wishlist reassign 307730 dpkg severity 307730 wishlist merge 287978 307730 merge 182747 287978 thanks
On Mon, 2005-06-20 at 21:31 +0200, Christian Hammers wrote: > On 2005-06-20 Scott James Remnant wrote: > > There is a bug reporting regarding the known bug (#182747), but this is > > particularly interesting... > > > > > It's common that admins replace directories with symlinks to relocate big > > > chunks of data to a different partition without mounting a whole partition > > > to this directory or using bind mounts which are not so known among > > > admins. So dpkg should not simply delete a symlink to a directory that > > > still contains files. > > > > > dpkg ordinarily tries very hard to keep symlinks-to-directories rather > > than replacing them with a directory again. > > > > The one known circumstance where there is a bug (noted above) is if the > > directory is removed from the package. If foo 1.0 ships "/foo" and foo > > 2.0 doesn't, dpkg will remove the /foo directory OR symlink. > > In this case the update was from > mysql-server-4.0 (4.0.22) > to > mysql-server-4.1 (4.1.11) > so the first package got removed which is probably technically the same > as an upgrade where the file is no longer in the package and thus this > bug was triggered. > That makes sense. I can see what's going on here, and it is a duplicate of the bug yesterday. This is a good additional use case for it, too. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
