[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems with --force-overwrite being default

On Sun, 2004-12-19 at 04:35 +0100, Goswin von Brederlow wrote:

> the debian-amd64 port had a major problem (breaks the ld, meaning
> everything) caused partially by dpkgs:
> dpkg (1.9.21) unstable; urgency=low
>   * Enable --force-overwrite by default in /etc/dpkg/dpkg.cfg
> I think that default is too dangerous.
Hmm?  --force-overwrite hasn't been the default for a long time.
Specifically dpkg.cfg was moved into the documentation directory.

It has been enabled once or twice just before a release as a quick-fix
for larger problems that there wasn't time to take care of.  It isn't
enabled currently.

> At least in the case of "Replaces" there should be no overwriting by
> the replaced (not the replacing) package by default. This can cause
> files to be lost.
Are you sure you're not just seeing Bug #164595 (dpkg only looks at
Replaces when installing a replacing package, not a package that has
files replaced by another).

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: