Bug#36972: dpkg: dpkg can remoev vital files/symlinks without warning adminitrator
On Fri, Apr 30, 1999 at 02:46:50PM -0700, Steve Lamb wrote:
> Package: dpkg
> Version: 188.8.131.52
> Severity: Critical
> While updating listar from .118a to .121a dpkg removed symlinks which
> were vital for listar to operate. This is because the maintainer had
> changed how his configuration worked and did not warn the administrator in
> the upgrade that a major change was forthcoming.
> Regardless of the semantics of this issue it raises the concertn that
> dpkg is deleting files/directories and symlinks based on the false
> assumption that if the maintainer is not using the links/files/directories,
> neither is (or should) the individual administrators. This can lead to any
> package, at any time, breaking based on such a false assumption.
> It is my opinion that dpkg, on an upgrade, should *NOT* remove any
> file/directory/link without first prompting the maintainer in the same
> manner that it prompts for action when it comes to the configuration file.
So let me get this straight, if tetex moves it's files from (not sure
if it's the right dir, but...) /usr/lib/tex to /usr/lib/tetex then you
want dpkg to prompt you for all (possibly) hundreds of files that it is
If a package breaks on an upgrade, it is the packages fault. dpkg can
only be but so smart about these things.
----- -- - -------- --------- ---- ------- ----- - - --- --------
Ben Collins <firstname.lastname@example.org> Debian GNU/Linux
OpenLDAP Dev - email@example.com The Choice of the GNU Generation
------ -- ----- - - ------- ------- -- ---- - -------- - --- ---- - --