Bug#410695: zope2.7 causqe upgrade failure

[Josselin Mouette]

I have already encountered similar problems in the past, with GConf, and
they were triggered by a circular dependency.

It seems that APT is unable to deal with such dependencies correctly, as
it removes packages depending on each other in random order (which is
fair) but can also remove one of them before packages depending on the
other are removed.

The solution is, in such cases, to make APT remove all packages
depending on either of those in the dependency loop, then remove the
loop itself. This is unfortunately far from trivial to implement, and -
let's be realistic - impossible to do before the release.

An acceptable workaround would be to upload a dummy zope2.7 package,
which doesn't depend on python2.3, and would make the transition to
zope2.9. At least, such upgrades wouldn't fail.

Thoughts anyone?
-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.alioth.debian.org/pipermail/pkg-zope-developers/attachments/20070302/8860ee18/attachment.pgp