Hi, On Fri, Feb 05, 2010 at 10:16:06PM +0200, Eugene V. Lyubimkin wrote: > No, no one package manager can upgrade packages in this situation directly, in > theory. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560896#74. > libapt-based package managers upgrade them indirectly silently, cupt - does > not, by default.
And why does cupt that different? I see no reason to break other packages by changing behaviour there. But anyway... > If Replaces don't make sense there, then Conflicts, probably, too. Eh, no, read again what Replaces: has for semantics in the policy (7.3 and 7.6.1) Replaces: just says that it replaces files. Which here obviously is not the case. (Or for replacing packages completely with Conflicts/Replaces/Provides as in 7.6.2) Replaces: has no business here. The Conflicts is to prevent e.g. 3.2 core with 3.1 langpacks (which indeed probably can be achieved by Breaks:) Grüße/Regards, René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' r...@debian.org | GnuPG-Key ID: D03E3E70 `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
