Bug#40977: dpkg fails to overwite and returns error
On Thu, Jul 08, 1999 at 01:53:04PM +0200, VALETTE Eric wrote:
> I've been using unstable for years and did not notice that...
That's your problem. Reading the dpkg changelog, I see the following
changes to --force-overwrite in the past one and a half years:
1999-05-26 22.214.171.124 - disabled (potato is unstable)
1998-10-22 126.96.36.199 - enabled (slink is about to be frozen)
1998-06-24 188.8.131.52 - disabled (slink is unstable)
1998-06-23 184.108.40.206.2 - enabled (hamm is frozen)
1998-01-09 220.127.116.11 - disabled (hamm is unstable)
> Do you expect me to send a bug in 30% of packages???
> Why do debian
> maintainer not do the precheck via the file list instead of putting
> the work via deferred means on users shoulders...
Really, if all maintainers could check everything without forgetting things
or without noticing some things, there would be no bugs. And we know how
probable that is, don't we. Unstable is called unstable precisely because
it can break unexpectedly.
%%% Antti-Juhani Kaijanaho % firstname.lastname@example.org % http://www.iki.fi/gaia/ %%%
"... memory leaks are quite acceptable in many applications ..."
(Bjarne Stroustrup, The Design and Evolution of C++, page 220)