Bug#145595: dpkg: --force-overwrite is supposed to be on for releases
Anthony Towns wrote:
> Well, our choices are:
>
> * new dpkg release
> * new boot-floppies for all architectures that munge it (maybe via
> debootstrap)
> * new base-config that munges it
> * don't fix the problem
>
> A new base-config seems by far the easiest to get right, doesn't need
> people to spend a few days building it, and since it's needed anyway...
(A new base-config is already available...)
If the change is put into base-config, it is going to return to bother
us when we want to have plenty of unstable systems later on with
--force-overwrite turned off. If it's all done in dpkg, a new dpkg in
unstable can turn the force-overwrite off easily, but there is no
similar upgrade path for base-config.
Also, putting this change in base-config will only affect new installs,
while it is file conflicts between differing versions of packages that
most often slip by, and so it is in upgrades that the file conflicts tend
to show up most often.
It's also a trivial, tested change in dpkg. It is a one byte change as I
recall. The autobuilders will only take a few days surely; the security
team could even use this as a test of whatever new autobuilder system
they are coming up with, to get a the new dpkg built.
I'm going to be away for a week after Tuesday or Wednesday; if I change
base-config now to add this inferior hack someone is going to have to be
ready to support it.
--
see shy jo
--
To UNSUBSCRIBE, email to debian-dpkg-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: