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

Bug#145595: dpkg: --force-overwrite is supposed to be on for releases



On Mon, May 06, 2002 at 12:12:30PM -0400, Joey Hess wrote:
> I do not follow your reasoning in this last paragraph at all, and the
> proceeding paragraph has a flawed premise.

> There are more file conflicts present between potato and woody than
> there are in woody itself. Therefore we have to find a means to get
> force-overwrite turned on on upgrade. base-config cannot do that.

You're right. Bugger.

Wichert, I don't see any way around this: either dpkg should have
--force-overwrite on by default and some way of overriding it in
dpkg.cfg, or the dpkg.cfg conffile shipped in dpkg.deb needs to have
--force-overwrite included.

We *could* probably do the latter by kludging around with base-files'
postinst or something similar, but that seems likely to be more pain
than a new dpkg upload.

So a new dpkg upload, with

	# uncomment this if you're clueful
	--force-overwrite

added to dpkg.cfg seems the simplest fix.

Am I missing anything?

Cheers,
aj

-- 
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.

     ``BAM! Science triumphs again!'' 
                    -- http://www.angryflower.com/vegeta.gif

Attachment: pgpYY5tVEo60r.pgp
Description: PGP signature


Reply to: