On Wed, Sep 06, 2006 at 11:45:59AM +0100, Colin Watson wrote:
> On Wed, Sep 06, 2006 at 11:27:31AM +0100, Alastair McKinstry wrote:
> > Colin Watson wrote:
> > > Package: unicode-data
> > > Conflicts: console-data (<< 2:1.0-1)
> > >
> > > Isn't this just replacing some files that used to be in console-data? If
> > > so, please use Replaces rather than Conflicts; it makes life easier for
> > > the package management system.
> >
> > Ok, will do; but whats the practical difference between
> > Replaces: and Conflicts: ?
>
> Conflicts causes the conflicted-against package to be removed entirely
> from the system (and presumably reinstalled later) if the package
> manager can't work out how to upgrade it first. This often causes
> thrashing, and sometimes causes the unwanted removal of packages higher
> up the dependency chain too (metapackages seem in practice to be
> particularly prone to having this happen to them).
FWIW this also caused console-data to FTBFS in Ubuntu, because:
console-data -> Build-Depends: kbd | console-tools
-> Depends: console-common (either way)
-> Depends: console-data
but:
console-data -> Build-Depends-Indep: unicode-data
-> Conflicts: console-data (of any version that's managed
to autobuild yet)
You wouldn't have noticed this in Debian because either you installed a
pre-release version of one of these package or you ignored some of the
build-dependencies while building. In Ubuntu we autobuild everything, so
we tend to run into these things. I've therefore applied the suggested
change in Ubuntu so that we can move on.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
