On Mon, 2005-06-20 at 11:43 +0200, Christian Hammers wrote: > On 2005-06-20 Debian Bug Tracking System wrote: > > > # Automatically generated email from bts, devscripts version 2.8.14 > > > reassign 287978 mysql-server > > Bug#287978: mysql-server: /var/lib/mysql symlink removed, causing major > > mayhem :) > > Bug reassigned from package `dpkg' to `mysql-server'. > > I'm not yet convinced that I can agree with that. Please retitle it or > change the severity or even tag it as wontfix but it had been assigned to > dpkg for a reason. > Looking at this bug alone, it looks like a problem with mysql's maintainer scripts mucking around with this directory and symlink, rather than dpkg misbehaving.
> Or is there another bug report regarding this issue? One should at least > be kept open for reference to both users and maintainers! > 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. However if both foo 1.0 and 2.0 contain the directory in the package list, then if the admin has changed it to a symlink, the symlink should be preserved. If dpkg is removing the symlink and replacing it with a directory, there is another bug that is not a duplicate of #182747 -- however so far it hasn't shown up in any other package. If #182747 is actually what's going on here (mysql no longer includes /var/lib/mysql and dpkg so the admin's symlink) then by all means reassign and merge the two bugs. If not, we'll need to look a little closer at what's going on -- and try without your maintainer script cruft which I think is really causing the problem. 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
