Bug#780359: Options w.r.t. libcgal11 transition

[Joachim Reichel]

Hi,

dolfin is now the only reverse dependency holding up the libcgal11 transition.

What are the options?
(1) Fix dolfin without causing another transition
(2) Remove dolfin from testing
(3) Upload 1.5.0-1 from experimental to unstable
(4) ...?

(1) I don't know the details but it seems to me that this is not easy.

(3) This causes another transition, but the only reverse dependencies of the
binary packages of dolfin are python-viper (plus the meta packages fenics,
science-mathematics and science-mathematics-dev). Rebuilding python-viper
against dolfin 1.5.0-1 worked without problems. Maybe this additional transition
isn't that bad (apart from the delay)?

BTW does anyone understand why dolfin does not appear in the list of
autoremovals? The bug is release-critical and not fixed in unstable/testing,
only experimental.

Joachim