Bug#225004: tetex-extra: Type1 fonts should be in a separate package
From: frank@kuesterei.ch (Frank Küster)
Subject: Bug#225004: tetex-extra: Type1 fonts should be in a separate package
Date: Sun, 15 Feb 2004 13:34:43 +0100
> 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
> `----
I might be wrong but the above is for Conflict without version,
isn't it?
> 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.
I see your point but the situation might be more complicated.
Please note that tetex-bin has also overwriting problem with
tetex-base (<< 2.0.1), that is tetex-base and tetex-bin have
mutually overwrinting problem when they are upgarding from
woody to sarge.
I don't know which one will be first unpacking but I suspect,
already at that stage, there could be overwriting problem and
failure of upgrading.
On tetex-extra, it might be enough to set Conflicts, however
I'm not sure at present.
Also, setting Replaces only in the current packages might be
wrong and if it is sure I'll add Conflicts as soon as possible.
If it is certain that Conflicts only is enough for smooth
upgrading, I'm willing to modify control.
FYI:
tetex-base (2.0.2-1) unstable; urgency=low
(snip)
* Installed web2c/mktex.cnf, formerly installed in tetex-bin. [kohda]
tetex-bin (2.0.1-1) unstable; urgency=low
* New Upstream Release.
(snip)
- tcdialog support files were moved from tetex-base to tetex-bin in
the upstream 2.0.1 so we setted Depends: tetex-base (>= 2.0.1) and
Replaces: tetex-base (<< 2.0.1) [kohda]
Regards, 2004-2-15(Sun)
--
Debian Developer & Debian JP Developer - much more I18N of Debian
Atsuhito Kohda <kohda@debian.org>
Department of Math., Univ. of Tokushima
Reply to: