Hello Scott
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.
What we noticed though was that a "real" directory would *not* have been
removed if it contained data.
This is the point where dpkg makes a difference between symlinks to
directories and real directories.
The tricks we did to our packages (i.e. removing and creating this symlink
ourselves) was *only* to circumvent this problem on upgrades.
> Scott
bye,
-christian-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
