Bug#225004: tetex-extra: Type1 fonts should be in a separate package

[frank@kuesterei.ch (Frank Küster)]

Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp> schrieb:

> I'm not sure but I suspect only conflict will make upgrade
> not so smooth.  In unstable, it is not so rare that one fails
> to upgrade a package with messages like
>
> dpkg: error processing
> /var/cache/apt/archives/foo.deb (--unpack):
> trying to overwrite
> `/some/where/some/duplicated/file', which is also in
> package bar
>
> I guess this is caused by lack of replace relation.

I doubt this. I think if there is a Conflicts, then the old package will
be removed before the new one can be installed, as Policy says in 7.3:

,----
| When one binary package declares a conflict with another using a
| Conflicts field, dpkg will refuse to allow them to be installed on the
| system at the same time.
| 
| If one package is to be installed, the other must be removed first
`----

Replaces is not needed for this. According to policy, the combination of
Replaces and Conflicts is only intended to be used together with a
third, Provides. This is clearly not the case here.

If you only have a Conflicts, but the Replaces is missing, then apt-get
doesn't know which of them should be preferred. However, if the
Conflicted-against package, in this case tetex-bin, can also be upgraded
- to a version that is not conflicted against - then I don't see why
this would break the upgrade. Perhaps Florent can again run one of his
experiments...

I think, Conflicts: tetex-bin (<=...) is sufficient.

Regards, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie