Hi,
On Sun, 9 Mar 2008 13:36:54 +0100, Philipp Kern <[EMAIL PROTECTED]> said:
> fvwm and fvwm-gnome have got their dependencies slightly wrong:
> a) fvwm-gnome should depend on the right replacement version of fvwm,
> which is `fvwm (>= 1:2.5.24), not `fvwm (>= 2.5.24)'.
This is a bug, but not a serious one, since the current package
still matches this.
> b) fvwm must not as a package with priority: optional conflict
> against another package of this set, which fvwm-gnome is.
Wrong. See ยง7.5.2. I did mess up the trsmsition, I think, but
this is not a valid reason. I need to do a versioned conflicts, is all.
> c) The conflict of fvwm against fvwm-gnome hinders the migration of
> your package to testing, because the conflict results in an
> uninstallable fvwm-gnome (even in unstable) and thus would
> increase the uninstallability count.
fvwm-gnome is supposed to be an empty package -- and if I put in
a versioned conflict, it will end up installing fvwm. Which is the
desired goal.
> d) The transition doesn't IMHO work as expected because apt will
> refuse to upgrade fvwm-gnome due to the conflict of fvwm against
> it.
Sure. The solution is *NOT* to remove the conflict
unconditionally, but to make it a versioned conflict (which, in effect,
does remove the conflict between the current versions, so you were
right insofar that the current versions of the packages in the archive
probably should not conflict; or fvwm-gnome should not be uploaded).
manoj
--
Weinberg's First Law: Progress is only made on alternate Fridays.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
