Re: Processed: force-overwrite bugs

[Michael Stone <mstone@debian.org>]

On Mon, Mar 03, 2003 at 09:47:55PM +0100, Josip Rodin wrote:
> On Mon, Mar 03, 2003 at 03:37:49PM -0500, Michael Stone wrote:
> > obvious? Note that policy section 7.5.1 says:
> >  If an installed package, foo say, declares that it replaces another,
> >  bar, and an attempt is made to install bar, dpkg will discard files in
> >  the bar package which would overwrite those already present in foo. This
> >  is so that you can install an older version of a package without
> >  problems. 
> >
> > By my reading of that a debianutils package without readlink should be
> > unnecessary.
>
> Well, my dist-upgrade today said:
>
> Preparing to replace coreutils 4.5.7-1 (using .../coreutils_4.5.8-1_i386.deb) ...
> Unpacking replacement coreutils ...
> Replacing files in old package debianutils ...
> Setting up coreutils (4.5.8-1) ...
>
> (Reading database ... 71250 files and directories currently installed.)
> Preparing to replace debianutils 2.2.3 (using .../debianutils_2.3.1_i386.deb) ...
> Unpacking replacement debianutils ...
> dpkg: error processing /fujitsu/debs/debianutils_2.3.1_i386.deb (--unpack):
> trying to overwrite `/bin/readlink', which is also in package coreutils
>
> So basically what you're seeing here is that the ordering isn't necessarily
> sane.

Read the quote above. The ordering shouldn't matter, IMO. Perhaps a dpkg
person can clear up my confusion? Is it the versioning on the replaces:
that's screwing things up?

> > I suppose that coreutils needs a Conflicts against debianutils << 2.4-1
> > as long as people are going to continue installing earlier versions
> > after coreutils 4.5.8-1.

That absolutely cannot happen if debianutils has a pre-depends on
coreutils.

Mike Stone